Related
I successfully loaded the latest Cordroid ROM V4 on HTC One X as far as install goes. However on reboot I get the Sense ring screen which am unable to use before phone reboots.
In a constant boot loop.
Thankfully took a Rom backup prior to install that got me out of trouble.
Anyone else managed to get this to work or is there an error in the Rom or the way I am installing?
Not had issues with previous Roms from Coredroid….
Probably something wrong with your install. Did you wipe dalvik cache, etc.?
Reflash new boot.img.
Sent from XDA App using HTC One X.
PCHAPM said:
I successfully loaded the latest Cordroid ROM V4 on HTC One X as far as install goes. However on reboot I get the Sense ring screen which am unable to use before phone reboots.
In a constant boot loop.
Thankfully took a Rom backup prior to install that got me out of trouble.
Anyone else managed to get this to work or is there an error in the Rom or the way I am installing?
Not had issues with previous Roms from Coredroid….
Click to expand...
Click to collapse
perform full wipe, clear cache and dalvik cache before installing v4 as it has new kernel and reflash boot image and reinstall ROM again
vivek_bhoj said:
perform full wipe, clear cache and dalvik cache before installing v4 as it has new kernel and reflash boot image and reinstall ROM again
Click to expand...
Click to collapse
Had done the full wipe and cleared both cache but not the reflash of boot imgage this did the trick. Thanks for the great help.......
My T-Mobile Galaxy s4 M919 will not boot after any custom ROM flashes. I tried 4 different ROMs with success messages. As soon as I reboot my phone after the ROM flash, it's stuck at the Samsung Galaxy S4 logo and would not enter the "phone desktop". I can easily enter download mode and recovery mode without any issue.
Background: I rooted with Odin successfully. (Used both CWM and OUDHS with the same no-boot results after flashing any custom ROMs). I can restore back to stock and phone boot up fine but tried root again and then with custom ROM and it would not boot. Any help would appreciate it.
After flashing a rom, go into recovery, and erase stuff. Like cache and dalvik cache. Possibly even data
Sent from my SGH-M919 using XDA Premium 4 mobile app
Android_Monsters said:
After flashing a rom, go into recovery, and erase stuff. Like cache and dalvik cache. Possibly even data
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I did that after each ROM flash. 1. Wipe data/factory reset, 2. wipe cache part, 3. wipe dalvik cache. Did not fix the problem. No good. Please clarify "possibly even data". I am not sure which wipe is that.
anothersaddream said:
I did that after each ROM flash. 1. Wipe data/factory reset, 2. wipe cache part, 3. wipe dalvik cache. Did not fix the problem. No good. Please clarify "possibly even data". I am not sure which wipe is that.
Click to expand...
Click to collapse
using CWM:
*wipe data/factory reset
*wipe cache
*wipe, dalvik cache
*wipe system
*wipe sdcard (only if you have the ROMs you plan on flashing on your external sdcard, this will erase internal sd)
now flash your ROM of choice. reboot (will take 1-2min on first boot)
use cwm touch. what ROMs have you tried so far?
I am thinking you are flashing something not specific to the TMo S4, so your not getting the right kernel installed. Try installing a TMo specific kernel immediately after flashing a rom and see what happens.
Yeah, what ROMs have you tried already? Have you tried TWRP 2.5 recovery?
Sometimes it'll take up to 10 minutes to boot up (I haven't experienced this yet with the GS4, but I have with other phones). How long did you wait before determining it was just stuck?
I switched to PhilZ Touch Recovery a couple of weeks ago and have not had Any issues as I did before.
TWRP 2.5.0.2 was issue free for months, until I started flashing ROMs with Aroma.
Nothing but issues re Samsung splash screen freezes, different solutions working sometimes and sometimes not, having to ODIN back to stock on many occasions, having to wipe INTERNAL SD on many occasions, etc., etc.
PhilZ was the solution.
This is coming from a hard core TWRP guy......
Check the link in Red in my sig for PhilZ and other good stuff
dynospectrum said:
using CWM:
*wipe data/factory reset
*wipe cache
*wipe, dalvik cache
*wipe system
*wipe sdcard (only if you have the ROMs you plan on flashing on your external sdcard, this will erase internal sd)
now flash your ROM of choice. reboot (will take 1-2min on first boot)
use cwm touch. what ROMs have you tried so far?
Click to expand...
Click to collapse
Where do you "wipe system"? I see a format /system inside Mounts and Storage Menu. Please confirm.
DKYang said:
Yeah, what ROMs have you tried already? Have you tried TWRP 2.5 recovery?
Sometimes it'll take up to 10 minutes to boot up (I haven't experienced this yet with the GS4, but I have with other phones). How long did you wait before determining it was just stuck?
Click to expand...
Click to collapse
I have not tried TWRP 2.5 recovery yet. I mostly use CWM. I have waited 20+ minutes after flashing a custom ROMs but to no success.
I have done the following ROMs:
Insanity v1
VirginROM
stevessvt said:
I am thinking you are flashing something not specific to the TMo S4, so your not getting the right kernel installed. Try installing a TMo specific kernel immediately after flashing a rom and see what happens.
Click to expand...
Click to collapse
I did try the InFamous ROM for Tmobile s4. This ROM also has a kernal. Same results, stuck at Samsung Galaxy s4 Logo screen. It would not go anywhere after that.
Really needing help here.
anothersaddream said:
I did try the InFamous ROM for Tmobile s4. This ROM also has a kernal. Same results, stuck at Samsung Galaxy s4 Logo screen. It would not go anywhere after that.
Really needing help here.
Click to expand...
Click to collapse
Okay let's start over from scratch.
First off can you restore the stock ROM using your nandroid backup?
Second, I don't think you are properly wiping everything prior to flashing the new ROM. You need to wipe system, data, dalvik, and cache in the CWM wipe menu prior to flashing the new ROM.
Wipe all 4 things. Wiping any less than all 4 things will cause the problems you are experiencing.
Once you've done that, then flash the ROM.zip and reboot and it should work just fine.
anothersaddream said:
Where do you "wipe system"? I see a format /system inside Mounts and Storage Menu. Please confirm.
Click to expand...
Click to collapse
wipe = format
yes, format system in mounts/storage.
Skipjacks said:
Okay let's start over from scratch.
First off can you restore the stock ROM using your nandroid backup?
Second, I don't think you are properly wiping everything prior to flashing the new ROM. You need to wipe system, data, dalvik, and cache in the CWM wipe menu prior to flashing the new ROM.
Wipe all 4 things. Wiping any less than all 4 things will cause the problems you are experiencing.
Once you've done that, then flash the ROM.zip and reboot and it should work just fine.
Click to expand...
Click to collapse
I did exactly what you stated. Restored to stock. Rooted successfully. Wiped all 4 things. ROM flash stated success. Still NO good. Stuck samsung S4 logo. You think there is something wrong with the hardware???? The s4 does randomly reboot on stock.
anothersaddream said:
I did exactly what you stated. Restored to stock. Rooted successfully. Wiped all 4 things. ROM flash stated success. Still NO good. Stuck samsung g4 logo. You think there is something wrong with the hardware???? The s4 does randomly reboot on stock.
Click to expand...
Click to collapse
When I was flashing ROMs w/Aroma using TWRP 2.5.0.2, I would sometimes get Samsung boot screen freezes. The only way I could resolve this was by wiping Internal SD, in addition to the other wipes mentioned, and flashing the ROM again.
find stock kernel, flash the roms you want and flash the stock kernel after and see if you boot
Biker1 said:
When I was flashing ROMs w/Aroma using TWRP 2.5.0.2, I would sometimes get Samsung boot screen freezes. The only way I could resolve this was by wiping Internal SD, in addition to the other wipes mentioned, and flashing the ROM again.
Click to expand...
Click to collapse
I also tried your suggestion exactly what you stated. Restored to stock. Rooted successfully. Wiped all 4 things + format /sdcard (internal SD). ROM flash stated success. Still NO good. Still Stuck Samsung S4 logo.
Is there any custom ROMs I can flash using odin?
anothersaddream said:
I also tried your suggestion exactly what you stated. Restored to stock. Rooted successfully. Wiped all 4 things + format /sdcard (internal SD). ROM flash stated success. Still NO good. Still Stuck Samsung S4 logo.
Is there any custom ROMs I can flash using odin?
Click to expand...
Click to collapse
ODIN Samsung Stock Firmware.
Boot.
ODIN Custom Recovery.
(I use PhilZ Touch Recovery. Flashes ROMs flawlessly )
Boot.
Flash custom ROM afterwards.
If ROM doesn't have Root, then Root with CF-AUTO-ROOT by Chainfire via ODIN prior to installing Custom Recovery.
Then flash custom ROM.
Biker1 said:
ODIN Samsung Stock Firmware.
Boot.
ODIN Custom Recovery.
(I use PhilZ Touch Recovery. Flashes ROMs flawlessly )
Boot.
Flash custom ROM afterwards.
If ROM doesn't have Root, then Root with CF-AUTO-ROOT by Chainfire via ODIN prior to installing Custom Recovery.
Then flash custom ROM.
Click to expand...
Click to collapse
I did as you stated. I love Philz Touch recovery UI. Very nice. Unfortunately, did not work as well. It stated successfully. I tried 2 rom, Infamous S4 v.2.5 and also the VirginROM v2.3.1. Both stated successful flashed but would not boot into the phone desktop. Stuck for over 10 minutes on black and white "Samsung Galaxy S4" logo.
I will send you a nice Starbucks gift card if anyone can fix this problem.
anothersaddream said:
I did as you stated. I love Philz Touch recovery UI. Very nice. Unfortunately, did not work as well. It stated successfully. I tried 2 rom, Infamous S4 v.2.5 and also the VirginROM v2.3.1. Both stated successful flashed but would not boot into the phone desktop. Stuck for over 10 minutes on black and white "Samsung Galaxy S4" logo.
I will send you a nice Starbucks gift card if anyone can fix this problem.
Click to expand...
Click to collapse
I have no idea why it ain't working for you.
On the plus side, I don't know everything
If you ODINd Stock.
ODINd Recovery.
Did a Md5 Checksum match between the ROM file and your Download.
Wiped Internal SD.
Flashed the ROM......
and you're still having issues.......
I'm at a loss....
Try again is my only suggestion, and insure the steps taken are correct, including ODINing the proper files for your device.
Check & Double check
Including making sure you have a good usb cable, which sometimes can work and sometimes not....
If you haven't, try flashing from internal sd card. Maybe remove th external sd card just in case.
I recently tried installing probam rom v4.4.9 from xda threads and followed all the instructions. everything worked fine up until the thread said to reboot the phone once more, anyway long story short i rebooted it and it was stuck at the galaxy note 2 logo (white letters black background) it was stuck like this for around 5-10mins at which point i pulled the battery and decided to go back to using rootbox rom.
Is their anyway i can install probam rom without this happening again?
I've also tried downloading and installing probam version 4.5.0 from their own website following the instructions given on xda, but once its booted from twrp it'll work until i have to reset, at which point i am back to square one, being stuck at the galaxy note 2 logo.
I have also tried installing pacman rom because i would like to use a 4.3 rom but the same thing happens, the rom will work fine until i have to reboot or it randomly reboots and gets stuck at the note 2 logo.
the only roms i am able to use without this happening are moon rom v10, rootbox rom and carbon rom, only thing is i would like to use different roms and check out their features, but i am somewhat limited to what i can use due to the above problem. Does anyone else have this issue? If so how did you get past it?
Haven't had the problem myself. Did you also format the system partition and not just wipe it? Wipe the data partition?
Perhaps you can try installing a stock firmware through Odin, reinstall your recovery. That might clean some thing up that keep you from booting in probam rom.
Sent from my GT-N7100 using xda app-developers app
Machiel187 said:
Haven't had the problem myself. Did you also format the system partition and not just wipe it? Wipe the data partition?
Perhaps you can try installing a stock firmware through Odin, reinstall your recovery. That might clean some thing up that keep you from booting in probam rom.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
through twrp i went to wipe, format data typed yes, after this i swiped to factory reset then advanced wiped clicking cache, dalvik cache and system, if i've done this wrong could you please tell me how to do it the right way as i'm not really sure how to, thanks in advance :highfive:
i did what you told me to and flashed a stock rom through odin, went through the whole rooting process and flashed probam 4.5.0 again and this time it worked!! But no signal at all
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
Hello,
I have a unique issue. I'm having a problem installing any custom rom on my t999 (tmobile). I have been using a custom rom for over a year. Always used TWRP. Started with Paranoid Android and for the last few months I've been using PAC-Man (nightly) roms. I was having gps lock issues, I decided to upgrade the modem to a leaked UVUEMJC, this fixed the gps lock issue. But after the reboot, I was stuck on bootloader screen. The only way I could get the rom to work was to backup the rom, flash the system and data, and after that, the rom would work until reboot. I did this a few times until it stopped working. My efs was corrupted, IMEI missing, To recover it, I went into download mode, and noticed in red Warranty bit =1. I used odin to flashed a rooted cf 4.3 samsung touchwiz rom (root66_TMO_T999UVUEMJC). All imei/efs issues were fixed. I decided to try installing a custom rom again, PAC-Man rom, it installed just fine, all EFS/IMEI info was intact, but at reboot, I got stuck on the CM bootlogo. This happens everytime. IF I recover a backup, it gets stuck on the boot logo. I'm using TWRP v2.6.3.
Anybody have any suggestions on how to fix this issue?
Thanks!
Install TWRP 2.6.3.1. Then take a Nandroid.
Next wipe /Data. Then flash your Custom Rom. Wipe Dalvik + Cache after the Flash. Reboot and report.
Perseus71 said:
Install TWRP 2.6.3.1. Then take a Nandroid.
Next wipe /Data. Then flash your Custom Rom. Wipe Dalvik + Cache after the Flash. Reboot and report.
Click to expand...
Click to collapse
Thanks for the reply Perseus71. I'll give it a shot!
acedik said:
Thanks for the reply Perseus71. I'll give it a shot!
Click to expand...
Click to collapse
Upgrading to the newest TWRP did the trick! Everything is working fine now. :good:
Thanks for the help!
I'm also having trouble flashing PAC-man.
SGH-T999LUVUBMK4
Factory reset everything, wiped SD card.
Tried latest TWRP and CWM.
Suggestions?
D
Donny Orbit said:
I'm also having trouble flashing PAC-man.
SGH-T999LUVUBMK4
Factory reset everything, wiped SD card.
Tried latest TWRP and CWM.
Suggestions?
D
Click to expand...
Click to collapse
You need to post info about the error
Sent from my SGH-M919 using Tapatalk
It says
E: Error executing updater binary in zip '/external
Error flashing zip '/external_sd/pac_d2tmo-night
I tried flashing the Rom that doc fixed specifically for the T999LTE for the CM10.1.2 also with no avail.
Same problem.
D
wipe Dalvik and Cache before trying the rom again. If