Database Develop

[Q] custom recovery

so i have the custom recovery clockworkmod 6.0.3.6
and when I reboot to the recovery and do what ever with it when i press reboot phone (first choose )
1 2 3
tinypic . com/r/25uu100/5
(remove the spaces)
it says: "Rom may flash stock recovey on boot. FIx?
this can not be undone
no
no
no
no
no
no
no
yes- disable recovery flash
no
no
no
++++go back+++++
so, I am wandering what should I do,
I am willing to install a custom rom but I am afriad of problems with the recovery
farther more, what if I want to use my warranty will choosing "yes" cause a problem?
in addition i noticed that on the bottom of the screen there is a massage says :
warning: no file contexts
what does it mean what should I do ?
thanks for your time

Do whatever >>>> what does that mean exactly .
Post really does not make any sense .
Does the phone boot normally ???
Warranty well root voided that

JJEgan said:
Do whatever >>>> what does that mean exactly .
Post really does not make any sense .
Does the phone boot normally ???
Warranty well root voided that
Click to expand...
Click to collapse
a. the phone is booting just fine
i am willing to insall a custom rom and i am not sure if to choise yes fix because i am afraid of problems with the phone after choosing fix:
i dont want the costum rom to install recovey over this recovery and get my recovery corrupted.
and about the root i know i can unroot my phone and use tringle away but with the recovery i dont know how to restore that to the stock
so to sum up before installing a custom rom what to choosie yes or no (on the massage )

Basically the problem is a total lack of understanding regarding rom custom roms etc .
You had better start by reading and understanding the basics before bricking your phone as you don't have a clue .
Basics read first.
http://forum.xda-developers.com/showthread.php?t=2344125
Critical you read the first two posts and understand the difference between I9300 and I9305 .
At a guess the message is due to failure to root .

JJEgan said:
Basically the problem is a total lack of understanding regarding rom custom roms etc .
You had better start by reading and understanding the basics before bricking your phone as you don't have a clue .
Basics read first.
http://forum.xda-developers.com/showthread.php?t=2344125
Critical you read the first two posts and understand the difference between I9300 and I9305 .
At a guess the message is due to failure to root .
Click to expand...
Click to collapse
how would i know if this message is due to failure to root ?
and what can i do to fix it
aka. i run root checker basic and it says i am rooted
i read the topics you told me to
and i am still not sure
is that info have somthing to do with the qustion about what to choose
Stock Recovery being reflashed after a reboot?
There is an auto recovery restore system on stock roms that will reflash the Stock Recovery on a Stock Rom. If the restore files are renamed then CWM Recovery should not be overwritten after a reboot.
You need to be rooted and then delete or rename the following files:
Quote:
/system/recovery-from-boot.p
/system/etc/install-recovery.sh

Why don't you start from the beginning as per the faqs and guides root flash recovery flash custom rom whatever .
I simply do not understand your posts they make little sense and i cannot work out where you are in the flashing process .
EG
Stock Recovery being reflashed after a reboot?
>>> No it is not flashed .
There is an auto recovery restore system on stock roms that will reflash the Stock Recovery on a Stock Rom
>> Their is no auto recovery stock includes stock recovery.
If the restore files are renamed then CWM Recovery should not be overwritten after a reboot.
>> no idea at all what this is and you do not rename files .
Are you sure you are in the right forum ?? this is I9305 forum .
You have an EFS backup ???

JJEgan said:
Why don't you start from the beginning as per the faqs and guides root flash recovery flash custom rom whatever .
I simply do not understand your posts they make little sense and i cannot work out where you are in the flashing process .
EG
Stock Recovery being reflashed after a reboot?
>>> No it is not flashed .
There is an auto recovery restore system on stock roms that will reflash the Stock Recovery on a Stock Rom
>> Their is no auto recovery stock includes stock recovery.
If the restore files are renamed then CWM Recovery should not be overwritten after a reboot.
>> no idea at all what this is and you do not rename files .
Are you sure you are in the right forum ?? this is I9305 forum .
You have an EFS backup ???
Click to expand...
Click to collapse
I read the REF you told me to,
yes am sure i am on the right fourm, i do own i9305
I have EFS backup
+i didnt copied the the rom zip to the sd card yet,
+i wish i could send you a picture of the Recovery its just that the site does not allow me to upload files yet,
the things stoping me from flashing custom rom is that massage appearing when i exit the recovery and the massage on the bottom
please give me your email or something and i will send you the picture

Idolized said:
I read the REF you told me to,
yes am sure i am on the right fourm, i do own i9305
I have EFS backup
+i didnt copied the the rom zip to the sd card yet,
+i wish i could send you a picture of the Recovery its just that the site does not allow me to upload files yet,
the things stoping me from flashing custom rom is that massage appearing when i exit the recovery and the massage on the bottom
please give me your email or something and i will send you the picture
Click to expand...
Click to collapse
Use Odin to flash recovery, or heimdall if you are running Linux.
You can already copy or download su zip ( in case you want stock rooted.) or custom ROM to your sdcard, so that you have it ready for flashing.
Sent from my GT-I9305 using Tapatalk 4

Use this method:
http://forum.xda-developers.com/showthread.php?t=1942150
Why use this Root Method? Well the main reasons are:
- You have a complete Odin Flashable ROM Package.
- No Insecure Kernels are used or required.
- You can flash these packages on Non-Rooted devices
- The Binary Flash Counter will NOT increase when flashing these ROM Packages.
- The Red Exclamation Mark will NOT appear at boot up.
- And finally, you only have to flash one file in Odin and you have a complete firmware including Root Permissions.

[Q] Stock Android Backup

Hlo Everyone,
I Am a Newbie To Custom Android Roms on Galaxy S Advance .I am on Stock JB with Cocore Kernel And Twrp . I Want To ask if i make a nandroid backup of stock android and try to install other custom rom ,can i revert back to stock jb via backup in case problem arises ...
I had tried this on a different phone but at that time it said md5 sum mismatch .
So Simply I am asking u can i revert back to stock jb via twrp recovery ...
Waiting for reply From GS Advance users ...

SultanRTS said:
Hlo Everyone,
I Am a Newbie To Custom Android Roms on Galaxy S Advance .I am on Stock JB with Cocore Kernel And Twrp . I Want To ask if i make a nandroid backup of stock android and try to install other custom rom ,can i revert back to stock jb via backup in case problem arises ...
I had tried this on a different phone but at that time it said md5 sum mismatch .
So Simply I am asking u can i revert back to stock jb via twrp recovery ...
Waiting for reply From GS Advance users ...
Click to expand...
Click to collapse
That mismatch happen because of bad backup I think. You can if you are on other stock based or on CM10.1. For CM10.2 and CM11 ROMs you must repartiton preload partition to be able to do that. HOW.

SultanRTS said:
Hlo Everyone,
I Am a Newbie To Custom Android Roms on Galaxy S Advance .I am on Stock JB with Cocore Kernel And Twrp . I Want To ask if i make a nandroid backup of stock android and try to install other custom rom ,can i revert back to stock jb via backup in case problem arises ...
I had tried this on a different phone but at that time it said md5 sum mismatch .
So Simply I am asking u can i revert back to stock jb via twrp recovery ...
Waiting for reply From GS Advance users ...
Click to expand...
Click to collapse
It is possible.
that md5 sum mismatch you had on different phone was most probably related to corrupted backup file - not related with current ROM installed as long as backup is not cross recovery (CWM / TWRP).
I have lost one backup same way due to corrupted files.
To be sure that it will work you can try to restore backup just after it was created - if it will work, then it should work later on.
if you will be trying CM11 revert procedure is a bit more tricky (as /preload partition is used differently than in stock):
it might need odin flash of stock, install CoCore, restore backup
EDIT ... or faster way presented by shut_down ;]

th3cr0w said:
It is possible.
that md5 sum mismatch you had on different phone was most probably related to corrupted backup file - not related with current ROM installed as long as backup is not cross recovery (CWM / TWRP).
I have lost one backup same way due to corrupted files.
To be sure that it will work you can try to restore backup just after it was created - if it will work, then it should work later on.
if you will be trying CM11 revert procedure is a bit more tricky (as /preload partition is used differently than in stock):
it might need odin flash of stock, install CoCore, restore backup
EDIT ... or faster way presented by shut_down ;]
Click to expand...
Click to collapse
I had tried this on galaxy fit ,but there also i got same problem and i had to use odin to get stock back ... i don't want to go over the same pls help me.my phone is hanging a lot and i cant stay on stock so pls help me

To be sure it is not corrupted backup file you can perform restore backup just after it was created.
If it is corrupted due to some reason it will not work from the beginning.
If it go smooth you are sure that you got correct backup - just store it some place safe (not on crappy SD that might go corrupt over time or sth ...)
At that point it is safe to assume it will work as system restore point from any custom ROM back to state of when it was made (official JB with cocore and all your apps / contacts / messages / etc already in place) - with exception of CM10.2 and CM11 ROMS (and those that are based on them) as explained already - those ROMs would need one extra step before reverting (but it is still possible, just not as straight forward as on other ROMs)

[Q] Questions before flashing custom ROM

I am planning to flash a custom rom on my phone (for the first time).
Model : Xperia SP(C5302)
Build : 12.1.A.1.205 (Stock) running JB 4.3 with LB
I have rooted my phone using the towelroot method and installed supersu. I have also installed custom recovery from here http://forum.xda-developers.com/showthread.php?t=2649923
I am planning to flash this custom rom http://forum.xda-developers.com/xperia-sp/development/cyanogenmod-11-locked-bootloader-users-t2868398
So I have a few questions that I am not clear about(even after searching the forums). And sorry if they are dumb. I really want to understand as much as possible before flashing roms.:fingers-crossed:
1. After reading the thread of my recovery, from what I understand, the recoveries are installed in /system. But on OP of the custom rom, I am about to install, there is an instruction to format /system before flashing the rom. So my question is if I format the /system partition, won’t my recoveries be removed (by the recoveries itself) before I even flash the rom?
2. Also will the recovery still be available to me if say I enter bootloop for some reason during flashing the rom?(asking for the same reason as above that is wiping my /system should also remove my recoveries)
3. Does CM 11 come with any inbuilt custom recovery? If not can I install the one I am already using (assuming installing a custom rom will remove my installed recoveries)?
4. Say I screw up during the flashing procedure. So if I want to rectify this I should first flash the stock .205 ftf, root, install a recovery again and then restore using the nandroid backup. Am I correct?
5. Is it necessary to wipe cache and dalvik cache before flashing rom? I see this instruction in some roms but not in others. And dalvik should be wiped after flashing rom and gapps, right?
6. Should I install supersu again after I flash the rom. I read in an article that it causes problems with CM. As far as I know CM11 comes pre-installed with superuser. But it also supposedly causes some problems.
7. Is it safe to restore user app+data, messages and contacts backed up using Titanium backup on a newly flashed rom? I have seen conflicted views on this.
Click to expand...
Click to collapse
And that’s it for my questions (for now at least... ).
A Big Thanks in advance for all your helpful answers

Prat92 said:
I am planning to flash a custom rom on my phone (for the first time).
Model : Xperia SP(C5302)
Build : 12.1.A.1.205 (Stock) running JB 4.3 with LB
I have rooted my phone using the towelroot method and installed supersu. I have also installed custom recovery from here http://forum.xda-developers.com/showthread.php?t=2649923
I am planning to flash this custom rom http://forum.xda-developers.com/xperia-sp/development/cyanogenmod-11-locked-bootloader-users-t2868398
So I have a few questions that I am not clear about(even after searching the forums). And sorry if they are dumb. I really want to understand as much as possible before flashing roms.:fingers-crossed:
And that’s it for my questions (for now at least... ).
A Big Thanks in advance for all your helpful answers
Click to expand...
Click to collapse
First of all, I am only explaining the one I know about
1. Well, wiping the system will remove the recovery. That's why you'll have to flash the ROM after wiping the system. Do not ever reboot the phone after wiping the system but haven't yet flashed the ROM zip, else you'll have to do more work to flash the Stock ROM. This is due to the fact your phone does not have an OS to boot into! When flashing the ROM zip, the recovery will be automatically installed.
2. This is based on luck, most of time you'll end up unable to boot into anything. A fix is to flash the Stock ROM again.
3. Every ROM has recovery built with it (unless stated otherwise in the thread)! Upon flashing, it will be automatically installed too.
4. The methods you mentioned is correct. However, only restore the nandroid backup if you want to stay on stock. You could always retry to flash the ROM again. Nandroid backup is an image backup of your android. If you restore your nandroid backup, you'll end up with your previous version of android (like the way before you started flashing the ROM)
5. Wiping /cache and dalvik-cache is a really good practise! It doesn't really matter when you will need to wipe them, but personally I wipe them all before flashing the ROM. Wiping /data and performing a factory reset through recovery is recommended if you're coming from a different ROM. That's why backing up user apps through TiB (Titanium Backup) is recommended for you to easily get your installed apps back. Remember, nandroid backup and apps backup from TiB is different to each other.
6. No, this might cause extreme conflicts. No, I am using SuperUser as long as I have used CM. It never fails to give root permission at all despite the hatred I sense in some apps that overly-recommends SuperSU.
7. Of course it is very safe to restore them backups with TiB. However, based on my experience, messages and contacts were unable to be restored due to the difference in ROM version. I don't know if anyone else faces the same problem as mine. As of this, I really recommend your contacts to be synced with Google.
Heads up!
Based on this post, the dev of the ROM you wanted to flash, MrSteve555, recommends PhilZ when flashing the ROM.

TechnoSparks said:
First of all, I am only explaining the one I know about
1. Well, wiping the system will remove the recovery. That's why you'll have to flash the ROM after wiping the system. Do not ever reboot the phone after wiping the system but haven't yet flashed the ROM zip, else you'll have to do more work to flash the Stock ROM. This is due to the fact your phone does not have an OS to boot into! When flashing the ROM zip, the recovery will be automatically installed.
2. This is based on luck, most of time you'll end up unable to boot into anything. A fix is to flash the Stock ROM again.
3. Every ROM has recovery built with it (unless stated otherwise in the thread)! Upon flashing, it will be automatically installed too.
4. The methods you mentioned is correct. However, only restore the nandroid backup if you want to stay on stock. You could always retry to flash the ROM again. Nandroid backup is an image backup of your android. If you restore your nandroid backup, you'll end up with your previous version of android (like the way before you started flashing the ROM)
5. Wiping /cache and dalvik-cache is a really good practise! It doesn't really matter when you will need to wipe them, but personally I wipe them all before flashing the ROM. Wiping /data and performing a factory reset through recovery is recommended if you're coming from a different ROM. That's why backing up user apps through TiB (Titanium Backup) is recommended for you to easily get your installed apps back. Remember, nandroid backup and apps backup from TiB is different to each other.
6. No, this might cause extreme conflicts. No, I am using SuperUser as long as I have used CM. It never fails to give root permission at all despite the hatred I sense in some apps that overly-recommends SuperSU.
7. Of course it is very safe to restore them backups with TiB. However, based on my experience, messages and contacts were unable to be restored due to the difference in ROM version. I don't know if anyone else faces the same problem as mine. As of this, I really recommend your contacts to be synced with Google.
Heads up!
Based on this post, the dev of the ROM you wanted to flash, MrSteve555, recommends PhilZ when flashing the ROM.
Click to expand...
Click to collapse
Thanks for such detailed answers. That cleared most of my doubts
Just some last few questions(promise!)
1. If wiping /system does remove the recovery before I install the rom, how is it possible to access it even to flash the rom? Shouldn't it like just close right when I wipe /system. Or does it not work like that?
2. Just to be sure the nandroid backup I made on my stock rom won't work if I later try to flash it through recovery while using CM,right?

Prat92 said:
Thanks for such detailed answers. That cleared most of my doubts
Just some last few questions(promise!)
1. If wiping /system does remove the recovery before I install the rom, how is it possible to access it even to flash the rom? Shouldn't it like just close right when I wipe /system. Or does it not work like that?
2. Just to be sure the nandroid backup I made on my stock rom won't work if I later try to flash it through recovery while using CM,right?
Click to expand...
Click to collapse
1. Wiping system wont close the recovery at all. It still runs and you can still navigate within it. But remember do not reboot unless you've flashed the ROM! The mechanism of how the magic works is yet to be acknowledged. So I can't tell why it doesn't closes upon wipe. My best guess here is that the recovery might be running on a temporary partition perhaps. I hope a developer see this post and explains the magic.
2. Nandroid backup works all the time (if they are no errors when you are creating them). Nandroid backup is simply a backup of your whole device. If you're on CM, restoring nandroid backup will get your phone back to the way when you attempted the nandroid backup (stock ROM, rooted, and triple recoveries installed). Nandroid backup is useful when you're about to try something that may damage your ROM, without doing so much work to restore your device.
Say, you created a nandroid backup in cwm in which Cyanogenmod was installed. And then you flashed something afterwards. If that "something" damages the ROM and gives you bootloop, you can simply flash Stock ROM, root it again, install recoveries again, and restore the nandroid backup. Then, voilà, cyanogenmod is back. This will simplify your work rather than flash CM again, then gapps, then restore your apps and all those other things that will consume so much time
So a new nandroid backup will backup the whole device, in a form of an image.

Issues with latest official TWRP 2.8.7.0 for Galaxy S3 4G I9305 and how to fix it

Hi everyone,
some who frequently read the forum may know already that there are issues with the latest official TWRP for the Galaxy S3 LTE. The recovery partition on the Galaxy S3 LTE is too small for the latest recovery provided by TWRP. The partitions are messed up, you won't be able to mount /system and /data. Some users couldn't even flash their preferred ROM. As of now the buggy recovery is getting fixed.
I am not responsible for any damage, losing data or weird behavior you encounter while doing one of the following steps. As reported by several users step 1 was the way for them to fix their phone. Be sure of what you're doing. Make sure you know how to boot into recovery/Download Mode to do these things mentioned here and how to use odin. If not, XDA users have provided several guides. Use the search.
If you already flashed the faulty recovery, flashed a custom ROM with it and your phone ends up in a bootloop there are several ways to fix this issue.
1. Via odin and official stock firmware - please note: You might lose all your data you have on your internal storage
Download the latest official Samsung firmware from sammobile or look on XDA for provided stock ROMs by the AMCHA team. Boot your phone into Download Mode and flash the official firmware via odin. If you're done, reboot into stock recovery (which will be provided after flashing the stock firmware), perform a factory reset and let your phone boot up once. First boot might take some time, so be patient. Although the first boot might not be needed, do it anyway to see if your phone is still in a bootloop or suffers from other damage. If the phone boots up fine reboot into Download Mode again, flash TWRP 2.8.5.0 or any other latest custom recovery (preferably the recovery the maintainers recommend in their development threads) and flash your preferred ROM. Your phone should now work as it should.
2. Via stock based custom ROM (if you haven't flashed any ROM via TWRP 2.8.7.0 already - please note: You might lose all your data in this process as well
Some users managed to get their phone working by flashing a stock based custom ROM like AMCHA or N4 Elite. If you only flashed the buggy recovery and didn't flash a custom ROM this way should be the step you should try first. Download any stock based custom ROM and flash it via the faulty one. If your phone boots up fine, boot into Download Mode and downgrade recovery or use any other recovery recommended for the ROM you're using. If you encounter issues or weird behavior with your phone go with step 1.
3. Via flashing a fixed TWRP 2.8.7.0 - please note: You might as well lose data
In this option you can flash a fixed version of TWRP which an user of XDA has provided. Many thanks to StdBarbarossa for his work. Unfortunately in his build you cannot mound your SD card via PC as it's not working at the moment. Make sure you have all the needed files already on your SD card. For some users this way was working for them. Boot your phone into recovery, click on install, change from .zip to .image, choose the Alpha17.img, install it by swiping and reboot your phone into recovery. Perform a wipe (preferably a factory reset, cache and dalvik cache might be working too) and see if your phone boots up fine. Here the same: if you're still facing issues go with step 1.
Link for the TWRP Alpha17 2.8.7.0 https://drive.google.com/file/d/0B-tlso-zNf9NMWlMMFpiYmYwTzA/view
I have gone through the same issue. In my case I only managed to get my phone working again with step one as I had flashed a custom ROM via the buggy recovery and ended up in a bootloop. As stated, others have managed to fix their phone with either option 2 or 3.
Link for the fixed TWRP is provided in the spoiler.
If you're not sure about something ask here first before you might brick your phone. If you know any other way to fix this issue feel free to post it here.

A cry for help

Hello all,
Firstly I would like to thank all the great people here, I've been struggling for hours with my dead Xperia Z and the amount of dedication and support I've found so far across all the members here is really impressing.
Let me first illustrate my case.
Firstly, I came here to root my phone and install a custom rom ships with Android N 7.1.2 (Resurrection Remix), I did went through all the newbies/how to threads and I did successfully ended up with Android N on my phone
Unfortunately, the device was not working probably in case of incoming or outgoing calls. No ringtone (already selected from Settings >Sound - played and heared), while in call it keeps ending the call unexpectedly, sometimes it feels very laggy that I couldn't even tap on anything. So I decided to give up until I found another rom that ships with Android N (XOSP), after successfully installing the rom, it starts out very smooth and I tested everything and it was ok, until yesterday the same issue still persists plus my device mic is not working no one can hear me while I'm talking neither from a headset mic nor the device mic. Finally I gave up and decided to rollback to the old lolipop stock rom.
Here's comes the current problem:-
1- I did flash 10.7.A.0.222 Customized MEA using flash tool and it's flashed successfully.
2- I'm now stuck with a dead black screen after sony logo.
I tried everything, changed the flashtool version, downloaded other ftf kernel file, used Xperia Companion and non of them worked for me. I did also tried what's listed in here https://forum.xda-developers.com/xperia-z/general/disaster-recovery-getting-z1-zu-z-zl-to-t2229250
I only can boot into fastboot or flashboot mode
I cannot copy files to my phone as it never appears as a storage media in my computer.
Any help will be much appreciated
Sorry for the long post

I never had this problem before, but have you try other ftf with lower android version like KK?
I see this problem on someone, everyone of them had this problem when they try to revert back to stock LP from N. Then someone suggest to flash KK ftf. You should try this if you haven't try this.
Sorry if my English is bad.
UPDATE:
when the first 7.0 nougat custom rom came, I'm on 5.1.1 rom with XZDual recovery. I made a backup for this rom and flash the 7.0 N rom only for trial then revert back to stock 5.1.1 that I backup before. Chippa's rom always came with latest built-in recovery so when I upgrade to nougat rom the XZDual recovery also lost (I don't have FOTA recovery, lol).
The step I made to revert back to stock is to do a FULL wipe of the phone (cache, davlik cache, data, system, AND internal storage), not a regular full wipe (without internal storage).
I put my backup stock rom file to my external sdcard (because the internal storage got wiped) and begin to flash, BUT NOT reboot into system, I reboot the phone to recovery instead (because I think the 5.1.1 rom works better with old TWRP so I reboot the phone to recovery first to get the old XZDual recovery).
After phone enter the old TWRP, I do a FULL wipe (cache, davlik, data, system, internal storage) once again to make sure everything OK, then flash the stock rom once again.
aand... it works. I did it 3-4 times to test new build of 7.0 n rom and never have any problem of reverting back.
But, I never test this method on newest 7.1.1 rom or 7.1.2 rom.
since you can't boot on LP rom, then try to flash KK rom.
Just install phone driver, flashtool, and download the KK ftf.
I'm sorry I can't provide you the full instruction because I never had this problem before, but you can search for this on N rom thread (the rom developed by Chippa). There is a guide made by someone on that thread.

Zerikwan said:
I never had this problem before, but have you try other ftf with lower android version like KK?
I see this problem on someone, everyone of them had this problem when they try to revert back to stock LP from N. Then someone suggest to flash KK ftf. You should try this if you haven't try this.
Sorry if my English is bad.
UPDATE:
when the first 7.0 nougat custom rom came, I'm on 5.1.1 rom with XZDual recovery. I made a backup for this rom and flash the 7.0 N rom only for trial then revert back to stock 5.1.1 that I backup before. Chippa's rom always came with latest built-in recovery so when I upgrade to nougat rom the XZDual recovery also lost (I don't have FOTA recovery, lol).
The step I made to revert back to stock is to do a FULL wipe of the phone (cache, davlik cache, data, system, AND internal storage), not a regular full wipe (without internal storage).
I put my backup stock rom file to my external sdcard (because the internal storage got wiped) and begin to flash, BUT NOT reboot into system, I reboot the phone to recovery instead (because I think the 5.1.1 rom works better with old TWRP so I reboot the phone to recovery first to get the old XZDual recovery).
After phone enter the old TWRP, I do a FULL wipe (cache, davlik, data, system, internal storage) once again to make sure everything OK, then flash the stock rom once again.
aand... it works. I did it 3-4 times to test new build of 7.0 n rom and never have any problem of reverting back.
But, I never test this method on newest 7.1.1 rom or 7.1.2 rom.
since you can't boot on LP rom, then try to flash KK rom.
Just install phone driver, flashtool, and download the KK ftf.
I'm sorry I can't provide you the full instruction because I never had this problem before, but you can search for this on N rom thread (the rom developed by Chippa). There is a guide made by someone on that thread.
Click to expand...
Click to collapse
Thank you so much for your reply. I will try it out. I really appreciate your contribution and I will keep you updated