Bricked Galaxy Nexus? - Samsung Galaxy Nexus

So my friend went to flash that lovely new JB ROM on his Verizon GNex; everything went fine through CWM like a normal ROM flash, and upon restarting the device to boot in to Android it just stuck at the Google logo. He left it for 10 minutes and nothing changed, so he did the following:
Pulled battery
Booted back in to CWM
Erased data/cache/etc.
Tried reflashing, same issue
Repeat with erasing data/etc.
Tried to restore Nandroid backup, greeted with corrupted error when it gets to restoring Data
Tried 3 other known good Nandroid backups, all fail at the same point
Tried just flashing known working ROMs like AOKP, same boot loop error after Google logo upon restart
Is he screwed? Does he just have to ODIN? If so how can he get stuff off the internal memory, as he has lots of pictures, music, etc. on there? Thanks!

Flashed a GSM Jellybean image to a verizon nexus?
...

IINexusII said:
Flashed a GSM Jellybean image to a verizon nexus?
...
Click to expand...
Click to collapse
No it's this one for the CDMA one:
http://forum.xda-developers.com/showthread.php?t=1738018
I flashed that ROM to my GNex and it is working like a charm.

No ideas, huh?

ive tried 3 times to get JB working on my verizon gnex as well
first time, got stuck on the new booting animation (the google X)
second time, was stuck on the google boot screen (same as your friend)
thrid time, im stuck on the google boot animation (the X) again
let me know if you find a solution please!

bkang4 said:
ive tried 3 times to get JB working on my verizon gnex as well
first time, got stuck on the new booting animation (the google X)
second time, was stuck on the google boot screen (same as your friend)
thrid time, im stuck on the google boot animation (the X) again
let me know if you find a solution please!
Click to expand...
Click to collapse
How long did you let yours sit on the X boot animation? Mine sat for probably about 10 minutes the first time and then finally booted into the OS.

I waited almost 20 minutes the first time
and right now i'm sitting at about 10 minutes =(
I don't understand whats going on, its not restarting the boot sequence (not going back to the google boot screen) but just keeps playing the boot animation

Flash the stock google image for verizon version:
https://developers.google.com/android/nexus/images
directions available in other threads.

yeah I did that then tried to get JB working again, but no luck
I'll prly just try again another time =/
thanks though

The exact same thing happened to me. I used Wugfresh tool kit to go back to stock. I lost everything on my SD card. I guess that's the price you pay for being a crack flasher !

bkang4 said:
yeah I did that then tried to get JB working again, but no luck
I'll prly just try again another time =/
thanks though
Click to expand...
Click to collapse
Are you able to access the bootloader? If so it's not bricked.
You need to flash EVERY SINGLE THING, all the partitions, bootloader, recovery, etc, everything, turn it back completely to stock. (then wipe before booting back up)

yeah i can get to the boot loader.
when i flashed to stock i used the factory image of 4.0.2 with the toolkit
everything works on 4.0.2, but i'm hell bent on getting JB to work on this phone haha

bkang4 said:
yeah i can get to the boot loader.
when i flashed to stock i used the factory image of 4.0.2 with the toolkit
everything works on 4.0.2, but i'm hell bent on getting JB to work on this phone haha
Click to expand...
Click to collapse
I guess that's the best way then. So there's no good way to get the stuff off the SD before ODIN/flashing it back to stock?

Fix
I had this same problem a bit ago. My device wouldn't boot and would sit on the Google logo.
Go back into Clockwork Recovery,
Wipe data,
Wipe cache,
Wipe dalvik
Install Jellybean
This worked for me, the problem was that I wasn't wiping everything correctly before installing Jellybean.

bkang4 said:
everything works on 4.0.2, but i'm hell bent on getting JB to work on this phone haha
Click to expand...
Click to collapse
1. Ok good.
2. Wait for a version made for the VWZ Galaxy Nexus or go buy the GSM Galaxy Nexus.

electroholic you're right, its worked! thanks a bunch

nxt said:
1. Ok good.
2. Wait for a version made for the VWZ Galaxy Nexus or go buy the GSM Galaxy Nexus.
Click to expand...
Click to collapse
Just in case you missed it, this is a version made for it, it's on my VZW GNex just fine as well as many others. There's just a few weird scragglers here and there it seems.

HELP!!
i tried to put the jellybean update on my verizon galaxy nexus and then found out it was only for gsm. now my phone has no signal at all. what do i do, i already tried to reset and restore, then i reset it and it just can't find any signal!

Well this happened to mine as well, but the funny thing is that if you just let it sit there for 5+ minutes the phone eventually boots.

ODIN
dude you might have to use odin unfortunately.:crying:

Related

[Q] Had my GN died?

I was updating some apps in the market, as suddenly the phone reboots without any warnings.
OK, **** happens i thought and let it boot. But now the phone starts the ROMs boot animation for about 4-5 seconds and then reboots over and over again.
I pulled the battery and started into recovery. I made a nandroid and wiped cache and dalvik. Reboot with same behavior.
Recovery again: wiped everything and flashed a new AOKP M3 - result: reboot and loop again
Back to recovery: tried to flash the before made nandroid - MD5 checksum error
Flashed an older nandroid and got boot loops again.
So, i think this piece is for the service now...
What is the best way to reset this GN? Using ToolKit to put back stock recovery and lock the bootloader? Or should i try something else?
Update:
Flashed Stock Google Image via ToolKit 5.4 and after that the phone is booting normal?!?
I reflashed the touch recovery and pushed the AOKP build 27 back to the phone and flashed it.
So far so good - I have to start from the bottom now, because flashing the stock rom wiped the whole phone and EVERYTHING on sdcard is gone
Do you think there is a hardware failure? Perhaps some sort of memory malfunktion or something like that?
Same thing just happened to me, thi is the second time
lighthammerhh said:
I was updating some apps in the market, as suddenly the phone reboots without any warnings.
OK, **** happens i thought and let it boot. But now the phone starts the ROMs boot animation for about 4-5 seconds and then reboots over and over again.
I pulled the battery and started into recovery. I made a nandroid and wiped cache and dalvik. Reboot with same behavior.
Recovery again: wiped everything and flashed a new AOKP M3 - result: reboot and loop again
Back to recovery: tried to flash the before made nandroid - MD5 checksum error
Flashed an older nandroid and got boot loops again.
So, i think this piece is for the service now...
What is the best way to reset this GN? Using ToolKit to put back stock recovery and lock the bootloader? Or should i try something else?
Update:
Flashed Stock Google Image via ToolKit 5.4 and after that the phone is booting normal?!?
I reflashed the touch recovery and pushed the AOKP build 27 back to the phone and flashed it.
So far so good - I have to start from the bottom now, because flashing the stock rom wiped the whole phone and EVERYTHING on sdcard is gone
Do you think there is a hardware failure? Perhaps some sort of memory malfunktion or something like that?
Click to expand...
Click to collapse
Firstly when you get bootloops or any other problem do NOT do a nandroid as it backs up EVERYTHING, including the problem.
When you "wiped everything" did you go to mounts and storage and format system, cache and data?
If not then you didn't do a proper full wipe.
This is my own experience, but I want to warn you guys. I had a similar problem with my GNex. The first time it happened, my phone rebooted itself every 5 seconds. I completely restored it using factory image and it ran fine for 3 weeks, then one day, the phone just rebooted itself and got stuck at the boot image. I had to factory reset it again to make it work.
After the second time, I called Samsung and sent it in for repair last week. They are shipping me a replacement unit. It seems the problem was hardware related.
econometrician said:
This is my own experience, but I want to warn you guys. I had a similar problem with my GNex. The first time it happened, my phone rebooted itself every 5 seconds. I completely restored it using factory image and it ran fine for 3 weeks, then one day, the phone just rebooted itself and got stuck at the boot image. I had to factory reset it again to make it work.
After the second time, I called Samsung and sent it in for repair last week. They are shipping me a replacement unit. It seems the problem was hardware related.
Click to expand...
Click to collapse
For 3 weeks... exactly 3 weeks, 21 days?
I can tell you that my first boot loop brick was 20 days after I bought the phone. The second was later that day. But the third one was... again, 20 days after the last successful restore. Is there something magical about the 3-week mark???
I am currently taking nightly nandroid backups, so when I had my third boot loop brick my backup was just under a day old. If this is ultimately a hardware problem that can be warrantied, I guess I'll have to try that next time. I would have to make sure I return it with the bootloader locked, stock recovery, but without the wipe because it has to still be boot looping to prove there's an issue!
Anyway, things I will point out:
- It's the complete wipe in bootloader that blanks the internal storage.
- If you have CWM installed, you can back up the internal storage over USB via adb pull /sdcard/ ./sdcard/ (correct me if I got the syntax wrong)
- When the boot loop brick has happened, CWM is not capable of properly reformatting or restoring to the data partition. I have not found a way to repair it without blanking /sdcard (which on the GN is actually in /data/media), so if you don't want to lose those files the only way to keep them is to pipe them out, blank the phone, and then pipe them back in afterwards.
- After a complete wipe in bootloader (either by flashing userdata.img or by relocking/unlocking bootloader), you must boot the phone once into the OS in order to complete the reformatting of /data. If you try booting straight into recovery after a wipe in the bootloader, CWM cannot read or write from that partition.
Can't say for sure whether it's exactly 21 days but it's definitely around 3 weeks. Why don't u give Samsung a call? The phone is not supposed to behave this way. Plenty of people don't have this problem. My wild guess is that the internal flash memory is faulty.
econometrician said:
Can't say for sure whether it's exactly 21 days but it's definitely around 3 weeks. Why don't u give Samsung a call? The phone is not supposed to behave this way. Plenty of people don't have this problem. My wild guess is that the internal flash memory is faulty.
Click to expand...
Click to collapse
I'll warranty it through my carrier next time as they do exchanges on site. The trouble is, once I've recovered the phone, there's no evidence of the problem anymore. The best way to prove it is to show it fritzing out.
Sent from my Galaxy Nexus using Tapatalk
I think this is a known problem. You shouldn't have to prove it to them. They should be aware of it.
It bricked again today so I warrantied it in-store at my carrier. They gave me a brand new one after being unable to find a solution when fiddling with it. As a bonus, all the little hairline scratches on my screen are gone too
The store guy said he's never seen this issue, and it's one of only two warranty locations for my carrier in the Vancouver area. So I can only hope this was a rare hardware problem and not something that pervades every GN they're going to sell.
I can tell this one is from a different batch because it came preloaded with 4.0.2.
Good for you. hopefully my new phone will behave

[Q] Stuck on boot logo, no matter what??

Ok, so I flashed a MIUI port for the AT&T Note 2, and it was disgusting...it crashed everything, and needless to say I ended up stuck at the boot logo for a long time. FINALLY managed to get it to flash via Odin...so I flashed Stock Rom...and now it's stuck on Samsung logo...Ok..so I go flash CWM...do a wipe and everything, and install CM10.1 via that...stuck at CM logo. I've left each ROM plugged in, stuck on boot screen for over 20-30 minutes each. I'm at a loss of what to do. Could I need to flash a kernel? or am I missing something obvious? The good news, I guess, is with a few steps, I can get into DL mode and use Odin, and I can flash CWM and get into that..but I can't inject anything into my phone so CWM can use it, I only have what's there now, which is CM10.1. I'm so mad...I've never had too many issues with ROMs but this one jacked things up badly...guess that's what I get for using a port even though it noted that everything was working now. Anyway...does anyone have any advice?
Edit: I flashed CWM, and tried to clear cache/dalvik then factory reset...the first two worked...as soon as I hit factory reset, that's where the screen goes black and it resets...it's like it just refuses to do it. I'm seriously at a loss here. Is it toast?
Edit again: sorry but I'm trying more to give more info. I went into CWM and went to advanced and started formatting one by one...it's when you hit format /data that it immediately dies and restarts. So..something weird is going on there. Can I use a PIT file for this phone, if it exists, to reformat and just get it going? I'm desperate...
Us this http://forum.xda-developers.com/showthread.php?t=2052779 on a PC.
Follow directions and Odin back to stock.
Sent from my SAMSUNG-SGH-I317 using xda premium

[Q] Stuck in boot loop, trying to return to stock, I think I need to use PIT file

Hi all. I'm in a real pickle here and hoping someone can tell me how to get out of this mess. It's a bit of a long story, but I'll summarise as best I can.
I've had my Galaxy Note 2 LTE (N7105) for a year and I rooted it pretty much the day after I got it. I'm not new to rooting at all (fourth Android device since 2010, all rooted), but I still feel like a noob at times. Over this 2014 Easter period I had time off so I decided to change ROMs.
I was previously using CM 11, which I had been using pretty much since I rooted. And I had updated CM at least once a month, sometimes more frequently. So I was looking for some new ROMs, downloaded about 5 and tried them out. The last two I tried was OmniROM (a 4.4.2 ROM) and CM 11 Remix (also a 4.4.2 ROM). I was using TWRP 2.7.0.2 to do the wipes, caches, flashes, etc. I had no issues flashing OmniROM, but when I flashed CM 11 Remix, I couldn't get in the first time. I was stuck in a boot loop. I pulled the battery, got back into recovery and tried flashing again. Still boot looping. I think the mistake I made was a Data Format. Either way, I finally got CM 11 Remix to load by first wiping, flashing the ROM, GApps, a sensor fix, a camera fix, Devil Kernel and then Super SU. However once in the ROM I was getting constant Google Play Store / Services FCs. Oh, and yes, I went through the typical brand new Android setups, entering my Google account and so on... I found that if I cleared data / caches on both Google Play Store app and Google Play Services app, it gave me temporary joy but as soon as I tried to download any app in Google Play I'd get the FC. Also, my signal was totally gone. I tried flashing back to OmniROM as it was my last known good and working ROM, but now that was boot looping. I even tried some of the other ROMs from that bunch I had, including AOKP. All would boot loop.
So after much trying different GApp packages, I decided to best thing to do would be restore it to stock, root again, then go for the custom ROM (hopefully CM 11 Remix) from a nice clean slate. So I did this. I downloaded the Android 4.3 stock ROM from SamMobile here. Installed Odin 3.07, then loaded it up and flashed the stock ROM. All seemed to go great, but when the ROM was done and phone rebooted, I get stuck in another boot loop! This time at the white "Samsung" logo with the glowing blue edges. Not the model number screen. Also my LED light is on blue, if that means anything.
So I found this thread (post at top of page) which suggests I need to flash the PIT file during the stock ROM installation with Odin. So I found the PIT file here, and I'm ready to flash this along with the stock ROM... HOWEVER, I read something somewhere (can't find it now) that implied if I'm on Android 4.3, flashing a PIT is a bad move. Can anyone comment on that? I guessing since the stock ROM is 4.3, I'm technically on 4.3 (even though I can't get into it).
Or if anything else I'm doing immediately stands out as a seriously stupid move, please let me know. I've been without normal use of my phone for a couple days now and ironically I'm at the point where I'm considering going without a phone for the rest of my life... LOL! AS IF I COULD!
Anyways, any help will be much appreciated!
EDIT: I just realised I should have posted in Troubleshooting, not General Questions... If mods want to move this, please do.
i just suggest that you flash the stock odin without the pit and see if its working out or not. sometimes playing with pit files can screw up your device even more...
btw... next time you play flashing... i'm suggesting you make a backup of your working custom. its will save you lots of time if this kind of problem happen.
edan1979 said:
i just suggest that you flash the stock odin without the pit and see if its working out or not. sometimes playing with pit files can screw up your device even more...
btw... next time you play flashing... i'm suggesting you make a backup of your working custom. its will save you lots of time if this kind of problem happen.
Click to expand...
Click to collapse
I don't have any working ROM. All I have now is a boot loop.
invertedskull said:
I don't have any working ROM. All I have now is a boot loop.
Click to expand...
Click to collapse
I had a problem with my device where I was stuck at boot loader as well, but it was from the rar file of the rom(cm 11) cause I tried downloading it again and it worked.
I suggest you prepare Odin and the stock firmware, wipe factory/cache dalvik, system (advanced), then flash stock firmware, to bring everything back to normal.
Banutu said:
I had a problem with my device where I was stuck at boot loader as well, but it was from the rar file of the rom(cm 11) cause I tried downloading it again and it worked.
I suggest you prepare Odin and the stock firmware, wipe factory/cache dalvik, system (advanced), then flash stock firmware, to bring everything back to normal.
Click to expand...
Click to collapse
Hmmm, I'm not stuck at boot loader, just boot loop. Maybe you meant that?
To clarify, all I can do now is...
1. Boot normally and end up in a boot loop (at "Samsung" white logo with glowing blue edges).
2. Boot into Download mode and from there I can use Odin to flash / install.
3. Boot into stock recovery, which I've never used before (only ever used custom recovery).
I've prepped Odin again, ready to flash the stock firmware, but I've never done a wipe / factory reset with Odin. I don't see any Advanced settings? Did you mean I can do it elsewhere? Cos I see I can do wipes / factory reset from stock recovery.
So should I do that AND then go into Download mode and flash stock firmware with Odin?
invertedskull said:
Hmmm, I'm not stuck at boot loader, just boot loop. Maybe you meant that?
To clarify, all I can do now is...
1. Boot normally and end up in a boot loop (at "Samsung" white logo with glowing blue edges).
2. Boot into Download mode and from there I can use Odin to flash / install.
3. Boot into stock recovery, which I've never used before (only ever used custom recovery).
I've prepped Odin again, ready to flash the stock firmware, but I've never done a wipe / factory reset with Odin. I don't see any Advanced settings? Did you mean I can do it elsewhere? Cos I see I can do wipes / factory reset from stock recovery.
So should I do that AND then go into Download mode and flash stock firmware with Odin?
Click to expand...
Click to collapse
ohhh my bad, I meant boot loop (stuck at samsung logo), mine was stuck there but then after it restarts and goes into recovery mode
do these following steps and you should be fine with your device.
1. Go into recovery mode
2. Wipe factory/reset
3. Wipe cache
4. Wipe dalvik
5. Advance > format/system
Now you have no rom or any OS to load,
1. Power off the device
2. Open Odin on your PC(right click run as administrator)
3. power on your note in Download Mode
4. Connect your device to your PC via USB
5. odin should recognize your device, something blue like " ID" or something there, you should be familiar with that.
6. click PDA, and find the official stock firmware zip you got it from samsung website, and make sure it fits your device(for example if you have your note from italy you should have ITV)
7. Hit Start and it should finish in 5-10 minutes.
Its the cleanest way with Odin, I did some crap on my device and that's how I return it to normal.
Banutu said:
ohhh my bad, I meant boot loop (stuck at samsung logo), mine was stuck there but then after it restarts and goes into recovery mode
do these following steps and you should be fine with your device.
1. Go into recovery mode
2. Wipe factory/reset
3. Wipe cache
4. Wipe dalvik
5. Advance > format/system
Now you have no rom or any OS to load,
1. Power off the device
2. Open Odin on your PC(right click run as administrator)
3. power on your note in Download Mode
4. Connect your device to your PC via USB
5. odin should recognize your device, something blue like " ID" or something there, you should be familiar with that.
6. click PDA, and find the official stock firmware zip you got it from samsung website, and make sure it fits your device(for example if you have your note from italy you should have ITV)
7. Hit Start and it should finish in 5-10 minutes.
Its the cleanest way with Odin, I did some crap on my device and that's how I return it to normal.
Click to expand...
Click to collapse
All good! Cheers man!
I actually went ahead and booted into stock recovery and did the factory reset and partition wipe before I saw your post. And the stock firmware I'd flashed with Odin previously is now booting and I'm finally back in!!! WOOOOOOOOO!!!
Just need to root this bad boy and get back to a nice shiny custom ROM.
Thanks for the advice everyone!
invertedskull said:
All good! Cheers man!
I actually went ahead and booted into stock recovery and did the factory reset and partition wipe before I saw your post. And the stock firmware I'd flashed with Odin previously is now booting and I'm finally back in!!! WOOOOOOOOO!!!
Just need to root this bad boy and get back to a nice shiny custom ROM.
Thanks for the advice everyone!
Click to expand...
Click to collapse
I'm glad to hear that man, peace ^^
Banutu said:
I'm glad to hear that man, peace ^^
Click to expand...
Click to collapse
I have another hurdle... Some built in security is stopping SuperSU from running. It's not Knox, but something like it. I get this error message:
"Unauthorized access to a secured area has been blocked. Tap here for more info."
How can I disable this? I've searched on Google already but so far nothing is helping and I can mostly only find info about Knox...
EDIT: It was goddamn Knox all along... And I just disabled it by means of SuperSU. Finally!
invertedskull said:
I have another hurdle... Some built in security is stopping SuperSU from running. It's not Knox, but something like it. I get this error message:
"Unauthorized access to a secured area has been blocked. Tap here for more info."
How can I disable this? I've searched on Google already but so far nothing is helping and I can mostly only find info about Knox...
EDIT: It was goddamn Knox all along... And I just disabled it by means of SuperSU. Finally!
Click to expand...
Click to collapse
Lolol, see your finding your way on your own ^_^, I was about to give you this link and suggest you to read the comments as well
http://www.w0lfdroid.com/2013/12/Fix-Root-Problem-on-Android-4.3-for-Galaxy-S3-S4-Note2-Note3.html
Unfortunately for me I don't have Note 2 =(, I have an S II Plus, I hope to get Note 2 next month can't wait =S
Banutu said:
Lolol, see your finding your way on your own ^_^, I was about to give you this link and suggest you to read the comments as well
http://www.w0lfdroid.com/2013/12/Fix-Root-Problem-on-Android-4.3-for-Galaxy-S3-S4-Note2-Note3.html
Unfortunately for me I don't have Note 2 =(, I have an S II Plus, I hope to get Note 2 next month can't wait =S
Click to expand...
Click to collapse
Heh, yeah, all is well in my world once again!
The Note 2 is a great device man. I am sure you'll love it. The Note 3 looks great also, but I don't like the ribbed sides (I'm fussy) and last I read there's an eFuze that goes off once rooted or something along those lines. That's sh!t.
invertedskull said:
Heh, yeah, all is well in my world once again!
The Note 2 is a great device man. I am sure you'll love it. The Note 3 looks great also, but I don't like the ribbed sides (I'm fussy) and last I read there's an eFuze that goes off once rooted or something along those lines. That's sh!t.
Click to expand...
Click to collapse
What do you think about the new oneplus one, do you think I should get that instead?
Sent from my GT-I9105P using Tapatalk
Banutu said:
What do you think about the new oneplus one, do you think I should get that instead?
Sent from my GT-I9105P using Tapatalk
Click to expand...
Click to collapse
Hmmm, I haven't seen that one... Feel free to PM me a link.
Help Me!
Banutu said:
I'm glad to hear that man, peace ^^
Click to expand...
Click to collapse
My case is the same case of Invertedskull. I already did all steps as you instructed. I wiped data/cache/system and flash a stock room 4.4.2 of Nordic Rom on SamMobile website.
After flashed, the looping still happens. When I put the charger, the looping stops and goes to the main screen normally. Sometimes, it suddenly restarts but not frequently.
OMG! How to stop it. Pls help me.
My Note 2 is N7105 LTE - Optus (Australia)
mroldman281 said:
My case is the same case of Invertedskull. I already did all steps as you instructed. I wiped data/cache/system and flash a stock room 4.4.2 of Nordic Rom on SamMobile website.
After flashed, the looping still happens. When I put the charger, the looping stops and goes to the main screen normally. Sometimes, it suddenly restarts but not frequently.
OMG! How to stop it. Pls help me.
My Note 2 is N7105 LTE - Optus (Australia)
Click to expand...
Click to collapse
If you have access to anything, and don't get JUST the boot loop, then you DO NOT have the same case I was in. You are probably able to recover from this. Try posting on the Tf Forums. The guys over there are "specialists" in Asus Tf tablets, and as you'll see on this thread (http://www.transformerforums.com/fo...-boot-loop-after-doing-routine-cm-update.html), they gave me a lot of help. Not that I was able to recover, but they were awesome dudes.
mroldman281 said:
My case is the same case of Invertedskull. I already did all steps as you instructed. I wiped data/cache/system and flash a stock room 4.4.2 of Nordic Rom on SamMobile website.
After flashed, the looping still happens. When I put the charger, the looping stops and goes to the main screen normally. Sometimes, it suddenly restarts but not frequently.
OMG! How to stop it. Pls help me.
My Note 2 is N7105 LTE - Optus (Australia)
Click to expand...
Click to collapse
mroldman281, You didn't post again, so I don't know, If You found solution, but since I had same simptoms, and after four days of reinstalling different stock roms, wiping and even messing with PIT via Odin etc..I can say, that in my case the reason for boot loop was faulty battery. The phone worked when it was plugged in and restarted soon after i unplugged USB cable, and just lopped afterwards. Replacement battery put everything back in order. And I am one happy Camper!
Hope this info helps someone else with boot loop problem
same problem stuck in bootloop
hey guys i have the same problem bootloop all the time i tryied stock firmware but nothing happend avec i rooted my note 2 and intalled a costom recovery and a many roms but stuck in bootloop i didn't chage baterry , by the way i wiped cache and reset factory and clear dalvick cache but the same always bootloop
what u suggest i do
ps : i can acces to bootloader or download mode it charge normally
woow get back my note 2 lte alone
hey guys i get back my note 2 i don't know how but it was a succes :victory:
first : i tried so many afficial firmware 4.4.2 and costom roms but didn't change the problem of bootloop
then i remembred what version i was in it was 4.1.1 so i download it from sammobiles thenks to them flash it and boooom the note 2 lte start like a charm
i want to thanks everyone for their help even if they didn't help directly but this past 3 days i read almost all the threads about note 2
well i thinks one of the selutions here is to revert back the the original stock firmware like i did so maybe will fix the bootloop

[Q] Loads of Problems (rooted, unrooted, firemwares, flash, stuck on logo screen)

I'm having one hell of a time with this tablet. This is pushing a month and I'm still not satisfied with my tablet.
Tonight I finally tracked down what I had hoped was a stock firmware for my tablet. Halfway through the download it timed out and when I went to download it again, the same thing happened.
So I tried to take my tablet that isn't "properly rooted" anymore and use Odin 9, instead of Odin 10, and place kitkat on my device rather than be stuck with Lollipop 5.0.2. All of this because The Sims Freeplay app isn't working and I can't find another soul on the face of the earth who can give me an answer to why this is happening.
Now I'm stuck on the samsung logo. I managed to get it back in download mode and that's where I flashed Lollipop 5.0.2 through Odin 10. I figured that would solve my problem. It didn't, but at least I got TWRP back on my device.
I never recovered anything that came with my tablet. I did not think I'd ever go back to unroot nor did I know how to back it up in the first place. So there's nothing in my recovery I can boot from. So what I did was I came back here and I downloaded the recovery for TWRP. I flashed it from my SD card, it told me it was successful... now what? I've rebooted and my device still loads to the samsung logo...and just stays there. The little confetti animation happens behind the logo, but that's it. It doesn't turn off. It doesn't reset itself.
CAN SOMEONE PLEASE TELL ME WHAT I'M DOING WRONG?!
I've already voided the warranty on this device and I regret almost daily that I decided to root in the first place. I say this only because I think rooted devices are top-notch, but I haven't been having very much luck with them. It took me a week to root. When I finally rooted then my favorite app game stopped working. Then I figured I could flash the stock firmware easily (but it seems like every place I go to find kitkat or even stock lollipop I can't find or I do, but files are corrupt or sites are full of ads).
I can't use my device at all now except click around in TWRP which isn't doing me any good.
I just want my tablet back. I spent 500 dollars on this thing and I haven't had time to even enjoy it. It's only two months old.
Please. Again. Someone HELP me. I want to figure this out and I don't want to accept that I bricked my device because I've watched plenty of videos on youtube and people are stuck with a phone that's resetting and all they do is fix it right there in front of my eyes.
Why can't I fix this? What is it that I'm not doing properly?
geekery15 said:
I'm having one hell of a time with this tablet. This is pushing a month and I'm still not satisfied with my tablet.
Tonight I finally tracked down what I had hoped was a stock firmware for my tablet. Halfway through the download it timed out and when I went to download it again, the same thing happened.
So I tried to take my tablet that isn't "properly rooted" anymore and use Odin 9, instead of Odin 10, and place kitkat on my device rather than be stuck with Lollipop 5.0.2. All of this because The Sims Freeplay app isn't working and I can't find another soul on the face of the earth who can give me an answer to why this is happening.
Now I'm stuck on the samsung logo. I managed to get it back in download mode and that's where I flashed Lollipop 5.0.2 through Odin 10. I figured that would solve my problem. It didn't, but at least I got TWRP back on my device.
I never recovered anything that came with my tablet. I did not think I'd ever go back to unroot nor did I know how to back it up in the first place. So there's nothing in my recovery I can boot from. So what I did was I came back here and I downloaded the recovery for TWRP. I flashed it from my SD card, it told me it was successful... now what? I've rebooted and my device still loads to the samsung logo...and just stays there. The little confetti animation happens behind the logo, but that's it. It doesn't turn off. It doesn't reset itself.
CAN SOMEONE PLEASE TELL ME WHAT I'M DOING WRONG?!
I've already voided the warranty on this device and I regret almost daily that I decided to root in the first place. I say this only because I think rooted devices are top-notch, but I haven't been having very much luck with them. It took me a week to root. When I finally rooted then my favorite app game stopped working. Then I figured I could flash the stock firmware easily (but it seems like every place I go to find kitkat or even stock lollipop I can't find or I do, but files are corrupt or sites are full of ads).
I can't use my device at all now except click around in TWRP which isn't doing me any good.
I just want my tablet back. I spent 500 dollars on this thing and I haven't had time to even enjoy it. It's only two months old.
Please. Again. Someone HELP me. I want to figure this out and I don't want to accept that I bricked my device because I've watched plenty of videos on youtube and people are stuck with a phone that's resetting and all they do is fix it right there in front of my eyes.
Why can't I fix this? What is it that I'm not doing properly?
Click to expand...
Click to collapse
I just skimmed through all this reading, so I may have missed a few things. The thing I didn't see if factory resetting. You need to factory reset in twrp. Just go to wipe and factory reset. Now reboot and wait at least 20 minutes as it does take quite a while to boot.
If doesnt do, transfer a custom stock based ROM for your device (any KK ROM should do) to your SD card. Factory reset in twrp and flash ROM. Now reboot and wait.
Typically, flashing with Odin takes 20 minutes to boot up for the first time. Just be sure you factory reset.
Sent from my SM-T800 using Tapatalk
DUHAsianSKILLZ said:
I just skimmed through all this reading, so I may have missed a few things. The thing I didn't see if factory resetting. You need to factory reset in twrp. Just go to wipe and factory reset. Now reboot and wait at least 20 minutes as it does take quite a while to boot.
If doesnt do, transfer a custom stock based ROM for your device (any KK ROM should do) to your SD card. Factory reset in twrp and flash ROM. Now reboot and wait.
Typically, flashing with Odin takes 20 minutes to boot up for the first time. Just be sure you factory reset.
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
Ok. I just factory resetted. Then I went to reboot and clicked "system". Now it restarted and brought me back to the same samsung logo... do I wait 20 minutes on that screen?
geekery15 said:
Ok. I just factory resetted. Then I went to reboot and clicked "system". Now it restarted and brought me back to the same samsung logo... do I wait 20 minutes on that screen?
Click to expand...
Click to collapse
Yep.
Sent from my SM-T800 using Tapatalk
DUHAsianSKILLZ said:
Yep.
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
By any chance does it take longer than 20 minutes?
It's been 28 minutes and I'm still on the Samsung logo.
geekery15 said:
By any chance does it take longer than 20 minutes?
It's been 28 minutes and I'm still on the Samsung logo.
Click to expand...
Click to collapse
Sometimes. Try and wait 10 more minutes.
If it doesn't boot, I think you may have to flash a custom stock based ROM and flash it from your SD card in twrp.
Sent from my SM-T800 using Tapatalk
DUHAsianSKILLZ said:
Sometimes. Try and wait 10 more minutes.
If it doesn't boot, I think you may have to flash a custom stock based ROM and flash it from your SD card in twrp.
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
Custom Stock Based Rom? Does that mean I'll push myself further away from a stock firmware? Also... where do I find one and are there instructions for it? I thought roms were firmwares up until like 4 hours ago and I've been reading of roots for a little over a month now.
I see you've got the same tablet. By any chance are you running 5.0.2 lollipop and do you happen to know having a rooted device is the reason why The Sims Freeplay won't get past it's splash screen or if it's the app itself and it's newest update that made it wiggy?
I'll flash whatever at this point, but my main reasons for continuing to mess with my tablet was because of not being able to play the sims on there. Every other game I play works.
geekery15 said:
Custom Stock Based Rom? Does that mean I'll push myself further away from a stock firmware? Also... where do I find one and are there instructions for it? I thought roms were firmwares up until like 4 hours ago and I've been reading of roots for a little over a month now.
I see you've got the same tablet. By any chance are you running 5.0.2 lollipop and do you happen to know having a rooted device is the reason why The Sims Freeplay won't get past it's splash screen or if it's the app itself and it's newest update that made it wiggy?
I'll flash whatever at this point, but my main reasons for continuing to mess with my tablet was because of not being able to play the sims on there. Every other game I play works.
Click to expand...
Click to collapse
The only thing I can suggest is download this to your SD card and flash it in twrp. http://forum.xda-developers.com/showthread.php?p=56345482
The Sims may not work because its uncomptiple with lollipop.
Simply, hit wipe in twrp, hit advanced wipe, and tick system, dalivk and cache. Then go back and install the Cm11 zip and reboot. Hopefully it gets you booting
Sent from my SM-T800 using Tapatalk
I'd actually flash this as its more like stock just debloated.
http://forum.xda-developers.com/galaxy-tab-s/development/prerooted-stock-touchwiz-rom-t2973107
You need to wipe system, dalvik, cache and data then Install via twrp.
Wait at least 10 to 15 mins after install for initial boot up.
For future reference whenever you go back to kitkat from lollipop you need to wipe the data and cache partition first.
By the way some apps and games do not work on rooted devices for security reasons.
DUHAsianSKILLZ said:
Yep.
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
DUHAsianSKILLZ said:
Sometimes. Try and wait 10 more minutes.
If it doesn't boot, I think you may have to flash a custom stock based ROM and flash it from your SD card in twrp.
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
ashyx said:
I'd actually flash this as its more like stock just debloated.
http://forum.xda-developers.com/galaxy-tab-s/development/prerooted-stock-touchwiz-rom-t2973107
You need to wipe system, dalvik, cache and data then Install via twrp.
Wait at least 10 to 15 mins after install for initial boot up.
For future reference whenever you go back to kitkat from lollipop you need to wipe the data and cache partition first.
By the way some apps and games do not work on rooted devices for security reasons.
Click to expand...
Click to collapse
I understand that. That is why I clicked unroot in supersu and tried the game app, but it still wouldn't work. On my galaxy note 3 I run 5.0 lollipop and my game works fine. My phone isn't rooted and I never decided to root it and then unroot it.
Is an app smart enough to know when a device has been rooted and if are those that hack their actual game on rooted devices uses cloak or xposed or both to by pass their root?
I rather be unrooted for the sake of the game, but how does one find the stock firmware? Or is it not possible at this point?
Sorry for any confusion.
ashyx said:
I'd actually flash this as its more like stock just debloated.
http://forum.xda-developers.com/galaxy-tab-s/development/prerooted-stock-touchwiz-rom-t2973107
You need to wipe system, dalvik, cache and data then Install via twrp.
Wait at least 10 to 15 mins after install for initial boot up.
For future reference whenever you go back to kitkat from lollipop you need to wipe the data and cache partition first.
By the way some apps and games do not work on rooted devices for security reasons.
Click to expand...
Click to collapse
Okay. I installed or flashed ironrom to my tablet from twrp. i followed the directions it told me and I decided to pick the regular rom above the custom one that was close to stock. Then it told me that it was going to reboot; which it did. When it came back it got stuck on the same samsung loading screen so I powered it off, went back into TWRP (because powering off now isn't possible, more like restart) and I went to "Reboot " and then I clicked "power off".
I guess I'll be waiting for 10 to 15 minutes.
I Pray I did this correctly.
geekery15 said:
Okay. I installed or flashed ironrom to my tablet from twrp. i followed the directions it told me and I decided to pick the regular rom above the custom one that was close to stock. Then it told me that it was going to reboot; which it did. When it came back it got stuck on the same samsung loading screen so I powered it off, went back into TWRP (because powering off now isn't possible, more like restart) and I went to "Reboot " and then I clicked "power off".
I guess I'll be waiting for 10 to 15 minutes.
I Pray I did this correctly.
Click to expand...
Click to collapse
Thanks for all the help! I'm finally back to where I want to be and the ss freeplay seems to be working. I can't thank you both enough.
geekery15 said:
Thanks for all the help! I'm finally back to where I want to be and the ss freeplay seems to be working. I can't thank you both enough.
Click to expand...
Click to collapse
Why did you reboot back into twrp? You should have just let it do its thing after it rebooted.
So for any others that may happen upon this thread.
What was your solution?
ashyx said:
Why did you reboot back into twrp? You should have just let it do its thing after it rebooted.
So for any others that may happen upon this thread.
What was your solution?
Click to expand...
Click to collapse
I did because I thought it had to be shut down before I powered it on and waited. I realized afterwards that you probably meant to just let it sit for 10 to 15 minutes.
Are you asking me my solution or other peoples solution?
geekery15 said:
Are you asking me my solution or other peoples solution?
Click to expand...
Click to collapse
Your solution.
cant reboot after failed encryption
I was trying to encrypt my galaxy tab s, which is rooted and has lollipop 5.0. Afrer reading encryption failed. I tried to reboot in recovery via twrp. My device doesn't reboot, it just acts like its going thru the motions. Only to return to twrp recovery menu. How do I reboot the system clearing the failed encryptions. I am a noob and any suggestions would be much appreciated.
You will have to go into recovery and wipe the data and cache partition then reboot.
It may take a while to boot up after that.
Well I thought my solution was using IronRom... but i'm not too sure now.
I just got back from work and I went to turn on my tablet and it took me to the same loading screen and then after about 5 minutes it tells me that the system can't respond. It asks me to click "ok" or "wait" ... clicking either just turns my tablet off.
Now the screen has dimmed. It's turning on when it wants and sometimes it'll show me the time in the upper right hand corner, but it won't let me do anything because it's a black screen.
What does all of this mean?
I just noticed if I click the "power button" it just flashes my tablet desktop then goes back to black, but it shows me the battery percentage and the time in the upper right hand corner...
smt 800 stuck in logo
SAMSUNG GALAXY TAB S 10.5 WIFI WHAT IT CAN AND CANT DO
i HAD ROOTED AND INSTALLED LOLLIPOP 5.0 WITH SUPER SU AND TWRP RECOVERY.
I THEN TRIED TO ENCRYPT WHICH FAILED.
MY DEVICE SAID TO REBOOT SYSTEM AND THEN TRY TO ENCRYPT AGAIN. AFTER REBOOTING, MY DEVICE IS STUCK WITH (logo screen)THE SAMSUNG TAB S NAME AT THE TOP OF THE SCREEN AND ANDROID ON THE BOTTOM. I then rerooted with cf auto root thru odin. Odin and my tablet went thru the motions. When everything was complete and device should have initialize, but didn't. This part of the process didn't happen.
I am able to go into DOWNLOAD MODE and can get to manual mode, but I seem to have lost recovery. Here is the info.
android system recovery <3e>
kot49h_t800xxu1af8..
the binary reads: samsung official
system status: custom
Do you have any suggestions.

att g3 stuck in factory restore stage 2 (not sure if this goes here sorry)

I tried restoring back to factory after being stuck in a boot loop, thinking my root was the issue or something idk. I used flash tool to try and flash back to stock and fac reset and it gets to the end where MiniOS tries to do its thing but i get no promts and it just says factory reset status 2. its driving me insane trying to get this thing flashed back to stock. i dunno if im missing anything or something but im foloowing the steps like to the letter and it keeps bricking. any help or advice here that could help me out? and sorry if this doesnt go here and stuff. im new to the forums and all that.
Hi,
I had the same problem yesterday. Even worse after that factory reset status 2 my phone couldn't be detected anymore by flashtool 1.8. So I tried the kdz method. This worked for me and from stock I was able to use one click root and flash twrp with flashify. Then I went straight to android 8.1 with magisk root. Don't forget to flash mr bump after root without any reboot in between.
f4lkon said:
Hi,
I had the same problem yesterday. Even worse after that factory reset status 2 my phone couldn't be detected anymore by flashtool 1.8. So I tried the kdz method. This worked for me and from stock I was able to use one click root and flash twrp with flashify. Then I went straight to android 8.1 with magisk root. Don't forget to flash mr bump after root without any reboot in between.
Click to expand...
Click to collapse
yeah i ended up getting it out of status 2 and tried to run stock for a bit but ended up having issues where it would just randomly shut itself off. and then boot loops. switched out like 3 different batteries, (1 that came with the phone, a not so great quality 6000mAh, and a new stock lg battery) and still having boot loop issues. so im thinking that the phone is just dead. so with tax season coming up soon i may just wait and get that new sexy razer phone. i need something new anyway and better than this walmart zte placeholder im using. lol

Categories

Resources