Hi Friends,
Model Number - GT-P7510
I recently rooted and installed the CM9 ICS nightly rom using the noob video instructions (This included rooting with Odin, installing CMW recovery 4.0.0.4, then I flashed the ROM cm-9-20120624 Nightly and finally flashed GAPPS-ics).
I over clocked using the CM9 settings and everything worked perfectly for about a week, it was great. Then it just crashed while I was reading my email and began to bootloop. After reading for similar errors I rebooted to recovery and tried wiped the cache and dalvic cache, I wiped data and factory reset several times but nothing worked, always the same bootloop. I re flashed the same ROM and still nothing, after a while the boot screen would simply freeze instead of bootloop.
Then I connected to my PC, and did this to no avail. In fact it simply added to the problem by adding a yellow warning triangle while attempting to boot so I did the Oden thing again like the first time I rooted however I installed CMW version 5.5.0.4 instead thinking it might help but it hasn't.
One last point, when I attempt to wipe data/factory reset the tablet seems to freeze and attempt to reboot rather than say something like "success" as it would during a cache wipe. This maybe normal or it maybe the problem! who knows?
On that point, I would be very grateful if some of you could help get me to the point when my PC recognises the tablet so I can reflash a new ROM.
Thanks in advance,
Karl
I once got the same problem. The only thing that helped was to flash back the stock rom via Odin with the pit file. And don't forget to do a hard reset after flashing the rom. I'll just stick to the stock rom until the official update is getting released.
Sent from my GT-P7501 using xda app-developers app
Questions go in the Q&A section
I think the best way is still to do factory reset, go back to the stock ROM first and try custom HC ROM until the official ICS is released.
Anyone else have problems flashing to a 4.3 ROM? (I know some people do because I've searched.)
No matter what ROM it is, if it is 4.3 it will always fail to reboot a second time after it has been flashed.
Currently on CleanROM ACE 4.9 (4.1.2) with TWRP 2.6.0.1
I've tried to go to CM10.2 and it would reboot initially but then hang on the Note II logo if I tried to reboot.
I've tried to go to Paranoid Android.. same thing.
I've tried to go to PAC-man.. same thing.
I've tried flashing from the stock 4.1.2 ROM and the same thing happens.
I've followed every instruction I could find including this: http://forum.xda-developers.com/showthread.php?t=2423057
I do a factory reset, format data, flash ROM, wipe caches, flash gapps, wipe caches, reboot. It will boot fine from TWRP and load everything normally. Then, if I reboot or power off the device, it will hang on the Note II screen and I have to nandroid back to my previous ROM.
Any insight as to why this is happening? I haven't been able to find anything besides some random instructions for wiping/flashing (which I've linked). These ROMs look great and I'd really like to move to 4.3, but I cannot figure out what the problem is.
BigBoy275 said:
Anyone else have problems flashing to a 4.3 ROM? (I know some people do because I've searched.)
No matter what ROM it is, if it is 4.3 it will always fail to reboot a second time after it has been flashed.
Currently on CleanROM ACE 4.9 (4.1.2) with TWRP 2.6.0.1
I've tried to go to CM10.2 and it would reboot initially but then hang on the Note II logo if I tried to reboot.
I've tried to go to Paranoid Android.. same thing.
I've tried to go to PAC-man.. same thing.
I've tried flashing from the stock 4.1.2 ROM and the same thing happens.
I've followed every instruction I could find including this: http://forum.xda-developers.com/showthread.php?t=2423057
I do a factory reset, format data, flash ROM, wipe caches, flash gapps, wipe caches, reboot. It will boot fine from TWRP and load everything normally. Then, if I reboot or power off the device, it will hang on the Note II screen and I have to nandroid back to my previous ROM.
Any insight as to why this is happening? I haven't been able to find anything besides some random instructions for wiping/flashing (which I've linked). These ROMs look great and I'd really like to move to 4.3, but I cannot figure out what the problem is.
Click to expand...
Click to collapse
First time installing CyanogenMod 10.2 to your Galaxy Note 2 I605, or coming from another ROM:
- Read known issues ans FAQs
- Flash the latest official ClockworkMod-Recovery
- Copy GApps and CM10.2 ZIPs to your SDCard
- Boot into Recovery
- Flash CM10.2 zip from SDCard
- Flash GApps zip from SDCard
- DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
- Reboot
- Don't restore system data using Titanium Backup!
- Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
read the OP for CM 10.2 next time....
First - clockworkmod not twrp for 4.3 usually fixes things
Second - do a factory reset AFTER installing
Third - Dont restore apps with TiBu going to 4.3
Next time be truthful when you say you read and searched.
HI.
I've changed roms before countless times, but now I'm trying to install a 4.4.2 rom on my Galaxy S3, and I have some problems. The installation (flash) passes with no problems, but after that, the phone won't boot. It sticks on whatever the rom's boot animation is. I've tried to wipe data, cache, wipe dalvik after this but it's still not working. Before I flash every rom, I do a factory reset, wipe the dalvik cache, and format system. I've tried with 15+ 4.4.X roms, and these are some of them: CyanogenMod, OmniROM, SlimKat, AOKP, Pacman and so on. As I said, I've flashed roms before a lot of times, without any problem. Only 4.4+ roms wont work. I tried to change the recovery, still the same result. I flash gapps with every rom too. Any idea what can be causing the problem? I'm using the latest Clockwork recovery, Sorry for my bad english and thanks.
divoom12 said:
HI.
I've changed roms before countless times, but now I'm trying to install a 4.4.2 rom on my Galaxy S3, and I have some problems. The installation (flash) passes with no problems, but after that, the phone won't boot. It sticks on whatever the rom's boot animation is. I've tried to wipe data, cache, wipe dalvik after this but it's still not working. Before I flash every rom, I do a factory reset, wipe the dalvik cache, and format system. I've tried with 15+ 4.4.X roms, and these are some of them: CyanogenMod, OmniROM, SlimKat, AOKP, Pacman and so on. As I said, I've flashed roms before a lot of times, without any problem. Only 4.4+ roms wont work. I tried to change the recovery, still the same result. I flash gapps with every rom too. Any idea what can be causing the problem? I'm using the latest Clockwork recovery, Sorry for my bad english and thanks.
Click to expand...
Click to collapse
Format data and system and cache (full wipe) also intstall the rom then boot it then flash gapps after see if that helps.
tallman43 said:
Format data and system and cache (full wipe) also intstall the rom then boot it then flash gapps after see if that helps.
Click to expand...
Click to collapse
I've already done that every time. As I said - Its not my first time flashing roms on my device. I know how to fix the general errors. This is something unusual tho.
Hey
When it bootloops, have you tried to goto recovery and see what us the cwm version??
Also try re-flashing the ROM without wipes..
Sent from my GT-I9300 using xda app-developers app
I just flashed EHNDROIX V (based on CynogenMod 4.4.2 KitKat) last night and it worked just fine.
Rooted the device with Odin, install TWRP from playstore, install TWRP recovery from TWRP, clean dalvik, clean data, clean cache, flash ROM and then flash Gapps (spesific Gapps for the ROM) and voila it worked right away.
Note:
You see, I am not using CWM but TWRP. I dunno if CWM is the one causing the problem.
Most of the weird flashing issues are due to the recovery used, you could also try the latest version of Philz recovery which has an option to wipe for new firmware.
Sent from my GT-I9300 using Tapatalk
divoom12 said:
I've already done that every time. As I said - Its not my first time flashing roms on my device. I know how to fix the general errors. This is something unusual tho.
Click to expand...
Click to collapse
Quote " Before I flash every rom, I do a factory reset, wipe the dalvik cache, and format system" You said nothing about formatting data that is why i suggested it! Next time please include all details on how you flashed the rom then It cuts down on useless post's like mine
Like everybody suggested try a different recovery ( latest one) which if you have flashed roms many times before you should have done anyway
Thanks guys, but I've already tried these things. CWM, TWRP and three other recoveries (not famous ones) haven't been able to help.
divoom12 said:
Thanks guys, but I've already tried these things. CWM, TWRP and three other recoveries (not famous ones) haven't been able to help.
Click to expand...
Click to collapse
If a rom is stuck in a loop, I would go to recovery and wipe dalvik and wipe data then reboot into same rom. This has worked for me when I've been stuck after a flash.
~ RazorMC
RazorMC said:
If a rom is stuck in a loop, I would go to recovery and wipe dalvik and wipe data then reboot into same rom. This has worked for me when I've been stuck after a flash.
~ RazorMC
Click to expand...
Click to collapse
I said that I've already done that in my First post.
divoom12 said:
HI.
I've changed roms before countless times, but now I'm trying to install a 4.4.2 rom on my Galaxy S3, and I have some problems. The installation (flash) passes with no problems, but after that, the phone won't boot. It sticks on whatever the rom's boot animation is. I've tried to wipe data, cache, wipe dalvik after this but it's still not working. Before I flash every rom, I do a factory reset, wipe the dalvik cache, and format system. I've tried with 15+ 4.4.X roms, and these are some of them: CyanogenMod, OmniROM, SlimKat, AOKP, Pacman and so on. As I said, I've flashed roms before a lot of times, without any problem. Only 4.4+ roms wont work. I tried to change the recovery, still the same result. I flash gapps with every rom too. Any idea what can be causing the problem? I'm using the latest Clockwork recovery, Sorry for my bad english and thanks.
Click to expand...
Click to collapse
Did you update your bootloader? When I flashed 4.4.2 from 4.4.1 on my s3, I had to update mine to get it to work. http://forum.xda-developers.com/showthread.php?t=2321310 hope this helps.
Sent from my unknown using XDA Premium 4 mobile app
I was using my phone and all had been working fine for ages. It was in my pocket for a while and when i took it out to use it I saw that it was on the boot animation of CM11. My phone was already on when I last used it so I had assumed it had crashed. I took the battery out and turned the phone on again but it got stuck on the CM boot animation. The last time I turned on my phone before that was when I flashed a supersu zip file to make my root work as I was having some problems. After flashing the supersu zip and told my CWM recovery to restart the system, it prompted me to "fix root" or something like that, and I clicked yes and it booted normally. That was the last time it booted normally before being stuck as it is now. First thing I did after it got stuck was go into recovery and reflash my current rom ( a CM11 snapshot) I then got faced with a status 7 error and so couldnt flash the rom. So then I flashed multiple other CM11 roms, none of which worked, so I flashed a CM10.2 stable rom which worked. I then got faced with the fix root before reboot thing and so I clicked yes. Still had the stuck booting thingy. I tried many things, flashing kernals roms gapps etc and nothing made a difference. I wiped cache, dalvik cache and no difference. I even wiped the system and tried to flash roms but only the 10.2 one would work, still got a status 7 with the CM11 ones. When I wiped my data however and flashed CM 10.2, it booted. I still couldn't flash the CM11 roms though even after a factory reset. So I have the reason to believe something in the data is wrong, not cache system or anything like that. What could it be? I don't want to have to lose all my data in order to be able to use my phone again, even then, something is still wrong as my phone won't flash CM11 roms anymore. So my questions are;
What things could have caused this?
Can this be a problem from flashing the supersu zip (a root issue)
Is it possible to somehow view or copy the internal data on a computer (since I cant get into the operating system), and this would allow me to get all my pictures contacts music etc anything so I can use my phone by wiping data?
Thanks, sorry this is quite long and probably hard to understand whats going on, but help is appriciated thanks
Don't fix root if you wish to use SuperSU instead builded-in cm superuser. Also try to flash via Odin latest recovery. TWRP should be fine. You can mount partitions from recovery level to download data to your computer. Of course if it still exists. If not, if they are corrupted you need to flash stock ROM and repeat whole cm11 adventure again. If Odin successfully flash the stock then it's a chance your partition layout and user data are untouched.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2
so ive been out of the loop for a while (2-3 years) but decided to updated my old omega v34, boeflla kernel jellybean s3 to the one in my sig (essentially blisspop+boeflla 4 alpha 13+gapps lollipop).
i updated my boot manager to twrp as suggested. rebooted. i did a format data, folowed by delvik cache and cache wipe, then a system wipe. i then installed the rom and gapps, then rebooted. i was still on the old kernel at this point.
as i rebooted i experienced some hanging, and then after taking off the battery and rebooting and finishing the setup process, i rebooted and installed the latest lollipop boeffla kernel. i still got some hanging so i full wiped again and repeated the process of installing the rom/gapps. my modem as remained the same and i have not updated it since last i did 2012.
as of now, i am still experiencing some freezes, but not as frequent as before and some slowdown. is there something that i messed up or forgot to do in the installation? any help is greatly appreciated.
@rab1412000412:
1. TWRP is a recocery, not a bootloader.
2. Maybe, you should update your firmware 1st. What modem is installed?
ddlj1 from 2012. i changed my gapps and its much more stable now.
@rab1412000: then you had old 4.1-firmware and can be happy, that LP-ROM didn't refresh your modem. I recommend to go back to your old firmware. Make sure, that IMEI and net access are ok. Then update via KIES, OTA or Odin to newest 4.3. Backup this version and flash any ROM you want.