Related
Hi guys, first of all there were similar posts, but couldn't find anything that looked like my problem
Im currently running CM 7.2-GIO-KANG [Update: February 13, 2012]...and CWM 5.2.0.7
Let me tell you how i ended up with this version
I bought my phone..flashed it with Darkshados rooted rom V2...then i used simply gio for a while..after which I upgrade to gio pro 1.3...and gio pro 1.4...after which i switched to CM 7.2.
Ive been told that this version shouldn't have any WiFi problems..but when my phone is screen locked for a while..the WiFi shuts off...and reactivate when I unlock it....this is pain..cause i use whats app...and if the WiFi isn't on when its locked...i don't get my messages.
SO i thought maybe...its because my model firmwear changed or something...and decided to flash back to stock...and install CM 7.2 form stock.
I had reason to believe this because...my phone also registered my netwrok provider as BELL...but im actualy with VIRGIN(Altho virgin uses bells network)...the previous roms didn't do this and showed virgin.
So i decided to go to downloading mode...and re flash to Stock V2 for the s5660M. And as expected I got a bootloop. Following the instruction for the bootloop fix..i went into stock recovery, installed CWM again...and wipe data..mounted partitions..and then installed arpegio..just to check..but i keep getting stuck on the boot screen every time. finally i used CWM to restore a CM 7.2 backup i made..and managed to get that working.
Anyone have any ideas to why i cant flash stock and another rom anymore
Please and Thank you^^
Flash stock rooted by darkshado with Odin. then go to stock recovery and wipe data, then r restart and wait for boot. Don't install cwm yet.
Sent from my GT-S5660 using XDA App
Ok Ill try that thnx
Thanks it worked XD
wasa67 said:
Thanks it worked XD
Click to expand...
Click to collapse
no problem. I have the exact phone and situation as you, so if you need help just let me know.
Hi I just flashed this new Modem and the radio on my phone is broken. Tried flashing back to UVKL1 and Blaze but still get the same error. When I go into the network settings its even acting like it can't detect the SIM. Any ideas?
Wow...you joined 18 months ago and this is your first post lol
Do you have a T989? What are you flashing from? What method did you use when trying to flash the new ROM? What error are you getting?
Thanks. I've never needed to post as I've always been able to find my solution searching on the forums.
I have a T989 and am on Darkside UCLE2 Beta 5. I flashed the radio from CWM. The error I'm getting is that where the radio icon should be its crossed out as if the SIM were not even in the phone. I can't even go to the wireless settings because its telling me there is no SIM. This happened immediately after I rebooted from flashing the radio.
Maybe a bad flash. Try Odin see if that solve the problem.
Sent from my SAMSUNG-SGH-T989 using Tapatalk
Since youre coming from an ICS ROM youre going to want to do a superwipe (tdj's superwipe...its in the dev forum) before you try to flash the new update. ICS partitions a bit differently than GB and that may be your issue.
Did you flash the radio without the RIL files?
if u have an backup try using it or ur going to have to do an dark side super wipe and reflash the rom again, if u have any important documents u should back them up
Jrude2262 said:
if u have an backup try using it or ur going to have to do an dark side super wipe and reflash the rom again, if u have any important documents u should back them up
Click to expand...
Click to collapse
Backups don't save radios
Any resolution to this problem? This has been reported in several threads (link 1, link 2, link 3, need I give more?)
I'm also experiencing the same problem. I installed Paranoid Android (per instructions here) and am now experiencing the same problem. After flashing, the phone continuously reboots. I am using an HTC One V (CDMA) from the US. I also flashed the JB 4.1.2 gapps with the ROM flash process.
When it boots, I receive two errors: "Unfortunately, android.process.acore has stopped working" and "Unfortunately, Contacts has stopped working". When I lock the screen, it reboots. When I try using it, it reboots after 30 seconds. If I just leave it alone, it reboots.
I have also tried several kernels with this same ROM (kernel that comes with the ROM, SuperSick [found here], and stock CM10) and they all just produced the same behavior.
I've looked all around. Some possibilities are: bad kernel, memory (RAM or otherwise) running out, bad install of ROM, or something no one has yet to define. I don't think its a bad kernel because this happens in 3 different ones. I don't think it's a memory issue because I lowered the CPU clockspeed and the phone has plenty of storage memory, and I've also flashed AOKP with the same results which rules out a bad ROM install.
I've wiped cache, system, data, and dalvik and followed all instructions as given to get a completely fresh installation. No avail. I realize that the One V isn't very popular, and there is only a limited amount of support for it but could anyone shed some light as to what the problem could be?? Perhaps some of the original devs who made the ROMs can help out us lowly fools who can't get it to work? I thank anyone in advance for being awesome and at least trying to help.
You may have to flash the old RUU. Look in the General subforum for a thread about phone rebooting after one minute.
sounds like you did the OTA update and have the new radio version, you need to RUU back to stock and dont get the OTA.
I'll try.
Thanks both of you! I will try flashing the RUU and I'll make sure to not install the OTA update. I'll post later with my results.
...
So... I flashed the RUU on the phone again. I again carefully followed instructions on how to flash ROMs (AOKP and Paranoid) and it simply doesn't boot. AOKP's ROM only starts up to a black screen. Paranoid boots to the boot screen animation and just hangs... I've used stock kernels, and tried the SuperSick kernel with both. No progress. Any other ideas?
Try the latest version of cm10 with the latest version super sick kennel. That's what I'm running. AOKP has a few versions that boot to a black screen. If you want AOKP use the latest stable version.
Awesome!
riggerman0421 said:
Try the latest version of cm10 with the latest version super sick kennel. That's what I'm running. AOKP has a few versions that boot to a black screen. If you want AOKP use the latest stable version.
Click to expand...
Click to collapse
Riggerman0421, thanks a ton for the suggestion!! It worked! Despite not being able to use the other roms, I think I can settle with using CM10.
htc one v
filoxo said:
Riggerman0421, thanks a ton for the suggestion!! It worked! Despite not being able to use the other roms, I think I can settle with using CM10.
Click to expand...
Click to collapse
Hey I am having the same problem as you with my htc one v. What did you do exactly to fix this?
lytesson said:
Hey I am having the same problem as you with my htc one v. What did you do exactly to fix this?
Click to expand...
Click to collapse
You have to RUU your device back to the original radio version; it was changed when you accepted the OTA update. That means that you're going to have to flash it to complete stock (no recovery, HTC Sense, booloader relocked, etc.) using the RUU. The forum I found that had all of the different RUUs was deleted unfortunately. You'll have to do careful research for the RUU for your specific device. I only know that Virgin Mobile in the U.S. uses the Sprint towers, so the RUU I used was titled "RUU_PRIMO_C_ICS_40A_Sprint_WWE_VM_1.08.652.6_Radio_1.00.00.0521_2_NV_VM_3.46_0503_PRL61008_release_262414_signed". Just a quick search on XDA and found this forum that has a download link to the RUU you would need for VM [CDMA] phone (read the comments); you can also look around yourself to make sure you have the right one.
You can find specific instructions on how to RUU your device at this awesome forum. It should only take, literally, 15-20 minutes.
After that is done, you will need to unlock your bootloader again and then you're ready to move on to bigger and better ROMs.
filoxo said:
You have to RUU your device back to the original radio version; it was changed when you accepted the OTA update. That means that you're going to have to flash it to complete stock (no recovery, HTC Sense, booloader relocked, etc.) using the RUU. The forum I found that had all of the different RUUs was deleted unfortunately. You'll have to do careful research for the RUU for your specific device. I only know that Virgin Mobile in the U.S. uses the Sprint towers, so the RUU I used was titled "RUU_PRIMO_C_ICS_40A_Sprint_WWE_VM_1.08.652.6_Radio_1.00.00.0521_2_NV_VM_3.46_0503_PRL61008_release_262414_signed". Just a quick search on XDA and found this forum that has a download link to the RUU you would need for VM [CDMA] phone (read the comments); you can also look around yourself to make sure you have the right one.
You can find specific instructions on how to RUU your device at this awesome forum. It should only take, literally, 15-20 minutes.
After that is done, you will need to unlock your bootloader again and then you're ready to move on to bigger and better ROMs.
Click to expand...
Click to collapse
So, this happend to my htc and I ruu'ed back to stock, after continunously trying to install roms with constant bootloops. I did the ota update again. So if I want to install a custom rom your saying DONT do the ota after ruu'ing then install one after rooting?
I've got a similar issue (virgin mobile HTC One V)
I currently have TWRP recovery installed, and I attempted to flash the jellybean CM10 as well as the AOKP rom, and I got as far as the unicorn and I actually manged to get the phone to boot to the main screen with all the icons, but it would constantly reboot after being on for maybe a minute
I tried flashing everything back to stock including restoring a backup I had previously taken with TWRP, but no luck
I also tried flashing the stock rom downloaded somewhere here on XDA and I even flashed the stock recovery, but all I got was constant rebooting.
it would get as far as the startup animation and then reboot indefinitely
I'm at a total loss here. I've seen a few links with some resources that look like they might have been helpful (like on this thread) but the links are dead, and I also read somewhere that HTC was putting the kibosh on a site that had some stock roms.
I'd prefer to get jellybean working on my phone, but ultimately, I just want a working phone.
I've followed the process of installing the rom - some instructions said to flash the boot img before flashing the rom, some say after
I've tried both methods
I went into recovery, mounted the usbmsd and copied the rom, and used recovery to install the rom after having cleared the cache, davlik cache and wiping the data (factory reset)
I also installed the gapps package after the rom, but I don't think that's critical to getting it to just boot.
The OTA update reboots were fixed in the latest 4.2 SickleKernels.
Sent from my One V using Tapatalk 2
bheadrick said:
I currently have TWRP recovery installed, and I attempted to flash the jellybean CM10 as well as the AOKP rom, and I got as far as the unicorn and I actually manged to get the phone to boot to the main screen with all the icons, but it would constantly reboot after being on for maybe a minute
I tried flashing everything back to stock including restoring a backup I had previously taken with TWRP, but no luck
I also tried flashing the stock rom downloaded somewhere here on XDA and I even flashed the stock recovery, but all I got was constant rebooting.
it would get as far as the startup animation and then reboot indefinitely
I'm at a total loss here. I've seen a few links with some resources that look like they might have been helpful (like on this thread) but the links are dead, and I also read somewhere that HTC was putting the kibosh on a site that had some stock roms.
I'd prefer to get jellybean working on my phone, but ultimately, I just want a working phone.
I've followed the process of installing the rom - some instructions said to flash the boot img before flashing the rom, some say after
I've tried both methods
I went into recovery, mounted the usbmsd and copied the rom, and used recovery to install the rom after having cleared the cache, davlik cache and wiping the data (factory reset)
I also installed the gapps package after the rom, but I don't think that's critical to getting it to just boot.
Click to expand...
Click to collapse
I think I'm having the same problem. The phone boots, gets as far as the "this build is for development purposes..." and then hangs for a few minutes and restarts, over and over. The flash with fastboot seemed to work fine and reported no errors.
EpicLordPhone said:
So, this happend to my htc and I ruu'ed back to stock, after continunously trying to install roms with constant bootloops. I did the ota update again. So if I want to install a custom rom your saying DONT do the ota after ruu'ing then install one after rooting?
Click to expand...
Click to collapse
Yes. Do NOT install the update if you want to flash another ROM onto your device. Use the RUU to get the device back to factory; this will restore the original radio version. Then go through the steps to unlock the bootloader, root, and flash your ROM as desired. There are other forums which explain the mentioned processes better.
BeyondExistence says that this is fixed with a "4.2 SickleKernel", but as far as I'm aware there are no JB 4.2 ROMs for the HTC One V. Maybe a little more information would be in order?
Bheadrick:
I'm not quite sure what you mean when you say you flashed the stock recovery. The One V doesn't have a recovery when everything is stock.
You will have to RUU your device back (have you read any of the posts in this and other forums??). The process will reinstall the stock rom, relock your bootloader, remove the recovery, etc.
I recommend that you use Paranoid android's rom with the latest SuperSick kernel. Its been my favorite and most stable build I've used.
Sent from my Nexus 7 using xda app-developers app
So I found what BeyondExistence might have been talking about (for those of you who care/are currently having the bootloop problem and would rather go with this route). Its called RhythmicRom. This is a 4.2.2 ROM and it has some cool things for users switching from Sense to a more-pure Android [Link here]. Its based off of CM10.1 for the One V and it includes the BeatsAudio app (which most ROMs don't, as far as I know).
The reason I think that this is worth mentioning is because whoever runs into this bootlooping problem can simply SKIP the RUU process and just move onto this ROM. Hit thanks if this helped!
Newest OTA update.
As some of you may have seen, there's an even newer OTA Update available through the stock ROM. As always, this will cause problems when you try to flash a different kernel, resulting in bootlooping (can anyone who has done the newest update confirm?). Anyway, I've also read that this update also updates your hboot (which, since I haven't and will not apply the update, don't know why it would impede you from flashing any other ROM/kernel but it does) and radio version.
I've looked for additional ROMs who try and make their builds compatible, but so far only RhythmicRom has done anything worthwhile (in my opinion). His latest v 1.3 build will be out soon, and I highly recommend it.
If you flashed both OTA updates, then please be sure to include that when making any post.
filoxo said:
As some of you may have seen, there's an even newer OTA Update available through the stock ROM. As always, this will cause problems when you try to flash a different kernel, resulting in bootlooping (can anyone who has done the newest update confirm?). Anyway, I've also read that this update also updates your hboot (which, since I haven't and will not apply the update, don't know why it would impede you from flashing any other ROM/kernel but it does) and radio version.
I've looked for additional ROMs who try and make their builds compatible, but so far only RhythmicRom has done anything worthwhile (in my opinion). His latest v 1.3 build will be out soon, and I highly recommend it.
If you flashed both OTA updates, then please be sure to include that when making any post.
Click to expand...
Click to collapse
I got my One V at the end of December and did the OTA update at the beginning of April. Last week, I decided to try messing with loading some different ROMs and have encountered all of the problems you've mentioned (e.g., boot-looping, inability to RUU back to stock). I have successfully gotten RhythmicRom to load using this OTA_support.zip (which has been incorporated into the regular release since I flashed it). I have also gotten the most recent version of PACman v22.1 to run (using the same kernel as RhythmicRom) without boot-looping, but the performance hasn't been great (browser crashes frequently and it seems like the launcher has to restart a lot). User demi_fiend has said that the PACman ROM will work using the CodefireX kernel from user BeyondExistence.
I had also tried to revert back to my stock CWM recovery, but it had the boot-loop problem too. However, demi_fiend has also informed me that you can revert to a stock backup by using the boot.img file that is located in the backup folder. I haven't had the chance to verify this, but I wouldn't be surprised if it were true.
It's a bit of a pickle being unable to revert back to previous radio versions, but there is hope that some of the devs will incorporate this issue into their new builds.
tallnproud said:
I got my One V at the end of December and did the OTA update at the beginning of April. Last week, I decided to try messing with loading some different ROMs and have encountered all of the problems you've mentioned (e.g., boot-looping, inability to RUU back to stock). I have successfully gotten RhythmicRom to load using this OTA_support.zip (which has been incorporated into the regular release since I flashed it). I have also gotten the most recent version of PACman v22.1 to run (using the same kernel as RhythmicRom) without boot-looping, but the performance hasn't been great (browser crashes frequently and it seems like the launcher has to restart a lot). User demi_fiend has said that the PACman ROM will work using the CodefireX kernel from user BeyondExistence.
I had also tried to revert back to my stock CWM recovery, but it had the boot-loop problem too. However, demi_fiend has also informed me that you can revert to a stock backup by using the boot.img file that is located in the backup folder. I haven't had the chance to verify this, but I wouldn't be surprised if it were true.
It's a bit of a pickle being unable to revert back to previous radio versions, but there is hope that some of the devs will incorporate this issue into their new builds.
Click to expand...
Click to collapse
Did you flash stock recovery and lock bootloader before running RUU?
Lsesp said:
Did you flash stock recovery and lock bootloader before running RUU?
Click to expand...
Click to collapse
I had flashed my stock recovery (although it was still boot-looping), and I did re-lock the bootloader before running the RUU.
I used the instructions found here.
I recently learned to flash,
So I used TWRPV to flash coz i cant access the recovery mode becoz of rooting.
1.Flashed Slim Bean. Worked perfectly.
2.Try to flash jellybam. Got flashin failed.
3. Reflshed Slim Bean.
4. Tried to flash Miui rom. Again got error, after googling i found that i have to delete two lines from the script in miui rom with note++
I did that but not worked, then i myself checked the slimbean script, and deleted some more lines from miui script and flashed, still not worked.
5. I did same to jellybam. Then one of jellybam rom worked.
6. Now after reboot some times note 2 switch off itself when in pocket or in table. Or sometime while charging with big battery on screen with stuck tiny round circle. I have to remove the battery to switch on.
and i can't turn on bluetooth also USB not working. In pc device manager when i connect phone to pc via usb it shows CDC COMMUNICATION INTERFACE (7 times), and Com neon Suspend (1 Times)
7. Now using slimbean but problem is still there.
Any idea what happened to my n7100, is my phones efs corrupted, or soft/hard bricked,
I don't have any backups.
Can anybody please help me. I posted it here coz I can't find the same problem anywhere. There arevsimilars but they are different.
And bad English coz I'm Apatani.
Sorry for that.
My note 3 was SICK from some times (from 7 Months)
Some said it was EFS corruption. my problem was occurred because I flashed my N7100 with MIUI rom built for Galaxy S3.
My Bluetooth was not turning ON (Blank in bluetooth adress), Usb not workin with PC, turning of or Freeze while phone sleeps or auto lock.
Tried many things Flashed different Modem or Kernels, Flashed all of the custom roms available for N7100, Flashed Stock from SamMobile site.
and Lost hope... then I continued my daily life with my N7100 (using Red EYE sleep disabler)
But now today I already using Ditto Note 3 v.3.0 (Used v.1.0,v.2.0,)
today Flashed Ditto Note 3 v.3.1.1 with aroma
Selected everything in Aroma Inataller (Including Updated Modem)
then in First Boot my N7100 Freezed while i was entering my Wifi Pin First Device Setup
Waithed for more then 1/2 hour but still Freezed...
then i rebooted it with removing my N7100 Batteries
then again Boot and it Widened my eyes, my mouth was open, and i was Smilin...
My N7100 Bluetooth was turning ON, my USB is connecting to PC without any secret code for UART mode, my Phablets screen turned off, I waited for around half Hour and then i Pushed my Home Button and it respond and turned on the Screen.
Firstly your very brave to do this or your too Rich to afford a new device if you brick it .
Now firstly Please dont make any changes to the existing Rom that you have downloaded seeing other Rom scripts ,
Now before flashing any rom go trough the OP to understand what OP has mentioned about flashing.
Dont Refer to Google refer to ROM OP OR THREAD any question you have post it there so you will get quick response.
aukhahaven said:
Firstly your very brave to do this or your too Rich to afford a new device if you brick it .
Now firstly Please dont make any changes to the existing Rom that you have downloaded seeing other Rom scripts ,
Now before flashing any rom go trough the OP to understand what OP has mentioned about flashing.
Dont Refer to Google refer to ROM OP OR THREAD any question you have post it there so you will get quick response.
Click to expand...
Click to collapse
Thanks...
But I'm confused, what should I do now...
And I don't have that much money to afford another device like this one...
Is there any fix or solution for this problem...
bullooka said:
Thanks...
But I'm confused, what should I do now...
And I don't have that much money to afford another device like this one...
Is there any fix or solution for this problem...
Click to expand...
Click to collapse
Well since your phn is acting weird better flash stock rom via odin and see if the prob persist if all is fine then gv a fresh start flashing recovery and stuff and use philz recovery for flashing if it acts weird than just make the flash counter 0 and take it to service center for precise details go though ketan thread
bullooka said:
Thanks...
But I'm confused, what should I do now...
And I don't have that much money to afford another device like this one...
Is there any fix or solution for this problem...
Click to expand...
Click to collapse
Download Stock ROM,
Flash it it Via Mobile Odin or PC ondin,
Once flash completes Boot into recovery and do a Factory Reset+User data ,this will wipe everything on your device memory .
and then tell which rom you want to flash ill guide on how to do it.
aukhan said:
Download Stock ROM,
Flash it it Via Mobile Odin or PC ondin,
Once flash completes Boot into recovery and do a Factory Reset+User data ,this will wipe everything on your device memory .
and then tell which rom you want to flash ill guide on how to do it.
Click to expand...
Click to collapse
Okay.
I'll inform u when i'am ready...
In my place broadband or network is not that good, to download stock ROM it will take some time.
And thanks for helping me.
bullooka said:
Okay.
I'll inform u when i'am ready...
In my place broadband or network is not that good, to download stock ROM it will take some time.
And thanks for helping me.
Click to expand...
Click to collapse
no problem any time
aukhan said:
no problem any t
Click to expand...
Click to collapse
Actually, I think I found out what exactly happened to my note 2.
The ROM I tried to flash was for s3 (MIUIv5 I9300 Note 2 Edition 3.6.21 by @muchopoli83)
This ROM was flashed after removing the two lines from updater script, the assert lines.
But after flashing my phone didn't started so I changed the ROM.
So, what should I do. Is stock ROM still important.
If yes can u please give me the link.
I found one with pit file in xda but that link is not working
And some guys with similar problems are talking that every stock ROMs are not working for problems like this.
bullooka said:
Actually, I think I found out what exactly happened to my note 2.
The ROM I tried to flash was for s3 (MIUIv5 I9300 Note 2 Edition 3.6.21 by @muchopoli83)
This ROM was flashed after removing the two lines from updater script, the assert lines.
But after flashing my phone didn't started so I changed the ROM.
So, what should I do. Is stock ROM still important.
If yes can u please give me the link.
I found one with pit file in xda but that link is not working
And some guys with similar problems are talking that every stock ROMs are not working for problems like this.
Click to expand...
Click to collapse
You could be in serious trouble since youve flashed s3 Rom just keep your fingers crossed thinking that its not corrupted your EFS folder
what Model is your device N7100 or n7105 which 1 >?
aukhan said:
You could be in serious trouble since youve flashed s3 Rom just keep your fingers crossed thinking that its not corrupted your EFS folder
what Model is your device N7100 or n7105 which 1 >?
Click to expand...
Click to collapse
My device model is N7100,
and today I found out that my Bluetooth is also not working, I can't switch it on.
shhbz said:
Well since your phn is acting weird better flash stock rom via odin and see if the prob persist if all is fine then gv a fresh start flashing recovery and stuff and use philz recovery for flashing if it acts weird than just make the flash counter 0 and take it to service center for precise details go though ketan thread
Click to expand...
Click to collapse
Actually I accidentally flashed the wrong ROM . S3 I9300 ROM in my Note 2 N7100.
Is there any other ways to fix this
aukhan said:
You could be in serious trouble since youve flashed s3 Rom just keep your fingers crossed thinking that its not corrupted your EFS folder
what Model is your device N7100 or n7105 which 1 >?
Click to expand...
Click to collapse
My model is N7100.
Can you tell me what happened to my note2, efs damage or soft/hard bricked
And what should I do.
Please tell me.:crying:
Still got the problem
Still got the problem and cant find any solution
anybody any idea
Simply go to recovery wipe everything including format_system,
then choose any rom from N7100 development thread as your suitability .
and flash in recovery as per instructions given in OP
Then tell here what happened
looks like efs croupt no worries just flash stock rom from odin then root it with cf-root method
use triangle away to remove the flash counter and then reboot unroot from su app and ur good to go to service center
just tell them i updated this phone to latest from ota and it failed iam when it restarted there was no cellular
bullooka said:
Still got the problem and cant find any solution
anybody any idea
Click to expand...
Click to collapse
Do you have GSM network?
Flash Stock ROM via PC Odin v3.09 and use re-partition and Nand erase all with PIT file, Freset Autoreboot.
After flash complete everything must be ok.
I had the same problem few weeks ago. I also tried to flash alot of ROMs but same problem exist. found a solution to this problem yesterday this is what I did
1. Download leaked 4.3 it will take time because the file is 1.2gb
http://forum.xda-developers.com/showthread.php?t=2499794
2. After download flash it via Odin in pda. Make sure auto reboot and f.Reset time only have check.
3. If the flash fails, it's ok but make sure it already flashed the radio and modem.
4. Reboot again in download mode then flash Philz recovery
5. Reboot in recovery mode then flash slimbean rom or any rom you prefer.
6. Install gapps
7. Wipe cache and dalvik
8. Reboot and your ok now
I'm in slimrom build 2 now. Bluetooth is ok and no more reboot when phone sleeps after few seconds.
Hope this helps.
Sent from my GT-N7100 using xda app-developers app
taticuio said:
Do you have GSM network?
Flash Stock ROM via PC Odin v3.09 and use re-partition and Nand erase all with PIT file, Freset Autoreboot.
After flash complete everything must be ok.
Click to expand...
Click to collapse
Got the GSM, WIFI is also OK but bluetooth,USB and reboot on sleep. but what re-partition and Nand erase work for and what is PIT file and where should i get it
any help
Still got the problem
Ok i'll try the leaked version and thanks for reply
bullooka said:
Got the GSM, WIFI is also OK but bluetooth,USB and reboot on sleep. but what re-partition and Nand erase work for and what is PIT file and where should i get it
any help
Click to expand...
Click to collapse
Never try to touch or else you'll get a big problem.
Sent from my GT-N7100 using xda app-developers app
So, first off, just wanna say that I have a RIDICULOUS amount of experience with flashing roms. Literally over 100 different devices and 1000s of different flashes of my own devices on top of it. Quite familiar with this S2 as well and have customized them to all sorts of extents, but this one has me baffled. This phone refuses to run 4.2.2/4.3/4.4.x roms. Using the most up to date radio and the suggested TWRP (2.6.1.0) as well as CWM 6.0.44 and the newer TWRP: 2.6.3.0. Every time the phone will get to the set up screen, refreeze and boot. No issues running stock or stock based 4.1.2 roms. I've tried changing recoveries, wiping everything (/system, /data, /caches) repeatedly, Odin back to stock and redoing everything, switching kernels, wiping caches before rebooting and leaving it be, changing batteries, etc but nothing has worked. So far I've tried BlackLiquid 2.92 (4.2.2 stable), Awesome Audio rom (4.3), official CM11 (whatever the last build up was last night), and BeanStalk 4.4.2 (12/16) and all behave exactly the same - freeze on start up and reboot. This doesn't seem to be much of a widespread issue obviously, so just baffled and getting a bit frustrated as this should have been a 20 minute process that has turned into a few hours already. Since USB Debugging isn't on by default on newer roms, how would I even do a logcat to see if there is anything meaningful there? Any ideas?
Update: I have another S2. Performed same steps, same TWRP, same radio and rom, on same external SD card and that one booted right up like normal confirming that it is the phone itself, but what causes that?? Corrupted partitions?
I have the same problem, just format your internal and external sd card with just ROM file on your storage then try to install, than please inform me
Sent from my SGH-T989 using XDA Premium 4 mobile app
iamdofus said:
I have the same problem, just format your internal and external sd card with just ROM file on your storage then try to install, than please inform me
Sent from my SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nope. No luck there (only tried Beanstalk so far, but exact same issue). Thanks for the suggestion though! Only using internal storage, no SD card, though thinking I might try that next...
Edit: Just to be thorough, I formatted internal storage via TWRP and my computer then readded the files and just tried to boot rom only and freezes before I can do anything.
Do you by chance have a refurbished s2?
The screen has been replaced by a friend of mine and he managed to mess up the soft keys with it, but everything else functions. That's actually why he sent it to me, so I could hook him up with Pie and all that kind of thing so the soft keys aren't an issue. What's your thoughts on the refurb side of it?
es0tericcha0s said:
The screen has been replaced by a friend of mine and he managed to mess up the soft keys with it, but everything else functions. That's actually why he sent it to me, so I could hook him up with Pie and all that kind of thing so the soft keys aren't an issue. What's your thoughts on the refurb side of it?
Click to expand...
Click to collapse
OK thanks for reply, I have one more solution give me. Some time I will give try that it worked for me.
Sent from my SGH-T989 using XDA Premium 4 mobile app
es0tericcha0s said:
Nope. No luck there (only tried Beanstalk so far, but exact same issue). Thanks for the suggestion though! Only using internal storage, no SD card, though thinking I might try that next...
Edit: Just to be thorough, I formatted internal storage via TWRP and my computer then readded the files and just tried to boot rom only and freezes before I can do anything.
Click to expand...
Click to collapse
ok lets stat it with this
1) download both the scripts of infamous wipe cache and infamous super wipe.
2) format your both SD card with PC (FAT32)
2) put both these wipe files and and your rom file ( i prefer try slimbean rom first)
3) Now in twrp 2.6.0.0- follow the steps
i) format your phone with twrp options
ii) again format your phone with infamous super file. (by going in to INSTALL ZIP file option in TWRP)
iii) than format with infamouse cache file (by going in to INSTALL ZIP file option in TWRP)
iv) install your rom and compatiable GAPPS zip file.
v) after installing or somewhere between procedure if twrp says something about supersu birnaries are not correct than click on DO . NOT FIX
vi) again format infamouse cache wipe.
vii) now FINALLY reboot the rom.
it should work, and it worked for me. if u sucessfully run the rom than you can eailsy run all the AOSP roms in this forum. Again If you try this please do tell me what happend.
Followed to a "T" and still in the same boat - freezes after bootup. I used those same steps before with another darkside wipe script (maybe older?) but yea, have already been down that road. I did downgrade to 2.6.0.0 and used Slim 4.3 because 4.4 is supposed to use the newer TWRP, just to be certain, but GRRR. I guess we're just gonna have to settle for a 4.1.2 rom and call it a day. :/
So here are the log output from the wipes:
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.SUPER.WIPE_recovery.log
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.CACHE.WIPE_recovery.log
I see some stuff at the bottom of those that might indicate something weird, but I am not adept at interpreting these, so just wondering if someone could point me to the right direction about the repair checks and what not listed on these. Thanks!
Edit 2: I did get a AOSP based 4.1.2 rom to boot with no problems! wtf... LoL
Last Edit:
Problem solved! I used basically the same steps I had been doing but once the AOSP 4.1.2 rom booted then now everything works like it should again. Have loaded a 4.3 and 4.4 rom successfully. Thanks for the help!
es0tericcha0s said:
So, first off, just wanna say that I have a RIDICULOUS amount of experience with flashing roms. Literally over 100 different devices and 1000s of different flashes of my own devices on top of it. Quite familiar with this S2 as well and have customized them to all sorts of extents, but this one has me baffled. This phone refuses to run 4.2.2/4.3/4.4.x roms. Using the most up to date radio and the suggested TWRP (2.6.1.0) as well as CWM 6.0.44 and the newer TWRP: 2.6.3.0. Every time the phone will get to the set up screen, refreeze and boot. No issues running stock or stock based 4.1.2 roms. I've tried changing recoveries, wiping everything (/system, /data, /caches) repeatedly, Odin back to stock and redoing everything, switching kernels, wiping caches before rebooting and leaving it be, changing batteries, etc but nothing has worked. So far I've tried BlackLiquid 2.92 (4.2.2 stable), Awesome Audio rom (4.3), official CM11 (whatever the last build up was last night), and BeanStalk 4.4.2 (12/16) and all behave exactly the same - freeze on start up and reboot. This doesn't seem to be much of a widespread issue obviously, so just baffled and getting a bit frustrated as this should have been a 20 minute process that has turned into a few hours already. Since USB Debugging isn't on by default on newer roms, how would I even do a logcat to see if there is anything meaningful there? Any ideas?
Update: I have another S2. Performed same steps, same TWRP, same radio and rom, on same external SD card and that one booted right up like normal confirming that it is the phone itself, but what causes that?? Corrupted partitions?
Click to expand...
Click to collapse
Interesting, so you're saying it's phone specific?
That begs to ask other questions now:
1. Where did this phone come from? is it a Tmobile version (SGH-T989) or AT&T (i-1900)?
2. You mentioned you got it from a friend; did it come rooted? unlocked? Or did you have to do that process yourself?
UltimaniumX said:
Interesting, so you're saying it's phone specific?
That begs to ask other questions now:
1. Where did this phone come from? is it a Tmobile version (SGH-T989) or AT&T (i-1900)?
2. You mentioned you got it from a friend; did it come rooted? unlocked? Or did you have to do that process yourself?
Click to expand...
Click to collapse
Yep, very much phone specific. Used same recovery, same rom zip and gapps off the same external SD card, to be certain. That one updated just like every other S2 I've done. And it's the Tmo version. The At&t models are i777 S2 or i727 S2 Skyrocket. The i9100 is international and has a physical home button. But the phone was not modified at all. No root, custom recovery, etc. I was only able to resolve it by first starting with an AOSP 4.1.2 rom and working my way up to 4.4. One of the weirder issues I've come across.
es0tericcha0s said:
Followed to a "T" and still in the same boat - freezes after bootup. I used those same steps before with another darkside wipe script (maybe older?) but yea, have already been down that road. I did downgrade to 2.6.0.0 and used Slim 4.3 because 4.4 is supposed to use the newer TWRP, just to be certain, but GRRR. I guess we're just gonna have to settle for a 4.1.2 rom and call it a day. :/
So here are the log output from the wipes:
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.SUPER.WIPE_recovery.log
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.CACHE.WIPE_recovery.log
I see some stuff at the bottom of those that might indicate something weird, but I am not adept at interpreting these, so just wondering if someone could point me to the right direction about the repair checks and what not listed on these. Thanks!
Edit 2: I did get a AOSP based 4.1.2 rom to boot with no problems! wtf... LoL
Last Edit:
Problem solved! I used basically the same steps I had been doing but once the AOSP 4.1.2 rom booted then now everything works like it should again. Have loaded a 4.3 and 4.4 rom successfully. Thanks for the help!
Click to expand...
Click to collapse
What did you exactly do? I flashed a 4.1.2 and then flashed a 4.3 based ROM and it didn't work. What recovery version did you use to flash the 4.3 ROM?
tpag02 said:
What did you exactly do? I flashed a 4.1.2 and then flashed a 4.3 based ROM and it didn't work. What recovery version did you use to flash the 4.3 ROM?
Click to expand...
Click to collapse
Sorry, I don't pay attention to the notifications on XDA very often. I don't usually browse the S2 forums unless needed because I have an N5, but anyway... The 4.1.2 rom you used, was it TW or AOSP type? I used 2.6.0 to wipe everything, then used cache and superwipe zips then 4.1.2 AOSP type rom then cache wipe zip again then after that booted, I was able to go back to 2.6.1 and flash a 4.3 via wiping, wipe zips, installing rom then cache wipe again. After that, repeated with a KK rom and now it loads roms just like it should. If you want more precise help, feel free to hit me up on Hangouts with my username: es0tericcha0s. Good luck! I know how frustrating it can be when it gets a little out of whack like this...
I'm in the same boat
Same here. I just bought a galaxy s2 from my friend (tmobile version) and I too get stuck in a bootloop no matter what rom I use. It boots up freezes then reboots 7 keeps doing that endelessly. I've even wiped using twrp & darkside then reflashed the stock rom in odin, but no luck. strangely it only happens on the cellular network, otherwise it works fine on wifi. But when I turn off the wifi and go to the cellular network I can't even turn on the wifi anymore and still stuck in this boot loop It's wierd and frustrating.
DennyTek said:
Same here. I just bought a galaxy s2 from my friend (tmobile version) and I too get stuck in a bootloop no matter what rom I use. It boots up freezes then reboots 7 keeps doing that endelessly. I've even wiped using twrp & darkside then reflashed the stock rom in odin, but no luck. strangely it only happens on the cellular network, otherwise it works fine on wifi. But when I turn off the wifi and go to the cellular network I can't even turn on the wifi anymore and still stuck in this boot loop It's wierd and frustrating.
Click to expand...
Click to collapse
Hmm. That's interesting... This is happening on the stock rom - where you turn on cellular data and it reboots? Definitely a different issue than the one I was having. Which stock rom were you flashing via Odin? Have you tried other versions of the stock rom and had the same problem?
TMO 4.1.2
es0tericcha0s said:
Hmm. That's interesting... This is happening on the stock rom - where you turn on cellular data and it reboots? Definitely a different issue than the one I was having. Which stock rom were you flashing via Odin? Have you tried other versions of the stock rom and had the same problem?
Click to expand...
Click to collapse
This was happening on any rom I used (Cm 10.2 stable, Cm 11 nightly, AOKP & Super Nexus 3.0 which is Android 4.3) I can't really speak for the stock rom (tmo 4.1.2) since I've never used it for more that 5 minutes, sigh but I'll try it and see if it gives me the same problem :/
Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk
yep
wikitiki said:
Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
ya, well at least I am anyways
wikitiki said:
Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
I had tried with and without and did not make any difference.
DennyTek said:
This was happening on any rom I used (Cm 10.2 stable, Cm 11 nightly, AOKP & Super Nexus 3.0 which is Android 4.3) I can't really speak for the stock rom (tmo 4.1.2) since I've never used it for more that 5 minutes, sigh but I'll try it and see if it gives me the same problem :/
Click to expand...
Click to collapse
I just started working on a VZW S3 on T-Mobile service that has this issue. Happens on stock VZW 4.1.2, stock T-Mobile 4.1.2 rom, custom 4.1.2 T-Mobile rom, and stable CM 10.2. Weirdest thing... full wipes including /system inbetween each flash. Changed the modem too. Nothing helps. Pretty sure it's a bad board at this stage.
Cool beans, 0! Having this exact problem, will try your method for my s2, btw which aosp 4.1.2 did u use? Can I get a link? Thanks been having the problem for a few months now and just gave up haha, been super thirsty for that beanstalk kk build
One last thing can u also provide a link to the 4.3 that u used? I really want it to work and want to follow what u did to the , megabyte