Database Develop

[Q] Deodexed Stock XXJVT - root problem

I installed Deodexed Stock XXJVT stock rom from here, and everything went well. Than I wanted to root it. I did that with this kernel CF-Root-XX_OXA_JVT-v4.3-CWM3RFS.zip, and it also went well. After that I wanted to "restore to factory settings" - format my user data. When I tried that, phone rebooted, than went to Android system recovery, and ask me to choose one of the options (see picture). I tried "wipe data/factory reset", but I got error messages from picture bellow. Tried again with same result.
Than I flashed phone with stock rom and stock kernel AGAIN. Tried to restore to factory settings, and 1. phone DIDN'T go to system recovery, and 2. erased all data WITHOUT any errors and with complete success.
Than I tried AGAIN (for the second time) to root with same kernel (again it went well). Than AGAIN tried to restore to factory settings (erase private data), and AGAIN problem mentioned above happened.
Now I have stock rom and stock kernel again. I need root for some things, but I don't know how to solve this problem. Could someone please help me with this?
Thanks.

hello
use odin to flash it see here
original rom xxjvt : http://www.techgom.com/2011/10/install-235-gingerbread-xxjvt-on.html
how to root it : http://www.techgom.com/2011/10/cf-root-for-gingerbread-235-xxjvt.html
-----
you must translate page to english with google chrome

You've already done a hard reset, so just install cf kernel again. Most instructions say wipe before flashing, you have still removed previous files etc
Sent using TCP/IP

Thanks both for quick reply.
@seghier
Thanks for these instructions. I did slightly different process. Maybe this why I got all these errors. I did use ODIN, but I flashed rom with "re-partition" checked (instruction says it shoudn't be checked), and also I used PIT while I am doing this and this instruction says I should do this without it. Check attachemnt picture for hw I did this.
Also, I did root with only PDA, and this tutorial says I should also PIT file included. See attachment for how I did this root.
I am a newbie so I am not sure if this could cause these errors? And did I do something wrong flashing and rooting phone my way?
Should I do this again following this two tutorials or not?
Also I am not sure what is DEODEXED means? Is there any differences between regular stock rom, and this DEODEXED one?
I just want regular stock rom and regular root.

oxeded rom is the original rom from samsung / deodexed is rom can be modified by users and you find in xda forums the difference
the method in photo is right
or you can install deodexed rom from here and the flash very easy :
http://www.multiupload.com/E9AT600ZUC
than use the files like see in image without pit or repartition
http://img707.imageshack.us/img707/1808/ppppas.png

Thanks, I will try now.

I still checked "re-partition" because I was using before DEODEXED, and now I am flashing ODEXED rom, so I thought maybe it is a different partition type. Is this ok? Flash went okay.

hello
when you find pit file repartition cheked automaticly
tell me if you success with flashing

Yes I did, thank you. But this problem with unable to restore to factory settings, after do root, still exist, even on ODEXED rom. It is deffinatelly some bug.

if you have problems you can format your sd card but first save all your files and data files using cwm : than create backup
you can try other deodexed rom from : s i9000 developement
i used the original deodexed rom and work fine

I don't have external SD card, just internal memory. Backup isn't problem. I wanted to delete all my personal data, but this error happenes. Did you try erase personal data AFTER did a root?

try this
settings ----- sd card and phone storage-------usb storage : format usb storage
and that remove all your files : music photos ...etc
-for hard reset try this : *2767*3855#
-factory data reset : *#*#7780#*#*
save all your photos and music ....

I already bring back some things, and also I managed to erased all that before doing root, so I won't experimenting anymore for now. Thak for your help. I will try this next time I want to clean my phone completly.

i hope that work for you
and deodexed rom more better because you can add new theme or launcher or flash update without limit than oxeded rom
good luck

Thanks.

try a new kernel

working now? please give a feedback ?

Like a wrote before. DEODEXED and ODEXED both work and I CAN restore to factory settings. After do root, it can't ba done anymore. I tried every possible combination, but result is same, so I guess that can't be done (which isn't so importante to me because I already restored to factory settings before apply root).
I didn't try other kernel (don't know either where to find other kernel), because I already installed programs, made personal settings, so I don't want again to wype all that.
If someone of you could try this it would be okay.

try semaphore kernel is very nice :
http://forum.xda-developers.com/showthread.php?t=1112908
use this application to install kernel :
https://market.android.com/details?id=neldar.sgs.kernel.flasher
and this application for save all your application to external card and you can restore it :
http://fr.appbrain.com/app/app-backup-restore/mobi.infolife.appbackup
--------
and don t forget to make backup with cwm

I am not so experienced about all this. What is difference between semaphore kernel and that other kernel I used for root?
Also if someone else could try this, who need to clean phone anyway, because I just make everything to work OK, so I don't want to experiment again.

[Q] Questions after installing ICS

Ive installed ICS N7000XXLQ2_N7000XXLPT_N7000CPWLP4_HOME.tar replacing my old N7000XXKL3_N7000ODDKL1_INU. I have followed all the steps from STOCK roms page. But i have a few questions now:
1) I have performed a data and cache wipe, but i then turned the phone on back to check my CSC, i skipped all the Welcome to Android steps and just dialed up the CSC check code. Then i turned off my phone to install ICS. Could it smhow affect my phone in a negative way?
2) Although I have performed the cache and wipe data my Android folder Data still has all the Data files from games and apps which i had in my previous software. Is it normal?
3) when first launching the ICS even after a few updates I could not run any new app. Everything would keep crashing. Then I went back into the mode and did a factory reset and wipe thingie again. That helped and i can run newly installed apps. Need your comments about this situation.
Grateful,
QVA

1. Yes. Any wipe or restore on ics stock kernel can cause damage. You won't knoe until it's bricked.
2. Actually i had the same experience under lpy as this when it wouldn't clear the sd card when selected. My interpretation was that ics sd is mounted in a different section to gb and maybe they hadn't updated the kernel to look for this section? I'm probably way off there. I ended up doing a full wipe while connected to pc.
3. Mass fc's seems to be common. Firstly check your dpi setting, make sure it's above 213 as tablet not supported. If that doesn't solve, do a factory reset on a safe gb kernel before upgrading to ics again. Don't do any restores or wipes under ics kernel!
please hit thanks if i helped

Questionvsanswer said:
Ive installed ICS N7000XXLQ2_N7000XXLPT_N7000CPWLP4_HOME.tar replacing my old N7000XXKL3_N7000ODDKL1_INU. I have followed all the steps from STOCK roms page. But i have a few questions now:
1) I have performed a data and cache wipe, but i then turned the phone on back to check my CSC, i skipped all the Welcome to Android steps and just dialed up the CSC check code. Then i turned off my phone to install ICS. Could it smhow affect my phone in a negative way?
2) Although I have performed the cache and wipe data my Android folder Data still has all the Data files from games and apps which i had in my previous software. Is it normal?
3) when first launching the ICS even after a few updates I could not run any new app. Everything would keep crashing. Then I went back into the mode and did a factory reset and wipe thingie again. That helped and i can run newly installed apps. Need your comments about this situation.
Grateful,
QVA
Click to expand...
Click to collapse
How did you do it? I would have used PC Odin to do the flash, so you have a clean install.
If you already had a rooted ICS with CWM recovery, you would be best advised to either go back to a stock GB, root it and then flash the ICS of your choice after a full wipe.
Or you could use Abyss 4.2 to flash from an existing rooted ICS ROM.

now it s getting better
smaiitm said:
How did you do it? I would have used PC Odin to do the flash, so you have a clean install.
If you already had a rooted ICS with CWM recovery, you would be best advised to either go back to a stock GB, root it and then flash the ICS of your choice after a full wipe.
Or you could use Abyss 4.2 to flash from an existing rooted ICS ROM.
Click to expand...
Click to collapse
now after a factory reset and after usb storage format to remove all those files that were left behind durin softwasre reinstallation ICS seems to be working fine. No more fcs, it is working faster than Ginger. I used odin( the pc ver) to flash it.

should i do smth?
Games that used to lag are now not lagging or lag less. Sometimes menu gets a lag spike for half of a sec or smth but i dont mind that. So after that clean up and wipe which left sd files undeleted and then they got removed with a mass storage format i should not worry anymore? everything is fine and wont have any bad result in the future? I have a fully functional ics?

It looks like it. Its probably worth not doing any further wipes or restores under ics if you're happy with the performance. Samsung will be releasing updated kernels within hopefully a month or so, best wait till then.
please hit thanks if i helped

[Q] the process com.android.phone has stopped unexpectedly

I'm currently running the latest CM9 on it with moboot... It seems like every time it boots up it pops up with that error message and literally won't go away and you have to reboot the device.. the only way I've found to temporarily fix it is to just wipe cache.... but it always comes back.
Is there any way to prevent this from popping up? It happened when I was on Classicnerd BUTTA too.

Wipe the system and caches, then reflash

I had this problem as well a while back. Wiping caches and reflashing the ROM worked for me.

And you guys didn't have the problem again, after that?

Help manually moving contacts and choosing a JB ROM.
If a pro could help me out I would appreciate it very much. I have been trying to move from a dangerous ICS build to JB and I am having this same problem.
My N7000 previously had this on it:
android 4.03
radio 19220zclp6
kernal version 3.0.15-i9220zclp1-cl131270 (bad ics kernal)
build number midnote 2.0 iml74k.zclp1
So I used ODIN to flash it to a GB rom but I got the com.android.process error and my phone would lock up.
So then I found this link http://forum.xda-developers.com/showthread.php?t=1424997 and flashed this ROM "N7000UBLR3 N7000UVOLR1 - Download - Argentina" from the bottom of the page. I wiped only the the cache (not the phone reset) and flashed it again but I still get the process error and phone locking up. I don't even know if this ROM is a safe ROM!!
Am I even on a safe kernal now? kernal n7000ublr3-cl890184 build imm76d.ublr3
What I need help doing is the following.
1. Before doing a full wipe, I need to either manually save my contacts to my PC or back them up. (no apps work but my pc can browse my phone) If I knew where my contacts were located, maybe I can manually copy them to my pc? So any help saving data from a partially unusable phone would help.
2. Flash to a safe GB rom, so I can then do the full wipes safely and then flash to a stable JB rom. (I have no clue which roms to choose here and need help).
Thanks for any help..

Need help bricked phone :(

i recently flashed the eXistenZ Ultra 2, and im sure i did everything fine, after flashing the rom in recovery and flashing suprsu and wifi fix, i powered off the phone, and powered on but sony logo has apeared until now , and welcoming`s sounding 999..times. i cant turn it off, or i should say i cant do anything.
please help,

After flashing ROM and the fixes you should flash the 12.1.A.0.266 Firmware with FlashTool!
If problem still persists:
http://xda-university.com/as-a-user/how-to-recover-from-a-bootloop
Take a look at this site A recovery would be quite useful, but I think the kernel of eXistenZ ROM has one. If not, you'll find one in the development section. Otherwise, use the ADB as solution.
Good luck

Thanx for the post!
I used force shut down and then flash the 254 rom, and did all those things, and the problem occured again.
does the recovery software have to be the touch recovery? I use CWM v6 that enables with volume +.
and i use SuperSU fix.zip rather than superUser.zip and generally i flash rom, supersu fix.zip and wifi fix.zip. i flashed those three, before first booting, do i have to boot first before flashing wifi fix.zip?

eefathi said:
Thanx for the post!
I used force shut down and then flash the 254 rom, and did all those things, and the problem occured again.
does the recovery software have to be the touch recovery? I use CWM v6 that enables with volume +.
and i use SuperSU fix.zip rather than superUser.zip and generally i flash rom, supersu fix.zip and wifi fix.zip. i flashed those three, before first booting, do i have to boot first before flashing wifi fix.zip?
Click to expand...
Click to collapse
I think you need to flash 12.1.A.0.266 instead of 12.0.A.2.254 after flashing ROM. You could also wipe data, cache and dalvik cache, reflash eXistenZ ROM and SuperSU fix (or SuperUser but SuperSU should be ok), shut down the phone with the option in recovery and then flash the 12.1.A.0.266 with FlashTool.
It doesn't matter which recovery you take. Use the one you like best. I'm not quite sure, but to go sure, please flash the wifi fiz.zip after first boot up!

Schokonuss said:
I think you need to flash 12.1.A.0.266 instead of 12.0.A.2.254 after flashing ROM. You could also wipe data, cache and dalvik cache, reflash eXistenZ ROM and SuperSU fix (or SuperUser but SuperSU should be ok), shut down the phone with the option in recovery and then flash the 12.1.A.0.266 with FlashTool.
It doesn't matter which recovery you take. Use the one you like best. I'm not quite sure, but to go sure, please flash the wifi fiz.zip after first boot up!
Click to expand...
Click to collapse
thanx again,
i flashed the 266 kernel before the first boot, and the rom runs correctly,
but ive got some new problems:
1. performance, when i click on performance, it closes unexpectedly and says it has stopped.
2. i used go backup for backing up from data in 4.1, but in this rom i restored my apps,the apps installed correctly but goBackup says the data restoring successfully finished , but the data didnt restored, by the way at the time i backed up from my apps&data, i swapped memories with that linux code that this forum did.

eefathi said:
thanx again,
i flashed the 266 kernel before the first boot, and the rom runs correctly,
but ive got some new problems:
1. performance, when i click on performance, it closes unexpectedly and says it has stopped.
2. i used go backup for backing up from data in 4.1, but in this rom i restored my apps,the apps installed correctly but goBackup says the data restoring successfully finished , but the data didnt restored, by the way at the time i backed up from my apps&data, i swapped memories with that linux code that this forum did.
Click to expand...
Click to collapse
You're welcome
1. Do you have SuperSU installed? On AOKP ROM I'm running it asked for superuser permission for ROM Control (the control center implemented in the settings of the ROM). Maybe it'll ask you if SuperSU is installed. Otherwise, because it is after the first boot it needs to rebuild cache and so on.. If problem persists after reboot, just use an other clock speed controler (No-frills CPU, SetCPU..)
2. If you did that at the same time, maybe Go Backup didn't really backup your data. Try again, if it doesn't work and if you have a nandroid backup (backup from recovery) you can go into recovery, then to advanced restore and restore data. Otherwise your data is unfortunately gone I think :/
PS: I prefer Titanium Backup

Install Stock Firmware (JB 4.1.2) without Odin

Hi everyone, I'm here because i have problems with my phone and i want to fully restore. To do this i would like to install a new ROM, but from what i've seen, to install a ROM is necessary to have the stock JB 4.1.2 on the device, while i have CyanogenMod 11 (4.4.4) running.
This wouldn't be a problem if i could use Odin, but apparently my USB port has something wrong, and i cant connect my phone to any PC, so i cant flash in that way. Luckly i can access to the custom recovery (CWM), so i 'd like to ask if there is a way to flash the stock firmware via CWM.
Instead, If I can install a ROM starting directly from CM11 without restoring stock JB, or if i'm missing something important, let me now, i would appreciate a lot
Thank you in advantage. (Excuse se for any misspelling, I'm not English)

What kind of problems do you have?
If you can access CWM recovery there's no need to install stock in order to flash a new ROM, just be sure to wipe caches and data before installing the new one to avoid related bugs; and you will probably need to update the recovery to TWRP if you want to flash one of the most recent ROMs
It's always recommended to create a backup before everything else.
Peace

Hi, thank you for then anwer Well, it would be a long list of problems ^^ The biggest one though is the fact that if I'm in AeroMode everything works as always, sometimes bugged but nothing exceptional, but in the moment i switch AeroMode off and digit the SIM pin, the phone turns off and then enters in a bootloop(vibrating every 1 minute like before entering the main window, but it remains stuck) that is solvable only pressing for 8/10 secs the POWER button and restarting it. I can't have a phone which is not able to make voice calls :/ Back to the problem, so if i'm not misunderstanding anything, I dont need to reverto to stock and then reflash the new ROM? Because, for example, in the main page of CM13 it's written:
ROM Firmware Required: Stock + CWM compatible with KitKat
and that's the origin of my post... But in case, which wipe should i do? Dalvik + wipe data/factory reset?

OK, the thing is that you need stock + CWM at minimum, it means you can't install it if you are on gingerbread; but if already installed something higher than 4.1 you can go from there.
First create a backup then wipe cache, wipe dalvik, factory reset and install your preferred ROM

Ohhh, that makes sense.... Ok, so i will wipe what you said and flash the new ROM! You saved me a lot of time, thank you so much!