I've been casually installing ROMs for the past year on my Galaxy Note, and know my way around with no problems. That is until I was rushing through and deleted the OS one time - I know, whatever. It happens. (formatted /system)
So I installed stock ICS via ODIN (IMG file) and then flashed CWM, and then installed TWRP2. All around functional, everything is great.
This is the problem though: when I flash CyanogenMod 10 (Stable), it gets stuck at the spinning boot logo (boot loop) for over 20 min. I've read about flashing RUU but I don't really understand it. I've tried. I gather that it has something to do with the modem, but I can send and receive data/texts perfectly fine. Could anyone please help me out?
Thanks!
I had the 10 minute wheel , I didn't wait ,I went back in to recovery ,wiped (cache,dalvik,reset) re installed worked flawless
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Dirty flash, or bad download I would guess...
And the loop is likely kernel related, as opposed to modem ....g
Related
Ok, here's the deal:
Rooted the device, everything was a-ok.
Installed Clockwork, everything still a-ok.
Tried using mod manager to install Cyanogen nightly 9, phone rebooted and the progress bar for the mod install wouldn't move. I waited for a while and eventually manually turned the device off as it wasn't making any progress.
Ever since, it won't go past the screen you get at the beginning (w/ the yellow sign indicating an unsecured rom). It just stays there forever.
What I have to work with:
- Clockwork Recovery is available.
- The device is recognized by Odin when in download mode.
- The device is not recognized by the computer/Kies.
What I've tried:
- Followed the instruction for boot loop w/ both stock rom and Villain (no dice).
I'm sorta freaking out now. I have yet to see anyone having the same problem online and I really hope it's not bricked - a 600$ paperweight...
Is there something else I can try? Is it possible to flash stock PIT/Bootloader/PDA/everything else? If it is, would it fix the problem?
Please just point me in the right direction.
Thank You,
Edit: In recovery mode, the following error appears:
- Can't access to "/system/csc/VMC/system/"
Edit: In download mode, the current binary is set to "Samsung Official". Therefore I think this isn't the problem.
Edit: OMG OMG holy crap. Problem has been solved. Got a friend who had the same phone from the same provider to tell me what the firmware for the phone was. Downloaded it. Installed it w/ Odin. I almost turned religious when it booted a bit slower than what I remembered. It works well enough now, although I will probably go exchange it for a new one ASAP, before my warranty expires.
If anyone has similar problems. Don't panic and re-install stock firmware.
Cheers Folks!
Rovah said:
Ok, here's the deal:
Rooted the device, everything was a-ok.
Installed Clockwork, everything still a-ok.
Tried using mod manager to install Cyanogen nightly 9, phone rebooted and the progress bar for the mod install wouldn't move. I waited for a while and eventually manually turned the device off as it wasn't making any progress.
Ever since, it won't go past the screen you get at the beginning (w/ the yellow sign indicating an unsecured rom). It just stays there forever.
What I have to work with:
- Clockwork Recovery is available.
- The device is recognized by Odin when in download mode.
- The device is not recognized by the computer/Kies.
What I've tried:
- Followed the instruction for boot loop w/ both stock rom and Villain (no dice).
I'm sorta freaking out now. I have yet to see anyone having the same problem online and I really hope it's not bricked - a 600$ paperweight...
Is there something else I can try? Is it possible to flash stock PIT/Bootloader/PDA/everything else? If it is, would it fix the problem?
Please just point me in the right direction.
Thank You,
Edit: In recovery mode, the following error appears:
- Can't access to "/system/csc/VMC/system/"
Edit: In download mode, the current binary is set to "Samsung Official". Therefore I think this isn't the problem.
Edit: OMG OMG holy crap. Problem has been solved. Got a friend who had the same phone from the same provider to tell me what the firmware for the phone was. Downloaded it. Installed it w/ Odin. I almost turned religious when it booted a bit slower than what I remembered. It works well enough now, although I will probably go exchange it for a new one ASAP, before my warranty expires.
If anyone has similar problems. Don't panic and re-install stock firmware.
Cheers Folks!
Click to expand...
Click to collapse
Same problem. anyone?
Vincho said:
Same problem. anyone?
Click to expand...
Click to collapse
Did you read the answer ???
jje
Look online (samfirmware), ask friends or on forums for anyone who has the SGS2 w/ the same carrier in the same country and try to find the firmware version (I9100***** - the stars are letter codes). Then just download that firmware and use Odin to install it.
If you can't find it,you presumably could just flash any stock firmware and it might work (or it might make things worse, try at your own risk)
Rovah said:
Tried using mod manager to install Cyanogen nightly 9, phone rebooted and the progress bar for the mod install wouldn't move. I waited for a while and eventually manually turned the device off as it wasn't making any progress.
Click to expand...
Click to collapse
The progress bar not moving is a known issue with the CM7 Recovery. All you need to do is wait for it to say that it's finished. There is nothing wrong with your phone and no need to return it. You just cancelled the CM7 install part way through which meant not all required files were installed on the phone, causing it to not boot.
As for it taking longer to boot into android after the odin reflash. That's because it has to build up it's dalvik-cache again. This is completely normal any time you install a new rom. It only happens on first boot of a rom.
So again, no need to return your device and feel free to try CM7 again. Just remember to let it finish even if the progress bar isn't moving.
Ahh. Ok that makes sense. This ought to teach me to read before screwing around w/ my phone.
I wanted to exchange it because I wasnt sure i'd still be able to install official Samsung firmware updates through Kies.
Suppose an official 2.3.4 firmware comes out, would i be able to install it through Kies?
Sent from my GT-I9100 using XDA App
Rovah said:
Ahh. Ok that makes sense. This ought to teach me to read before screwing around w/ my phone.
I wanted to exchange it because I wasnt sure i'd still be able to install official Samsung firmware updates through Kies.
Suppose an official 2.3.4 firmware comes out, would i be able to install it through Kies?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Yes, as long as the firmware you're flashing is the same as the stock version that came on the phone. And even if not, you'll get the kies updates for whatever region firmware you did flash onto the phone.
I see. Thanks a lot!
Is there any danger to flashing firmware from a different region than the one youre from?
Sent from my GT-I9100 using XDA App
I have been flashing roms for at least a year now with no problems. For some reason, recently I can flash some roms fine and some roms only boot loop or boot freeze. I am currently using Bamf SoaB v1.0. when I tried to flash iBolt v0.90 the most I can get is to the MUIU boot screen and it either boot loops or freezes. I can boot OMFG roms and others fine as well and have ran into other roms that boot loop and freeze also. I have even had an issue with recovery boot looping in the middle of trying to load a rom or wipe. I have tried different Recoveries with no luck. I am wiping everything every time I flash. I even returned to stock Ruu with S-on and rerooted and no luck. Does anyone have any ideas?
Did you check the md5 of the file? Maybe it was a bad download
Update to newest CWM and use newest recovery or use 3.0.2.5 that was always a great one for flashing with no issue or boot loops.
If I helped you in any way please use the thank you button.
1) you aren't wiping (probably not the case since you've done this b4)
2) bad/corrupt rom download (check md5 as suggested)
3) recovery borked causing failures (reflash newest recovery)
4) recovery outdated and those roms require an updated version (reflash newest recovery)
5) your phone doesn't like the kernel and/or default clock speeds of the rom you are flashing (use different rom or flash a different kernel immediately after the rom *YMMV*)
.
.
.
15) hardware failure (get new phone) *not really failure, just not living up to potential*
All that is meant by the dots is to indicate that there are a few other things to check before settling on it being a hw problem but I can't think of any right now.
After eliminating the likely causes described above, you may want to check your recovery log immediately after you flash. Export the log to the sd card, then examine the log file from your computer.
I am a frequent rom flasher, and I have had issues with bad nand blocks only being a problem to me with select roms and not others. Little bit of weirdness.
I have not received my thunderbolt yet, so I am only assuming that htc designed the internal and sd memory in your phone in a similar manner to my sexy nexy. Please correct me if I am wrong!
Sent from my Nexus One using xda premium
Thanks for all the help. The issue seemed to be a kernal problem. At least with ibolt it was. Sad thing after all that work and time and losing everything on my SD I ended up not caring much for the rom. lol At least I know what to try if the problem happens on other roms.
For some reason when I flashed Jellybean I was stuck in a bootloop and it looked like it was booting but then it froze at the bootanimation and shutoff I then proceeded to turn it back on. The same thing happened again except this time it turned back on by itself I have restored it since then but I would love to know what happened.
I flashed it and i wiped it like I usually do and then flashed the jellybean Gapps from the 0.01 thread.
please use the 'excellent' search tool that xda provided for us. go to the top of the NT forum and search. it is 'super' cool in that it allow you to see the specific post.
.
i was reading... and i think i understand... that sometimes the new recovery and the old recovery do not get along, and the result is a boot loop. where is raywaldo ? ( chuckle, chuckle, chuckle . . . ) he's been beating his head against this for a long while !
.
have you tried a sd card ( bootable ) cwm recovery ?
mamifsidtect said:
For some reason when I flashed Jellybean I was stuck in a bootloop and it looked like it was booting but then it froze at the bootanimation and shutoff I then proceeded to turn it back on. The same thing happened again except this time it turned back on by itself I have restored it since then but I would love to know what happened.
I flashed it and i wiped it like I usually do and then flashed the jellybean Gapps from the 0.01 thread.
Click to expand...
Click to collapse
Same here eventually it loaded I just let it keep going after about four boot loops it loaded does not happen after first load.
Sent from my NookTablet using xda app-developers app
similar thing here
I had a kind of “boot loop" with 0.02 too: constantly reboot after the boot loader screen or at the animation.
But after several (I guess 8) failures, NT started an "official" wipe process (my emmc recovery is stock one, not sure if that played a role), and after that, guess what, the system started. The animation stalled a lot at the first time, but eventually it started.
I got crashes (black screen with backlight on) 3 times yesterday. And the battery drain over a night, with wifi on, is like 20% percent. Aside from those, it seems a pretty usable system. The sliding is smoother than 4.0, but not as good as that on i9000 with alpha Jelly Bean.
It's what Custom Recovery your running MOST likely... Try the new Clockworkmod or TWRP
in another thread it was stated that flashing jellybean or any 3.0.x kernel based rom with a cwm recovery that isn't version 5.5.x will result in a bootloop.
thats because v5.5.x of cwm was compiled from cm9/10 whereas cwm v5.0.x was compiled from cm7.
hope this helps.
credit goes to succulent for this info, you can find him at iamafanof.wordpress.com
Hi Guys,
i have a Sony Tablet S (first version, not Xperia) with 4.0.3 r5a (prerooted with AiO and old hidden.img) and it gets stuck on every second reboot, that means:
- Tablet is powered off
- Power on Tablet
- Tablet stuck on Sony logo (Logo refresh one time as you can see on the screen)
- Hold Power for 10 seconds to power down
- Tablet is powered off
- Power on Tablet
- Tablet boots normally
- Reboot Tablet from adb shell or app or just reboot manually (power off/power on)
- Tablet stuck on Sony Logo
- Power off 10 seconds
- Power on
- Tablet boots normally
........ and so on
What i have tried:
- Downgrade to 4.0.3 r1
- Connect via adb while stuck (not possible, adb does not recognize the device in this state)
- Wipe data (through recovery mode)
- Tried to find some log files which gives information (failed badly, logcat only produces output when tablet is already booted, no other logfile found)
Any ideas what could be the reason or what i should check?
Btw, the tab works perfect once it has booted up.
Keep on rockin'
Sony tablets have 2 boot partitions, one of yours is corrupt so the tablet boots to the other one. I think Condi's flasher can fix it, because it flashes both
Sent from my Nexus 4
lopezk38 said:
Sony tablets have 2 boot partitions, one of yours is corrupt so the tablet boots to the other one. I think Condi's flasher can fix it, because it flashes both
Sent from my Nexus 4
Click to expand...
Click to collapse
This is true, or since you have old recover you can use condi's double flash. If you use flasher please install the new recovery as well so it doesn't mess anything up.
I just reflashed 4.0.3 r5a with the actual AiO but so far the problem persists. Flashing went through flawlessly except the stuck on sony logo on the reboots and also the wipe after flash went through with no problems. Device is rooted and working, but still stuck on every second reboot.
Any other ideas?
Keep on rockin'
EDIT: I also tested it now with Flasher 3.0 (not AiO but also from condi) where i chose option 1 4.0.3 r5a wifi+3g and also flashed old recovery (option 2). I had no problems in the update process but the problem is still there.
i got same problem at 4.0
flash stock rom(root-able ver) then root it,the system is ok.
i guess aio tool have some bugs with none us regsions(my is china)
check your regaion.zip,file content,version and permition
Use his flasher tool, not the AiO
@robin
What exactly should i check on region.zip, anything special to look out for?
@lopezk38
As you might have read i also tried with the flasher tool, it wrote both partitions (current system and second system) but the problem persists.
Any other ideas how to fix this?
Keep on rockin'
Still nobody with an idea?
Just flashed custom_prerooted_doubleFLASH_R5A_nbx03_016-ota-121116077.zip from condi's thread @ http://forum.xda-developers.com/showthread.php?t=2020911 but still no luck, always stuck on second boot.
Although i had at least a little bit success with flashing 3.2.1 via AiO, after flashing it and getting stuck on reboot i wiped data in recovery mode and was able to boot at least once into 3.2.1, but after reboot i got stuck again and on second reboot it booted back to 4.0.3
At least that tells me that it is possible to boot from the partition, but something is still wrong.
I really appreciate all the help and the work from you guys.
On another note, i'm pretty firm with shell commands (long time linux user), anything i could try to check via adb shell?
Keep on rockin'
Corrupted for sure on the second boot partition, if double flashing does not help then something is really wrong with the second partition.
Sent from my Nexus 4 using xda app-developers app
andyabc said:
Corrupted for sure on the second boot partition, if double flashing does not help then something is really wrong with the second partition.
Click to expand...
Click to collapse
Leaves the question if there is a way to repair it, maybe by copying an image from the working partition with dd to the bad partition. I don' want to give up yet
DudemeisterAT said:
Leaves the question if there is a way to repair it, maybe by copying an image from the working partition with dd to the bad partition. I don' want to give up yet
Click to expand...
Click to collapse
Exactly same issue here since i rooted the device with last AIO 6.4 tool. Still searching for a solution too.
In the meantime i tried two more things to fix this problem.
First i copied the working partition to the not working partition with dd
dd if=/dev/mmcblk0p3 of=/dev/mmcblk0p2
The writing of the partition went through with no problems but it did not help at all. In my last effort to get system0 working again i tried flashing the OTA update (knowing that i will loose adb shell in recovery), but to my surprise after finishing the update successfully i was stuck with the same problem and a working adb shell. It seems OTA was flashed to system0 but is still not able to boot from it
I am running out of ideas and thinking about buying a new tablet (definitlely NOT a Sony Device anymore). Hopefully someone has another idea.
DudemeisterAT said:
In the meantime i tried two more things to fix this problem.
First i copied the working partition to the not working partition with dd
dd if=/dev/mmcblk0p3 of=/dev/mmcblk0p2
The writing of the partition went through with no problems but it did not help at all. In my last effort to get system0 working again i tried flashing the OTA update (knowing that i will loose adb shell in recovery), but to my surprise after finishing the update successfully i was stuck with the same problem and a working adb shell. It seems OTA was flashed to system0 but is still not able to boot from it
I am running out of ideas and thinking about buying a new tablet (definitlely NOT a Sony Device anymore). Hopefully someone has another idea.
Click to expand...
Click to collapse
I have the same problem, have you found a solution?
Sadly i was not able to fix it, i even tried to let the battery run out completely (was my last hope) but no change at all. I am thinking of sending it back again to sony for repair, cause now I am absolutely out of ideas, i think i tried everything possible.
Keep on rockin'
Sent from my Sony Tablet S using xda app-developers app
Any updates on this problem... BUMP
Sent from my Galaxy Nexus using Tapatalk 4
Sadly no, anyway i use my sgs4 more than the sony, much better Hardware just smaller screen. If there is a tab with the same or better specs (like sgs 4) i will buy a new one and give the sony to my brother. Farewell sony, i have enough of your crap.
Sent from my GT-I9505 using xda app-developers app
I have the same problem ! Any help would be greatly appreciated !
Did you try the things written in this thread?
Sent from my GT-I9505 using xda app-developers app
I don't know if there are still people interested in this but i finally got my tablet working again normally and booting up everytime.
Today i powered on the tablet after loading it fully and realised that there was no wifi anymore, i couldnt even enable the wifi adapter itself. After some other issues, including loosing root, i tried to reflash my backup. I went to recovery and selected the zip to flash which resulted in the "error in base sku" message. I tried different rom files which i had saved (custom signed, officialy signed) and none of them seemed to work. Rooting the device also did not work anymore, even if i tried manually executing all the commands, mostly i just got shut down by permission denied.
Anyway, after failing to try and flash the rom named signed-nbx03_016-ota-121116095.zip i luckily got the idea of renaming it to update.zip and put it in the root of the external sd card. I went back to recovery mode and selected the update.zip, flashing started and went through completely. The tablet rebooted and finished installing the rom and i ended up on the standard ics screen. I then took condis AiO and went to root the tablet and after the tablet rebooted it surprisingly booted again normally and after a quick check with super su i knew it was rooted. I did a couple of reboots with and without cable/ac adapter attached and now i am sure, it boots up every single time.
It looks like that the filename update.zip might tell the tablet to flash differently than with another name, at least i like to hope so. Maybe it helps someone out there with the Tab S.
Funny sidenote, two weeks ago i bought a SM-T805
Have fun
So ,im sorry but its a long story. Hopefully someone can help. My note is Rooted Ive been using TWRP. Everything had been fine until 2 days ago. I tried flashing a ROM i found on Goomanger.( I had been running liquid smooth) just wanted to try something different. Anyways it got stuck on a boot loop. Cant remember the name of the Rom. Anyways i was able to get back to recovery, thankfully. But when i wiped and flashed back to liquid smooth it would say optimizing apps, then it would reach a certain number then reboot and star all over again. So then i tried another Rom and the same thing happened. tried flashing back to stock rooted but it would turn on then completely crash and star booting up again. So finally i was able to flash paraandroid 4.1.2 and Gapps, but here is the kicker i have no service (AT&T) says cannot locate network, my IMEI is gone basically the cellular isn't working. Everything else works fine WiFi,apps, camera. Just cant make calls. I really need your guys help please.:crying:
If you have a suggestion please let me know, i hate using an old Iphone
dar101978 said:
So ,im sorry but its a long story. Hopefully someone can help. My note is Rooted Ive been using TWRP. Everything had been fine until 2 days ago. I tried flashing a ROM i found on Goomanger.( I had been running liquid smooth) just wanted to try something different. Anyways it got stuck on a boot loop. Cant remember the name of the Rom. Anyways i was able to get back to recovery, thankfully. But when i wiped and flashed back to liquid smooth it would say optimizing apps, then it would reach a certain number then reboot and star all over again. So then i tried another Rom and the same thing happened. tried flashing back to stock rooted but it would turn on then completely crash and star booting up again. So finally i was able to flash paraandroid 4.1.2 and Gapps, but here is the kicker i have no service (AT&T) says cannot locate network, my IMEI is gone basically the cellular isn't working. Everything else works fine WiFi,apps, camera. Just cant make calls. I really need your guys help please.:crying:
If you have a suggestion please let me know, i hate using an old Iphone
Click to expand...
Click to collapse
Just odin back to stock. Get a complete factory stock image from the main sticky thread and flash it with Odin and Download Mode. There's a bug on one of the TWRP versions with 4.3-based ROMs that will put it into a bootloop by breaking device reboots. I was unable to flash my way out of the problem and was forced to do a complete reimage which solved all the problems and put me right back to clean-out-of-the-box state, then I reinstalled TWRP (though an older version before the boot loop bug) and re-flashed my custom ROM. The package I used was the stock image and Odin tool all in one .exe, just plug in to download mode and run it and it flashed bootloader, recovery, system, kernel, etc. all back to stock.
CalcProgrammer1 said:
Just odin back to stock. Get a complete factory stock image from the main sticky thread and flash it with Odin and Download Mode. There's a bug on one of the TWRP versions with 4.3-based ROMs that will put it into a bootloop by breaking device reboots. I was unable to flash my way out of the problem and was forced to do a complete reimage which solved all the problems and put me right back to clean-out-of-the-box state, then I reinstalled TWRP (though an older version before the boot loop bug) and re-flashed my custom ROM. The package I used was the stock image and Odin tool all in one .exe, just plug in to download mode and run it and it flashed bootloader, recovery, system, kernel, etc. all back to stock.
Click to expand...
Click to collapse
Thanks thats what i did, I just basically had to use KIES to use the emergency recovery, then root my phone again. My question is what version of TWRP causes this? cause i used the newest version i could find off GOO. My other concerne is, will it accept or be safe to use a custom ROM? Well i gues ill find out :laugh: THANKS AGAIN!
Everyone with the sgh-i717 is having problems with the latest TWRP and the most stable version is 2.5.0.0. Go with that one or you'll be starting all over again I imagine. And don't just stop at the download link in the OP's, read the thread and find out what's going on. The problems with TWRP have been going on for a while and the development threads have a lot of comments about the latest build causing problems. Good luck! :good: