Related
I have a problem with the installation of JB. No matter what ROM I install, after boot, when home screen appear, my touch screen does not respond. I've tried a lot of roms and a lot of kernels. I have unlocked BL. In stock rom I have no problems.
What could be causing this? Should I format system before installing rom via recovery or just wipe data, cache and dalvik? When I should flash kernel? Before/after installing rom? I care about CM10. Plz help.
P.S. sorry for my english
saymonek said:
I have a problem with the installation of JB. No matter what ROM I install, after boot, when home screen appear, my touch screen does not respond. I've tried a lot of roms and a lot of kernels. I have unlocked BL. In stock rom I have no problems.
What could be causing this? Should I format system before installing rom via recovery or just wipe data, cache and dalvik? When I should flash kernel? Before/after installing rom? I care about CM10. Plz help.
P.S. sorry for my english
Click to expand...
Click to collapse
I have Neo,and this is how i'm installing it: first wipe everything (data,wipe cache and Dalvik cache),flash the rom,and then flash the kernel.
georgeiulian89 said:
I have Neo,and this is how i'm installing it: first wipe everything (data,wipe cache and Dalvik cache),flash the rom,and then flash the kernel.
Click to expand...
Click to collapse
I've tried to do that way but but not succeed
Certain ROMs require phone-specific patch, make sure you install it!
Other ROMs have different downloads for different phones, make sure to download correct one!
If you install wrong phone ROM, touch dies.
All question threads belong here in Q&A so please post in the correct sections going forward.
Thanks
AvRS
saymonek said:
I have a problem with the installation of JB. No matter what ROM I install, after boot, when home screen appear, my touch screen does not respond. I've tried a lot of roms and a lot of kernels. I have unlocked BL. In stock rom I have no problems.
What could be causing this? Should I format system before installing rom via recovery or just wipe data, cache and dalvik? When I should flash kernel? Before/after installing rom? I care about CM10. Plz help.
P.S. sorry for my english
Click to expand...
Click to collapse
The problem is caused by the kernal. You MUST have JB kernel to flash any JB ROM. Generally, for each ROM you will find the recommended kernel and the required steps. Do exactly like posted by OP.
As an example, see here: http://forum.xda-developers.com/showthread.php?t=1979829
You can make an idea on the steps to follow.
okty2k said:
The problem is caused by the kernal. You MUST have JB kernel to flash any JB ROM. Generally, for each ROM you will find the recommended kernel and the required steps. Do exactly like posted by OP.
As an example, see here: http://forum.xda-developers.com/showthread.php?t=1979829
You can make an idea on the steps to follow.
Click to expand...
Click to collapse
Ok, so now I have installed Xperia T rom (7.0.A.3.195 v6.0 for ARC/ARC-S). Should I flash V77 baseband, then flash kernel from CM10 FXP150 pack via fastboot, make a wipe (data, cache, dalvik) then install ROM via Recovery, and then install GAPPS and it should work? This is what i'm gonna do, so if I'm wrong please tell me.
EDIT:
(edited in case someone had same problem)
I found the solution:
I had to flash BB 72 and libs, then flash ROM+GAPPS and libs once again, then everything works awesome. (edited in case someone had same problem)
saymonek said:
(edited in case someone had same problem)
I found the solution:
I had to flash BB 72 and libs, then flash ROM+GAPPS and libs once again, then everything works awesome. (edited in case someone had same problem)
Click to expand...
Click to collapse
I'd got a touch screen problem.
Could you please tell me that how can i flash 'libs once again' So, I can try on my Arc.
Thank you very much.
Howdy y'all!
I'm currently running a 4.1.1 ROM, and would like to get on to MMuzzy's 4.2, but there are a ton of things I think I need to flash and want to make sure I get the order right. Your help will be much appreciated!
I am already using the latest version of TWRP.
I would like to flash the latest JB bootloader, and latest JB radios, but have never flashed either. Should I do these before flashing the ROM, or after? Should I do these before formatting cache? Should I format system or factory reset before flashing these, too?
I am planning to do factory reset, format cache and dalvik before flashing ROM, gapps and kernel. Do I need to do anything else to prep for flashing the ROM? Also, is it okay to flash all three at once, or should I do rom and gapps, let everything boot and restore from market, and only then flash kernel?
My main concern is the differences in file system between 4.1 and 4.2. I'm aware of the /0 subdirectory thing already, but I'd there anything else?
Thanks much!
Jamie
I wouldn't bother with the bootloader, but if you insist then you can flash the bootloader and the radios before or after. Doesn't matter.. Other than that, you do them ROM, gapps, kernel and I've done all three at once. Mmuzzy's is a good ROM. Enjoy.
First make a backup in TWRP
Factory reset
Wipe both caches
Install ROM, gapps, then kernel and reboot. (All at the sometime in that order)
I have heard its better to flash the kernel with the new ROM so just do it all in one flash.
Set everything up and let your phone sit for 15 minutes untouched and go for it.
Sent from my Galaxy Nexus using xda app-developers app
jrbedford said:
My main concern is the differences in file system tree between 4.1 and 4.2. I'm aware of the /0 subdirectory thing already, but I'd there anything else?
Thanks much!
Jamie
Click to expand...
Click to collapse
Just a small correction; file system change would mean switching from ext4 to f2fs, for example. That's not the case.
MartianCeo said:
First make a backup in TWRP
Factory reset
Wipe both caches
Install ROM, gapps, then kernel and reboot. (All at the sometime in that order)
I have heard its better to flash the kernel with the new ROM so just do it all in one flash.
Set everything up and let your phone sit for 15 minutes untouched and go for it.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Watch out with restoring backups. Don't restore app/system data. OP is switching major versions.
sent from my Google Galaxy Nexus
dear all,
please am facing a very bad problem and i need urgent help.
every time i wanted to flash a custom rom, to flash a stock rom, re-root the phone.
i mean that if i was in a custum rom and want to change the rom i stuck on the sony logo which force me to re-do all the first process (flash a stock rom, re-root the phone),
well my problem and the main question is... what am doing wrong?!?! please heeeeeelp.
When you install a custom rom install the kernel provided with that rom and read the instruction on that specific rom how to install
Sent from my LT26i using xda premium
oache said:
When you install a custom rom install the kernel provided with that rom and read the instruction on that specific rom how to install
Sent from my LT26i using xda premium
Click to expand...
Click to collapse
am doing all the steps mentioned, and am still on locked boot loader.
thats your problem you cant have custom roms on locked bootloaders.
when you install other custom roms you should follow those steps
factory reset
cache partition wipe
wipe davlik cache (cwm>advanced)
(i also format system but its optional)
install rom zip
reboot... i do this and i have never stuck on sony's logo
soldiers33 said:
thats your problem you cant have custom roms on locked bootloaders.
Click to expand...
Click to collapse
Yes you can but only stock based roms. Which are you trying to flash?
Sent from my 4.2.2 Xperia S via Tapatalk
devilakos said:
when you install other custom roms you should follow those steps
factory reset
cache partition wipe
wipe davlik cache (cwm>advanced)
(i also format system but its optional)
install rom zip
reboot... i do this and i have never stuck on sony's logo
Click to expand...
Click to collapse
wow thanks it worked after factory reset, i never format my phone before installing a custom rom, i thought while installing the custom rom it writes formatting system, wiping cahe.. etc... though i thought i do automatic
really thanks for helping
Ben36 said:
Yes you can but only stock based roms. Which are you trying to flash?
Sent from my 4.2.2 Xperia S via Tapatalk
Click to expand...
Click to collapse
am flashing XZXperience v2 rom, well as i noticed and a friend before your post figured it out, i must factory rest.. i really worked and didnt stuck on sony logo
thanks all for helping and replying me
this forum rooooooocks
Hi,
For about a few days, I can't flash any touchwiz based rom, even the ones I could flash without any problem before. After I flash any touchwiz rom, my phone goes into a bootloop cycle. Though I can boot into recovery and download mode with key combinations. I don't know when this happened for the first time but as far as I can remember, it would be after I flashed some 4.4 AOSP rom (could be Omnirom, I'm not sure though)
What I did to recover from boot loop:
- Wipe cache, wipe dalvik cache and reboot, no joy.
- Wipe cache, wipe dalvik cache, wipe data, reboot, no joy.
- Wipe cache, wipe dalvik cache, wipe data, wipe data/media, reboot, no joy.
- Pulled out the battery between these steps too.
At first, I thought something was wrong about the aroma installer itself because the phone was getting frozen during aroma installer setup screen, then I came up that it was caused due to my older CWM version, so I updated the recovery and it didn't freze again during installation.
And by the way, I've lost my efs partition during these processes, thankfully I've had a nandroid backup from a couple of months before.
Now I'm stuck with AOSP roms and the only way I can use a touchwiz rom is to flash the stock rom via odin. But I want to use the new leaked version based Note3 featured roms.
I've seen similar topics at S4 section but I couldn't be sure if I can do the exact steps for an N7100 international device.
I'm pretty familiar with linux system and I can use adb so I can provide any kind of information you need to diagnose this issue. Thanks in advance. Best regards.
HOW I SOLVED THIS PROBLEM
- Wiped everything (system, data, sdcard, of course internal sdcard)
- Flashed n7100 16GB pit file via odin
- Flashed stock rom via odin
- During these steps, I realized that my CSC code had been changed, I've corrected it acording to my country code
- Rooted my phone again
- Flashed CWM 6.0.4.3 recovery
- Flashed DN3 V3.1 rom
- Bingo, I successifully booted into DN3 rom but had no WIFI
- Flashed MJ5 bootloader
- Rebooted, then WIFI worked without a problem
- Setup my phone and did some restore
It's all good now. Thanks for everything, I hope these steps can help someone facing the same problem.
Guys, I really need some help.. Any idea about what might the problem be?
Sent from my GT-N7100 using XDA Premium 4 mobile app
Download HD wipe script,flash the script zip via cwm/philz then try installing the rom of your choice.
I found the script from tamirda's phoenix rom thread and is very useful:http://d-h.st/fWr
Full wipe cache and reset in recovery menu, clear everything, you should be up and running.
akp.ajinkya said:
Download HD wipe script,flash the script zip via cwm/philz then try installing the rom of your choice.
I found the script from tamirda's phoenix rom thread and is very useful..
Click to expand...
Click to collapse
Thanks for the reply. I flashed this superwipe script, then flashed DN3 rom but still I got stuck at Samsung Galaxy Note II screen boot loop. I really don't understand this. What am I missing? What would happen if I wipe the entire internal memory block, I mean the whole things, even the root partition too.. I'm thinking that maybe there's some file inside the root partition that prevents me to flash touchwiz roms or perhaps something wrong about touchwiz based roms' bootloaders.. I'm truely pissed..
(InsertNameHere) said:
Full wipe cache and reset in recovery menu, clear everything, you should be up and running.
Click to expand...
Click to collapse
Have you read my first message? I remember that I've mentioned I've done already what you ask me to do.. Believe me I wouldn't shoot a new thread if I could've solved my problem with such easy steps. I've already done so many wipes, including internal SD and whatsoever.. I'm really confused and NEED help. Thanks anyway..
I think you can go for the method you mentioned.But also give a try to start fresh i.e pit file flashing...wiping everything n installing stock rom then rooting,flashing custom recovery n then installing any TW custom rom.
Also give other TW based roms a try too.
Im having the same problem but after flashing kernels (e.i. saber & perseus).
Im currently running on Tigra rom. Is this a compatibility issue or im just missing something here too?
I came across flashing bootimg but this thread http://forum.xda-developers.com/showthread.php?t=1752270
is for One S, im not sure if will work on Note 2 & haven't tried it yet.
Any suggestions? help pls...
akp.ajinkya said:
I think you can go for the method you mentioned.But also give a try to start fresh i.e pit file flashing...wiping everything n installing stock rom then rooting,flashing custom recovery n then installing any TW custom rom.
Also give other TW based roms a try too.
Click to expand...
Click to collapse
Well, the problem is gone.
What I did was the things you said.
- Wiped everything (system, data, sdcard, of course internal sdcard)
- Flashed n7100 16GB pit file via odin
- Flashed stock rom via odin
- During these steps, I realized that my CSC code had been changed, I've corrected it acording to my country code
- Rooted my phone again
- Flashed CWM 6.0.4.3 recovery
- Flashed DN3 V3.1 rom
- Bingo, I successifully booted into DN3 rom but had no WIFI
- Flashed MJ5 bootloader
- Rebooted, then WIFI worked without a problem
- Setup my phone and did some restore
It's all good now. Thanks for everything, I hope these steps can help someone facing the same problem.
Happy to help you bro
Hi,
I don't know what happened because I didn't do anything out of ordinary, but my S3 (TMO LTE) seems bricked. It was unlocked, rooted, and was running pacman lollipop ROM. The recovery was TWRP (the latest). I was going to sell this phone, so I turned off, removed sim card and microsd card. Powered it on. Everything was working. Then, I went to setting and hit factory reset from there. The phone restarted, but got stuck on the blue teamwin screen (the one that gets displayed before TWRP loads). The phone can't get past it. Not sure what caused it because it was a simple factory reset from the OS itself. Any help would be appreciated.
Thank you,
Just flash stock rom from sammobile.com using Odin. After flashing, boot to recovery and perform a full wipe.
audit13 said:
Just flash stock rom from sammobile.com using Odin. After flashing, boot to recovery and perform a full wipe.
Click to expand...
Click to collapse
If I flash the firmware from there, I'm going to lose root, right?
The phone will go back to completely stock, no root.
audit13 said:
The phone will go back to completely stock, no root.
Click to expand...
Click to collapse
Is there an alternative fix that will maintain the root TWRP? I know I can just root it again, but if possible I'd rather not go through all that because I am relocating in 3 days.
Do you want to sell the phone with a custom ROM? If you do, you could download and flash another custom ROM after re-installing TWRP.
audit13 said:
Do you want to sell the phone with a custom ROM? If you do, you could download and flash another custom ROM after re-installing TWRP.
Click to expand...
Click to collapse
Yes. I'm trying to make it more appealing with Lollipop on it lol So, just to double check, I should just install TWRP using Odin then install custom ROM, correct? By the way, do you have any idea what why my S3 got bricked? Did I do something wrong???
Sometimes, things just happen. Could be a several factors, one of which is the fact that cm12.1 may not have reached a stable state on the device. Also, the latest bootloader for the T999L is 4.3 while KK is the latest for T999v. Maybe the KK bootloader makes the phone more stable? I really don't know.
Yes, just flash TWRP, boot to recovery, do a full wipe of the system, cache, dalvik, data, flash ROM, flash Gapps, flash supersu if the ROM is not pre-rooted, and re-boot.
audit13 said:
Sometimes, things just happen. Could be a several factors, one of which is the fact that cm12.1 may not have reached a stable state on the device. Also, the latest bootloader for the T999L is 4.3 while KK is the latest for T999v. Maybe the KK bootloader makes the phone more stable? I really don't know.
Yes, just flash TWRP, boot to recovery, do a full wipe of the system, cache, dalvik, data, flash ROM, flash Gapps, flash supersu if the ROM is not pre-rooted, and re-boot.
Click to expand...
Click to collapse
Thank you for all your help. You are awesome!
You're very welcome. We're all here to help each other out!