Database Info

i cant do Recovery

hello, im trying to install a custom rom, and now im in recovery step. i installed like 3 different recoverys.
all of them stuck in the red text step(when i get in to recovery mode from bootloader), and even after 20-30 mins still in the same position.
can someone say me when i need to do? i really need to fix it.

Snow201 said:
hello, im trying to install a custom rom, and now im in recovery step. i installed like 3 different recoverys.
all of them stuck in the red text step(when i get in to recovery mode from bootloader), and even after 20-30 mins still in the same position.
can someone say me when i need to do? i really need to fix it.
Click to expand...
Click to collapse
Make sure you are not plugged into your pc when you boot to recovery! - if that doesn't solve it ..
Does the phone boot to the existing Rom, do you have Rom manager installed? - if so update the recovery from Rom Manager. I found that after rooting the One S using the toolkit I could not get in to recovery, the update from Rom Manager sorted it!
All the best :good:

FatherD said:
Make sure you are not plugged into your pc when you boot to recovery! - if that doesn't solve it ..
Does the phone boot to the existing Rom, do you have Rom manager installed? - if so update the recovery from Rom Manager. I found that after rooting the One S using the toolkit I could not get in to recovery, the update from Rom Manager sorted it!
All the best :good:
Click to expand...
Click to collapse
i tried before to get in to recovery mode without USB(plugged to my computer or to charger) and still same problem.
and i dont have any rom manager.
i got HTC one S only with Unlocked phone and recovery(that doesnt work), so i think i need root for rom manager.
got something else?

Snow201 said:
i tried before to get in to recovery mode without USB(plugged to my computer or to charger) and still same problem.
and i dont have any rom manager.
i got HTC one S only with Unlocked phone and recovery(that doesnt work), so i think i need root for rom manager.
got something else?
Click to expand...
Click to collapse
Had same issue with the tool kit, the cwm didnt stick. The Touch work one did stick and I was able to get into recovery. However I downloaded the app ROM MANAGER and flashed the recovery from there. Since then I've had no issues booting into reocvery or bootloader. Just download rom manager and go about it that way!

osugsxr said:
Had same issue with the tool kit, the cwm didnt stick. The Touch work one did stick and I was able to get into recovery. However I downloaded the app ROM MANAGER and flashed the recovery from there. Since then I've had no issues booting into reocvery or bootloader. Just download rom manager and go about it that way!
Click to expand...
Click to collapse
NVM, there is no recovery for HTC at all, only Galaxy and some more. what i need to do?

I had this problem when I first rooted its weird just download the recovery again but save straight to fastboot folder wherever u have the folder and don't rename then flash the recovery that's how mine worked
Sent from my HTC One S using xda premium

k1llacanon said:
I had this problem when I first rooted its weird just download the recovery again but save straight to fastboot folder wherever u have the folder and don't rename then flash the recovery that's how mine worked
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
but i dont have root... and for root my phone i need recovery
there is some other way to root?
because the ROM manager doesnt work well without root.(cant install new recovery)

Snow201 said:
but i dont have root... and for root my phone i need recovery
there is some other way to root?
because the ROM manager doesnt work well without root.(cant install new recovery)
Click to expand...
Click to collapse
I'm not telling you to use Rom manager =\
Sent from my HTC One S using xda premium

k1llacanon said:
I'm not telling you to use Rom manager =\
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Ohh. .. but still in tried install the recovery like 2-4 times.
There is other way?

Snow201 said:
Ohh. .. but still in tried install the recovery like 2-4 times.
There is other way?
Click to expand...
Click to collapse
Which recoveries have you tried, and what version of phone do you have (S3 or S4). These must match.
Make sure you bootloader unlocked OK, check in bootloader screen, should say Unlocked.
The problem youre describing sound like when you try to boot after successfully flashing a ROM but forgot to or the kernel failed to flash with it. Only happens when ROM and kernel are mismatched enough that it wont boot, fex flashing CM9 and still on HTC original kernel. Try flashing the kernel from the ROM zip file with
Code:
fastboot flash boot boot.img
You can also try booting a recovery without installing it,
Code:
fastboot boot nameofrecoveryfile.img

frdd said:
Which recoveries have you tried, and what version of phone do you have (S3 or S4). These must match.
Make sure you bootloader unlocked OK, check in bootloader screen, should say Unlocked.
The problem youre describing sound like when you try to boot after successfully flashing a ROM but forgot to or the kernel failed to flash with it. Only happens when ROM and kernel are mismatched enough that it wont boot, fex flashing CM9 and still on HTC original kernel. Try flashing the kernel from the ROM zip file with
Code:
fastboot flash boot boot.img
You can also try booting a recovery without installing it,
Code:
fastboot boot nameofrecoveryfile.img
Click to expand...
Click to collapse
nope, until now i did only unlock for my phone. and i have no idea with version i have, how do i check it?

Snow201 said:
nope, until now i did only unlock for my phone. and i have no idea with version i have, how do i check it?
Click to expand...
Click to collapse
If you have working ADB and fastboot working (there is a sticky by user fibsib that explains this) you can make sure your phone isnt really just trying to boot the OS and failing rather than trying to enter recovery with the command
Code:
adb reboot recovery
But anyways figure out which version you have before doing anything more, flash the wrong stuff and you could break stuff. There are good info here as to how to see if you have the Ville=Z520e=S4 processor model or the Ville C2/Z560e/S3 processor model.
Then download a recovery for your phone model and install it with this command from your computer
Code:
fastboot flash recovery nameofrecoveryyoudownloaded.img
Should work.

have you actually flashed a recovery yet?
which one and how did you do it?

Make sure you have your phone updated to the latest software version before you root. Download system update OTA and click update.
Otherwise you will have issues.
I am rooted T-Mobile phone with original software 1.54 and still can not do recovery or update, it is probably me but it is difficult.
If you are in the US, make sure you use the US version in the development section after you upgrade your phone. Update then try to root it might be easier.

Problems with downgrading to KitKat

Hey guys, I'm trying to downgrade to KitKat after all the issues Lollipop is giving me and the incompatible apps I'm trying to run.
I am following instructions here but I came across a problem when flashing the system.img file.
The error it gives me is:
FAILED (remote: Insufficient memory.)
I can't flash over system and can not boot.
What am I missing? I was rooted and my bootloader unlocked prior to starting and I tried with the factory recovery and the 1.2.1 recovery image.
Edit: My issue has been solved. Flashing the Full OTA.zip file will install KitKat over Lollipop. No need to manually flash each file through fastboot. I wish guides would tell you that instead.

BlackDave said:
Hey guys, I'm trying to downgrade to KitKat after all the issues Lollipop is giving me and the incompatible apps I'm trying to run.
I am following instructions here but I came across a problem when flashing the system.img file.
The error it gives me is:
FAILED (remote: Insufficient memory.)
I can't flash over system and can not boot.
What am I missing? I was rooted and my bootloader unlocked prior to starting and I tried with the factory recovery and the 1.2.1 recovery image.
Click to expand...
Click to collapse
I don't know why that wouldn't work. Have you tried just downloading the image from nvidia HERE?
I'm assuming wifi since your sig says 16GB

Keithn said:
I don't know why that wouldn't work. Have you tried just downloading the image from nvidia HERE?
I'm assuming wifi since your sig says 16GB
Click to expand...
Click to collapse
Those are the same files as the ones I downloaded in the other thread.

I got my tablet working again on Lollipop 5.0.1 but that's not where I want to be. I've searched about my error message but most threads I found went unanswered.

Your best bet might just be to try getting a full OTA and flashing it through cwm or something. I'll try with mine when I have some time to backup and flash, probably later tomorrow. If I find anything out I'll post.
Sent from my SHIELD Tablet

BlackDave said:
I got my tablet working again on Lollipop 5.0.1 but that's not where I want to be. I've searched about my error message but most threads I found went unanswered.
Click to expand...
Click to collapse
I just flashed the images and booted.
Did you accidentally try flashing to the wrong place, such as flashing to boot( which would be too small) instead of system? Did you do all of the commands yourself or use the .bat? My shield disconnected after doing the boot.img and system.img for some reason, so I had to select fastboot protocol to reboot the bootloader and continue to flash the userdata.img, blob, and battery.dtb.

was your tablet internal memory full?, try wipping data and chace and you could use the script that the original Nvidia recovery image has zipped. I went up and down like 3 times, im in kitkat right now and not experiencing any problem.

Iams1002 said:
was your tablet internal memory full?, try wipping data and chace and you could use the script that the original Nvidia recovery image has zipped. I went up and down like 3 times, im in kitkat right now and not experiencing any problem.
Click to expand...
Click to collapse
No I wipped internal data since I keep everything on external and it still didn't work.
Keithn said:
I just flashed the images and booted.
Did you accidentally try flashing to the wrong place, such as flashing to boot( which would be too small) instead of system? Did you do all of the commands yourself or use the .bat? My shield disconnected after doing the boot.img and system.img for some reason, so I had to select fastboot protocol to reboot the bootloader and continue to flash the userdata.img, blob, and battery.dtb.
Click to expand...
Click to collapse
So I should just flash the ota.zip?
Also i did everything like the guide. I flashed boot to boot, recovery to recovery. The only thing that gave me an error was system. Userdata, blob, and battery also flashed successfully. After that didn't work, I also tried the .bat and that didn't work either. Flashing the 5.0.1 update got my tablet running again.

BlackDave said:
No I wipped internal data since I keep everything on external and it still didn't work.
So I should just flash the ota.zip?
Also i did everything like the guide. I flashed boot to boot, recovery to recovery. The only thing that gave me an error was system. Userdata, blob, and battery also flashed successfully. After that didn't work, I also tried the .bat and that didn't work either. Flashing the 5.0.1 update got my tablet running again.
Click to expand...
Click to collapse
If you can find a full ota.zip for update 1.2.1 I'd try that. I'm not sure why you would be having this issue. The only other things I can say to try is redownloading and rebooting the boot loader (select fastboot protocol) between images in case something funny is happening there. Let us know how you end up doing.
Sent from my HTC M8

Keithn said:
If you can find a full ota.zip for update 1.2.1 I'd try that. I'm not sure why you would be having this issue. The only other things I can say to try is redownloading and rebooting the boot loader (select fastboot protocol) between images in case something funny is happening there. Let us know how you end up doing.
Sent from my HTC M8
Click to expand...
Click to collapse
I flashed the 1.2.1 OTA update and it worked. The first time I tried, I did using the TWRP recovery but for some reason, that recovery fails to flash OTAs, so I went with CWM and flashed the 2.1 update and all worked again. After a while, I got tired of all the issues lollipop gave me so that's why I tried following that guide to downgrade.
In the end, using CWM and flashing the OTA is the best way to go. Thank you all for you help.

[Resolved] Installed TWRP on phone with a locked bootloader - now stuck in boot loop

I am new to rooting, and decided to root my Galaxy Note II SGH-i317m a few days ago. I used a method with no adb access...i think. Here's the reference thread, just in case I'm wrong: http://forum.xda-developers.com/showthread.php?t=1980644
I got a bit overenthusiastic, and got TWRP while forgetting to unlock my bootloader first. Now, my phone will only boot into TWRP. All 4 reboot options go back to TWRP. What is the best way to get my phone back to working? I understand that I may have to lose my data. It doesn't matter: my top priority is getting my phone to work again.
Thanks in advance!
EDIT: I'm sorry if this is in the wrong place. I'm new here.

if you can boot into recovery than try to wipe cache and dalwik cache than try to too boot again it may work
Sent from my SM-G7102 using Tapatalk

EMONESSboy said:
if you can boot into recovery than try to wipe cache and dalwik cache than try to too boot again it may work
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
Thanks for the quick reply. I just tried that, and no change. Just to clarify, the only thing I can boot into at the moment is recovery mode.
I think what I need to do is flash the stock recovery back onto my phone. Is this a possible solution? If so, how should I go about doing it? I currently cannot access download mode.

i think u should install your current rom again if u insall stock recovery you may not able to do this with stock recovery even cant get twrp back
so..do a nandroid backup and install a rom which u like stock1 or custom1
Sent from my SM-G7102 using Tapatalk

I Can Help
@phoenix204
im sure i can help you
u sure can boot into recovery mode and that too TWRP?if yes ...,
then install usb and adb drivers for your note 2 search minimals adb and fastboot and universal adb drivers on google and download them install them reply if u did it and i will tell u to unlock your bootloader and flash a rom if necessary
we sure can fix it
just tell me when u r done

EMONESSboy said:
i think u should install your current rom again if u insall stock recovery you may not able to do this with stock recovery even cant get twrp back
so..do a nandroid backup and install a rom which u like stock1 or custom1
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
Well, the thing is, my problem isn't with the ROM at all. It's that TWRP does not work with a locked bootloader. So the way I see it, either I need to replace TWRP with something that works with a locked bootloader, or unlock the bootloader. In your opinion, how would replacing the ROM help with my problem?
[email protected] said:
@phoenix204
im sure i can help you
u sure can boot into recovery mode and that too TWRP?if yes ...,
then install usb and adb drivers for your note 2 search minimals adb and fastboot and universal adb drivers on google and download them install them reply if u did it and i will tell u to unlock your bootloader and flash a rom if necessary
we sure can fix it
just tell me when u r done
Click to expand...
Click to collapse
It's done. It's worth noting that my root method, linked in the OP, doesn't give adb access. I'm not sure if this changes anything.
Also, I discovered that by removing and replacing the battery, my phone can power off. From here I can access download mode. Something that might be useful, especially if the solution involves odin.

Phoenix204 said:
Well, the thing is, my problem isn't with the ROM at all. It's that TWRP does not work with a locked bootloader. So the way I see it, either I need to replace TWRP with something that works with a locked bootloader, or unlock the bootloader. In your opinion, how would replacing the ROM help with my problem?
It's done. It's worth noting that my root method, linked in the OP, doesn't give adb access. I'm not sure if this changes anything.
Also, I discovered that by removing and replacing the battery, my phone can power off. From here I can access download mode. Something that might be useful, especially if the solution involves odin.
Click to expand...
Click to collapse
tried system restore with twrp?
try it first and if ur not sure that it will work just make backup of boot , efs , system and data(if necessary) via twrp to sd card copy the backup to pc via card reader or something and extract the system backup there should be a file named build.prop in system folder edit it and do it like this :
under #additional build properties
ro.adb.secure=0
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.root_access=1
find the above lines and edit the parameters as i have shown to you use notepad++ to edit the file save it the last line will give ya root access by default and second last will make it debuggable just save it repack and flash with twrp cheers
hit thanks

Alright. Since I can't find another thread like this one, I will assume that I am one of the first to have this problem. Here is what I did.
I used samsung-firmware.org to find the latest firmware for my phone, which includes both ROM and recovery. Other brands probably also have a website like this.
I used Odin to flash the firmware onto my phone - this wiped my data, but removed TWRP, which is an acceptable solution to me. I might also have wiped my data while playing around with TWRP trying to fix my phone - I'm not sure.
Thanks to both EMONESSboy and [email protected] for their help. I ended up going with something similar to EMONESSboy's solution, since the commands seemed a little risky. Thanks anyways, your help is much appreciated!

IRIS Fuel50
EMONESSboy said:
i think u should install your current rom again if u insall stock recovery you may not able to do this with stock recovery even cant get twrp back
so..do a nandroid backup and install a rom which u like stock1 or custom1
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
Same problem with my lava iris Fuel50. My phone is stuck up. I am able to get recovery menu using volume + power button.
Pl advice what to do now ?

mzn.facebook said:
Same problem with my lava iris Fuel50. My phone is stuck up. I am able to get recovery menu using volume + power button.
Pl advice what to do now ?
Click to expand...
Click to collapse
If your situation is the same as mine was, I would recommend the same solution. Just to clarify - you rooted your phone? And then you installed a custom recovery, which is now the only thing you can access?
If so, you should install your stock ROM the same way you installed the rooted ROM. I'm not sure how you would go about doing that, or even if you can access that mode, since your model is not very common.

Kingaroot
Phoenix204 said:
If your situation is the same as mine was, I would recommend the same solution. Just to clarify - you rooted your phone? And then you installed a custom recovery, which is now the only thing you can access?
If so, you should install your stock ROM the same way you installed the rooted ROM. I'm not sure how you would go about doing that, or even if you can access that mode, since your model is not very common.
Click to expand...
Click to collapse
Actually, what happend was that i tried to root my phone through Kingaroot. It shows some error at 90%. After few seconds my phone gets rebooted and snce then, it is showing Mfr LOGO only.
I have tried Factory reset, wipe cache partition etc.
I had lollipop earlier on my phone.

Rootable Stock Kernel [32.2.A.0.253] [E6883]

Hey guys, just compiled a rootable kernel for the Z5P (E6883) 6.0.1 dual sim version, FW 224.
Features:
1. Sony RIC is disabled.
2. TWRP recovery - press volume up while booting.
3. Busybox.
4. DRM fix.
Code:
fastboot boot boot.img
fastboot reboot
IMPORTANT:
1. Please don't flash any recovery after flashing this kernel as recovery is already present in it.
2. Press volume up to enter recovery, pressing volume down won't work and the phone will reboot.
The first version was having some root permission issues. Flash the new kernel and then flash SuperSU 2.65 via recovery.
Reboot to system and manually install SuperSU 2.74 beta. Update the binary and reboot.
Thanks to tobias.waldvogel for his resources and tutorials.
Please don't flash it on any other device.
I'll not be responsible if you damage your device, just make sure your bootloader is unlocked and you know how to flash using fastboot.​

Is it runs E6853 ?
edit ...

jarnsaxa said:
Is it runs E683 ?
Click to expand...
Click to collapse
Its only for the E6883 dual sim variant..

arjun.arora said:
Its only for the E6883 dual sim variant..
Click to expand...
Click to collapse
Hey man,
I've already put up the kernel for e6883 in the general section in the proper thread no offence

It work on e6833 it is the same kernel??

jarnsaxa said:
Is it runs E6853 ?
edit ...
Click to expand...
Click to collapse
karrouma said:
It work on e6833 it is the same kernel??
Click to expand...
Click to collapse
Well, in theory is should. You can give it a shot. If it doesn't, flash the stock kernel with flashtool to revert back. Don't flash it on single sim variants of the Z5P.

arjun.arora said:
Well, in theory is should. You can give it a shot. If it doesn't, flash the stock kernel with flashtool to revert back. Don't flash it on single sim variants of the Z5P.
Click to expand...
Click to collapse
I flashed it over custom rom RomAUR v4.0.1, on E6833. Unfortunately it says Baseband version Unknown and thus doesn't recognise the sim - plus the brightness slider doesn't function.

slayerz said:
I flashed it over custom rom RomAUR v4.0.1, on E6833. Unfortunately it says Baseband version Unknown and thus doesn't recognise the sim - plus the brightness slider doesn't function.
Click to expand...
Click to collapse
This is for stock firmwares buddy.. RomAur already has a modded kernel..

arjun.arora said:
This is for stock firmwares buddy.. RomAur already has a modded kernel..
Click to expand...
Click to collapse
It work with e6833??
Same kernel

what about E6653 ?

arjun.arora said:
Hey guys, just compiled a rootable kernel for the Z5P (E6883) 6.0.1 dual sim version, FW 224.
Features:
1. Sony RIC is disabled.
2. TWRP recovery - press volume up while booting.
3. Busybox.
4. DRM fix.
Code:
fastboot boot boot.img
fastboot reboot
The first version was having some root permission issues. Flash the new kernel and then flash SuperSU 2.65 via recovery.
Reboot to system and manually install SuperSU 2.74 beta. Update the binary and reboot.
Thanks to tobias.waldvogel for his resources and tutorials.
Please don't flash it on any other device.
I'll not be responsible if you damage your device, just make sure your bootloader is unlocked and you know how to flash using fastboot.​
Click to expand...
Click to collapse
Thanks. I'll try it later tonight.. I've had a pretty ****ty time this far with other boots. Nothing has worked with 6.0.1 224 for me, but I'm willing to try.
In sitting on the 6.0 Hong Kong 1.185 atm
Sent from my E6883 using XDA-Developers mobile app

slayerz said:
I flashed it over custom rom RomAUR v4.0.1, on E6833. Unfortunately it says Baseband version Unknown and thus doesn't recognise the sim - plus the brightness slider doesn't function.
Click to expand...
Click to collapse
korom42 said:
what about E6653 ?
Click to expand...
Click to collapse
I don't own a 6653 buddy. Do one thing, please share the kernel.sin of your fw, open the firmware in winrar and extract it.

giz02 said:
Thanks. I'll try it later tonight.. I've had a pretty ****ty time this far with other boots. Nothing has worked with 6.0.1 224 for me, but I'm willing to try.
In sitting on the 6.0 Hong Kong 1.185 atm
Sent from my E6883 using XDA-Developers mobile app
Click to expand...
Click to collapse
FAILED!
Attempt 1:
Procedure -
Flashed Customised MY 32.2.A.0.224
Dropped to fastboot flashed boot and recovery (twrp-3.0.2-0-E6653-20160417.img)
Rebooted.. to system
Couldn't update SU from OS. (Installation Failed)
Tried dropping recovery again so I could load su manually, but no file systems were mountable.
Attempt 2:
Procedure
Flashed Stock Customized IN 32.2.A.0.224
Rebooted to system
Dropped to fastboot
Flashed boot
Rebooted to System
Launched SU, couldn't update from OS (Installation Failed)
Dropped to fastboot
Flashed recovery (twrp-3.0.2-0-E6653-20160417.img)
rebooted to recovery so I could load su manually,
but no file systems were mountable. (Same as attempt 1)
You've wasted my time - NO workable root...
At least Xreality/DRM appears to have worked.
Going back to 6.0

giz02 said:
FAILED!
Attempt 1:
Procedure -
Flashed Customised MY 32.2.A.0.224
Dropped to fastboot flashed boot and recovery (twrp-3.0.2-0-E6653-20160417.img)
Rebooted.. to system
Couldn't update SU from OS. (Installation Failed)
Tried dropping recovery again so I could load su manually, but no file systems were mountable.
Attempt 2:
Procedure
Flashed Stock Customized IN 32.2.A.0.224
Rebooted to system
Dropped to fastboot
Flashed boot
Rebooted to System
Launched SU, couldn't update from OS (Installation Failed)
Dropped to fastboot
Flashed recovery (twrp-3.0.2-0-E6653-20160417.img)
rebooted to recovery so I could load su manually,
but no file systems were mountable. (Same as attempt 1)
You've wasted my time - NO workable root...
At least Xreality/DRM appears to have worked.
Going back to 6.0
Click to expand...
Click to collapse
You don't have to flash recovery after flashing this. It already has TWRP. Read the instructions carefully.

arjun.arora said:
You don't have to flash recovery after flashing this. It already has TWRP. Read the instructions carefully.
Click to expand...
Click to collapse
Bro. Read beyond attempt 1 procedure.. Carefully
I tried su binary upgrade os.. FAILED
Recovery didn't after this attempt .. held vol down after yellow LED but was greeted by flashing red LED, followed by black screen and reboot.
Flashed recover at this point.. permissions trashed.
Couldn't mount any fs..
Failed.
What are you saying anyway, that u can't flash recovery with your kernel?
I regardless, i recommend as a e6883 owner with device in hands to other e6883 owners that this kernel be avoided until fixed .
I'm guessing you guys didn't rebuild from scratch after your ran into your 2.65 su issues. The jump to 2.74 isn't working for me with your kernel fix

giz02 said:
Bro. Read beyond attempt 1 procedure.. Carefully
I tried su binary upgrade os.. FAILED
Recovery didn't after this attempt .. held vol down after yellow LED but was greeted by flashing red LED, followed by black screen and reboot.
Flashed recover at this point.. permissions trashed.
Couldn't mount any fs..
Failed.
What are you saying anyway, that u can't flash recovery with your kernel?
I regardless, i recommend as a e6883 owner with device in hands to other e6883 owners that this kernel be avoided until fixed .
I'm guessing you guys didn't rebuild from scratch after your ran into your 2.65 su issues. The jump to 2.74 isn't working for me with your kernel fix
Click to expand...
Click to collapse
You need to press volume up after flashing the kernel..

Working perfect for me..no issue at all..e6883
Sent from my E6883 using XDA-Developers mobile app

zams85 said:
Working perfect for me..no issue at all..e6883
Sent from my E6883 using XDA-Developers mobile app
Click to expand...
Click to collapse
Great

arjun.arora said:
You need to press volume up after flashing the kernel..
Click to expand...
Click to collapse
Yes..
flash using flashtool.
drop to fastboot (vol up)
flash boot image... reboot
I get into OS, and su tries to update from 265 to 274.. fails in os
reboot to recovery (vol down when yellow led comes on)
try installing su zip from but can't see file system.. can't mount.. busted permissions everywhere
to recover I revert to 6.0
flashtool (using customized HK .185 load)
after flash, drop to fast boot (vol up)
flash older 6883MM bin
flash recovery (3.0.2)
boot to os.
reboot to recovery
install SU (file systems mount without issue).
everything works normally at 6.0 again
---------- Post added at 09:22 AM ---------- Previous post was at 09:18 AM ----------
zams85 said:
Working perfect for me..no issue at all..e6883
Sent from my E6883 using XDA-Developers mobile app
Click to expand...
Click to collapse
When you say "Works perfectly" have you gone into recovery mode and attempted file system mount, OR;
did you flashtool, then flash boot and then use phone?
I'll say that the phone booted to OS fine with this kernel, and I was able to access xreality settings, HOWEVER I was not able to use recovery mode due to numerous permissions errors. (could not mount FS.)
you (ZAM): have you tested recovery mode? specifically mounting fs and and installing zips?

giz02 said:
Yes..
flash using flashtool.
drop to fastboot (vol up)
flash boot image... reboot
I get into OS, and su tries to update from 265 to 274.. fails in os
reboot to recovery (vol down when yellow led comes on)
try installing su zip from but can't see file system.. can't mount.. busted permissions everywhere
to recover I revert to 6.0
flashtool (using customized HK .185 load)
after flash, drop to fast boot (vol up)
flash older 6883MM bin
flash recovery (3.0.2)
boot to os.
reboot to recovery
install SU (file systems mount without issue).
everything works normally at 6.0 again
---------- Post added at 09:22 AM ---------- Previous post was at 09:18 AM ----------
When you say "Works perfectly" have you gone into recovery mode and attempted file system mount, OR;
did you flashtool, then flash boot and then use phone?
I'll say that the phone booted to OS fine with this kernel, and I was able to access xreality settings, HOWEVER I was not able to use recovery mode due to numerous permissions errors. (could not mount FS.)
you (ZAM): have you tested recovery mode? specifically mounting fs and and installing zips?
Click to expand...
Click to collapse
Yep no problem..before this i stay with stock rom..then decide to root and i use this kernel..flash using flashtool and go to recovery for backup stock rom because i want to use custom rom..so no problem with mount or unmount..stock rom backup perfectly..no issue
Sent from my E6883 using XDA-Developers mobile app

Unroot and relock bootloader to install ota updates ?

Dear members
I want to update my rooted E6633 running 32.2.A.0.376 to 32.4.A.0.160 through the OTA, of course, because my device is already rooted the downloaded update couldn't be installed, the reason behind seeking for this update that I'm not able to make phone call and the phone is not able to detect the SIM cards and showing pop up error message android.phone.com has stopped repeatedly whenever I press ok and phone app crashes.
what I have done so far is through superus app I chose full unroot and the phone rebooted successfully and I have checked it with the root checker showing that the root is not installed properly
I launched the flashtool and booted the device on flashmood and selected the bootloader relock option
flashtool said that bootloader finished relocking the device, but the device is not able to boot to the normal mood whenever I push the power on button the device only vibrate or boots to flashmood when the cable is connected but when unlocking the bootloader, the device boots normally.
How to update my device without losing my current data and to fix phone application and SIMs recognition?
Do I have to fastboot the original Sony kernel and where can I find it? because I didn't make any backup
I don't mind losing root I just want to make the OTA update installed without flashing my phone and starting from the beginning.
Thank you
Notes: when the device is rooted again and when opening luckyputcher the error messages disappear and SIMs cards work fine and phone app opens normally

I will assume the reason you are not going for this is because of limited bandwidth or something along those lines.
You can either wait for someone to post a stock kernel of it but if you have a the .376 ftf you can extract the kernel using this guide (at step 3 you can flash the kernel using adb/fastboot)

Dna10 said:
I will assume the reason you are not going for this is because of limited bandwidth or something along those lines.
You can either wait for someone to post a stock kernel of it but if you have a the .376 ftf you can extract the kernel using this guide (at step 3 you can flash the kernel using adb/fastboot)
Click to expand...
Click to collapse
Thanks for your reply, not limited bandwidth but slow connection that one of the reasons, if I could extract the kernel from the firmware and flashing it without losing the data and allowing ota to be installed this will be great. Hopefully this way fixes the system errors and keeping the data and settings as it is.
Thanks again I will start following these guidelines if something went wrong surely I will sue you :laugh:

Ok I downloaded the ftf file, extracted kernel.sin
opened flashtool
I coudn't found the Dump Data option but I clicked on extract data inisted
I renamed the extracted kernel from elf to boot.img
I flashed the kernel using this command
fastboot boot boot.img
I got this error message : FAILED (remote: dtb not found)
so I relocked the bootloader and I got diffrent message : FAILED (status read failed (Too many links))
I went to flashtool and flasehd the kernel with no errors but the mobile did'nt boot, it's stuck on sony logo
what is the problem !?

kingskull said:
Ok I downloaded the ftf file, extracted kernel.sin
opened flashtool
I coudn't found the Dump Data option but I clicked on extract data inisted
I renamed the extracted kernel from elf to boot.img
I flashed the kernel using this command
fastboot boot boot.img
I got this error message : FAILED (remote: dtb not found)
so I relocked the bootloader and I got diffrent message : FAILED (status read failed (Too many links))
I went to flashtool and flasehd the kernel with no errors but the mobile did'nt boot, it's stuck on sony logo
what is the problem !?
Click to expand...
Click to collapse
Ok First Things First you should have used the command :
fastboot flash boot boot.img
Secondly to remedy to the problem flash the ftf BUT don't select anything in the wipe section, keep them all unchecked. Then you will have a stock and unrooted ROM without having lost your data.
Edit: If you were able to download that big of a file why didn't you go directly with the .106 fw? You would have had the same initial result you wanted! ::facepalm::

Dna10 said:
Ok First Things First you should have used the command :
fastboot flash boot boot.img
Secondly to remedy to the problem flash the ftf BUT don't select anything in the wipe section, keep them all unchecked. Then you will have a stock and unrooted ROM without having lost your data.
Edit: If you were able to download that big of a file why didn't you go directly with the .106 fw? You would have had the same initial result you wanted! ::facepalm::
Click to expand...
Click to collapse
I was not sure about flashing the whole ftf, I was worried if I flashed the the new 160 would cause the system to break down, so I decided to unroot and to keep my self on the safe side by unrooting, relocking bootloader and installing the stock kernel so that I will be able to update to the .160 fw through OTA
I will follow your instruction about flashing the .367 fw. I was thinking about it but I wasn't sure which options that should I select without losing the data. Should I select the whole options except the wipe section?
Thanks for your help

Don't select anything! It should look like in the screenshot I uploaded

Dna10 said:
Don't select anything! It should look like in the screenshot I uploaded
Click to expand...
Click to collapse
Hmmm yesterday before posting my last reply I flashed the firmware I only selected the kernel and nothing happened, no changes happened to the firmware except the ota size was reduced from 485mb to 187mb !?
Oh dear according to the screenshot you uploaded the ftf I downloaded is for middle east and I'm from Saudi Arabia never thought there is custom firmware for Saudi Arabia do you think that the reasone behind this boot failure is because of the difference between the installed firmware and the downloaded one?

It shouldn't pose any problems at all. Any problem arising might be of your doing. What you could do is make a Titanium Backup of your user apps and go for clean install if your problems persist.

Dna10 said:
Don't select anything! It should look like in the screenshot I uploaded
Click to expand...
Click to collapse
Ok that's great, after flashing the ftf the device boot normally but the bloody ass error still persist I can't make or receive phone calls the phone app is crashing, of course, since the root is not available luckypatcher will not solve the problem and to be honest I don't know what is the relation between this error and luckypatcher.
The funny thing after the process succeed the phone showing that the software is up to date man !!
more than that when checking software update settings app crashes
I really want to thank you for helping me, I really appreciate it :good:
my last option is downloading 160 fw and flashing it

Have you tried a different dialier app?

First Lock Bootloader Then Flash FTF File.