I received a Galaxy Note 1 I717 (AT&T) and it was in a bootloop. I have experience with flashing stock roms through Odin and fixing bootloops that way. So after going through recovery mode, wiping, flashing, I am still getting put into a bootloop after a successful flash on Odin. I've spent 2 days with this and tried all the little suggestions of wiping before flashing, using the original roms from XDA , trying some other stock roms specifically for my model and I'm still left with a bootloop. I'm capable of getting into download and recovery, and I've actually gotten different stock recovery modes! So the flashes are working, but it just won't boot up correctly. I looked around for the U.S. version of the Pit CSC Phone and PDA to try and re partition it, but they are absolutely NOWHERE! Any help would be greatly appreciated, whether it's a ROM suggestion, the re partition files, or whatever else.
Charles Sparkley said:
I received a Galaxy Note 1 I717 (AT&T) and it was in a bootloop. I have experience with flashing stock roms through Odin and fixing bootloops that way. So after going through recovery mode, wiping, flashing, I am still getting put into a bootloop after a successful flash on Odin. I've spent 2 days with this and tried all the little suggestions of wiping before flashing, using the original roms from XDA , trying some other stock roms specifically for my model and I'm still left with a bootloop. I'm capable of getting into download and recovery, and I've actually gotten different stock recovery modes! So the flashes are working, but it just won't boot up correctly. I looked around for the U.S. version of the Pit CSC Phone and PDA to try and re partition it, but they are absolutely NOWHERE! Any help would be greatly appreciated, whether it's a ROM suggestion, the re partition files, or whatever else.
Click to expand...
Click to collapse
A bad kernel can be the cause of this problem. Try and search for a custom kernel for your device and flash it.
I hope this will solve your problem.
Ibrahim9999 said:
A bad kernel can be the cause of this problem. Try and search for a custom kernel for your device and flash it.
I hope this will solve your problem.
Click to expand...
Click to collapse
I already tried flashing the stock Rom then flashed the kernel and got boot loops still from this XDA page http://forum.xda-developers.com/showthread.php?t=1506330 . Having a lot of trouble with this one.
Charles Sparkley said:
I already tried flashing the stock Rom then flashed the kernel and got boot loops still from this XDA page http://forum.xda-developers.com/showthread.php?t=1506330 . Having a lot of trouble with this one.
Click to expand...
Click to collapse
OK, download these files and put them on your device:
Rom: http://goo.gl/81TamM
Gapps (important!): http://goo.gl/ws5KZF
Then follow these steps exactly:
1. Boot to recovery (CWM or whatever you use)
2. Wipe data/factory reset
3. Wipe Cache
4. Wipe Dalvik cache (advanced-> wipe dalvik cache)
5. Flash rom
7. Flash the gapps
This must work, if it doesn't, please say it, maybe I can help you further.
Ibrahim9999 said:
OK, download these files and put them on your device:
Rom: http://goo.gl/81TamM
Gapps (important!): http://goo.gl/ws5KZF
Then follow these steps exactly:
1. Boot to recovery (CWM or whatever you use)
2. Wipe data/factory reset
3. Wipe Cache
4. Wipe Dalvik cache (advanced-> wipe dalvik cache)
5. Flash rom
7. Flash the gapps
This must work, if it doesn't, please say it, maybe I can help you further.
Click to expand...
Click to collapse
My bad for not properly explaining my situation, the note is stuck in a boot loop. So I can't upload files to it through drag and drop in USB. It's still capable of flashing through Odin and going into recovery with CWM, but there's no way I know of putting files onto a boot looping phone.
Charles Sparkley said:
My bad for not properly explaining my situation, the note is stuck in a boot loop. So I can't upload files to it through drag and drop in USB. It's still capable of flashing through Odin and going into recovery with CWM, but there's no way I know of putting files onto a boot looping phone.
Click to expand...
Click to collapse
Doesn't the Galaxy Note 1 I717 has a MicroSD-Card Slot?
I tought it had one..
Ibrahim9999 said:
Doesn't the Galaxy Note 1 I717 has a MicroSD-Card Slot?
I tought it had one..
Click to expand...
Click to collapse
Oh it does, would I just put those files onto a good sd card via a working phone and THEN put it into the Note?
Charles Sparkley said:
Oh it does, would I just put those files onto a good sd card via a working phone and THEN put it into the Note?
Click to expand...
Click to collapse
Yes of course, or put the files with a computer on the SDCard.
If you've put the files onto the SDCard, insert it to your Note, and follow the steps on my previous post.
Charles Sparkley said:
Oh it does, would I just put those files onto a good sd card via a working phone and THEN put it into the Note?
Click to expand...
Click to collapse
Did it work?
Ibrahim9999 said:
Did it work?
Click to expand...
Click to collapse
Just got an extra SD card my friend is letting me borrow. I'm going home tonight, putting the files on, and going to try to flash it. I'll tell you how it goes!
Charles Sparkley said:
Just got an extra SD card my friend is letting me borrow. I'm going home tonight, putting the files on, and going to try to flash it. I'll tell you how it goes!
Click to expand...
Click to collapse
OK, hope the best for you!
Ibrahim9999 said:
OK, hope the best for you!
Click to expand...
Click to collapse
Alright, so on my good phone I threw the 2 zips on my extra SD card. Then I put that SD card in the note, went into CWM, wiped the necessary areas as you said, and the dead android with a red triangle appeared. It's a long error, but the end says Error in /sdcard/cm-10.1.3-quincyatt.zip
(Status 7)
Installation aborted.
Are you sure you gave me the right ROM to install?
Charles Sparkley said:
Alright, so on my good phone I threw the 2 zips on my extra SD card. Then I put that SD card in the note, went into CWM, wiped the necessary areas as you said, and the dead android with a red triangle appeared. It's a long error, but the end says Error in /sdcard/cm-10.1.3-quincyatt.zip
(Status 7)
Installation aborted.
Are you sure you gave me the right ROM to install?
Click to expand...
Click to collapse
Status 7 means the device is incompatible, but that's impossible since we have the right ROM for your device.
OK just be sure, I'll give you another ROM and you must follow the other steps, but with the different files of course.
ROM: http://downloadandroidrom.com/file/...CARBON-JB-NIGHTLY-20131015-0513-quincyatt.zip
Google Apps: http://downloadandroidrom.com/file/gapps/gapps-jb-20130813-signed.zip
This is an Android 4.3.1 ROM so you're really up to date with this one.
Put these on a SD Card and follow the given steps in my other post.
This one has to work.
Ibrahim9999 said:
Status 7 means the device is incompatible, but that's impossible since we have the right ROM for your device.
OK just be sure, I'll give you another ROM and you must follow the other steps, but with the different files of course.
ROM: http://downloadandroidrom.com/file/...CARBON-JB-NIGHTLY-20131015-0513-quincyatt.zip
Google Apps: http://downloadandroidrom.com/file/gapps/gapps-jb-20130813-signed.zip
This is an Android 4.3.1 ROM so you're really up to date with this one.
Put these on a SD Card and follow the given steps in my other post.
This one has to work.
Click to expand...
Click to collapse
Hate to say it, but installed the new ROM file and got the same exact message. Right now I'm on CWM-based Recovery v5.5.0.4 and I flashed to stock before this, thanks for all of the help so far. Any suggestions?
Charles Sparkley said:
Hate to say it, but installed the new ROM file and got the same exact message. Right now I'm on CWM-based Recovery v5.5.0.4 and I flashed to stock before this, thanks for all of the help so far. Any suggestions?
Click to expand...
Click to collapse
Do you know for sure you're on a Galaxy Note i717 AT&T?
Because 2 roms incompatible is almost impossible.
Ibrahim9999 said:
Do you know for sure you're on a Galaxy Note i717 AT&T?
Because 2 roms incompatible is almost impossible.
Click to expand...
Click to collapse
Sorry for not getting back in a while, thanks for all the effort you've been putting into helping out.
I'm 100% positive, I'm looking at the back below where the battery goes and it says SGH-I717. I thought that model number meant for sure it was AT&T. I live in the states also if that helps.
Charles Sparkley said:
Sorry for not getting back in a while, thanks for all the effort you've been putting into helping out.
I'm 100% positive, I'm looking at the back below where the battery goes and it says SGH-I717. I thought that model number meant for sure it was AT&T. I live in the states also if that helps.
Click to expand...
Click to collapse
But don't you think it's maybe a Chinese replica with a different kernel?
If you got it cheap, that might be the case.
And can you please thank my posts?
Because the few clicks you do, help me a lot
Ibrahim9999 said:
But don't you think it's maybe a Chinese replica with a different kernel?
If you got it cheap, that might be the case.
And can you please thank my posts?
Because the few clicks you do, help me a lot
Click to expand...
Click to collapse
No it was definitely bought in the US, legit from a phone store.
Charles Sparkley said:
No it was definitely bought in the US, legit from a phone store.
Click to expand...
Click to collapse
So, for my understanding, you bought it new from the store and rooted it and then got in a bootloop?
Can you please tell me how you came in the bootloop, did you get it with flashing a ROM or a kernel etc.?
Ibrahim9999 said:
So, for my understanding, you bought it new from the store and rooted it and then got in a bootloop?
Can you please tell me how you came in the bootloop, did you get it with flashing a ROM or a kernel etc.?
Click to expand...
Click to collapse
I bought it from a friend because they had it in a boot loop. Everything on it was completely stock since they were your average user, I'm pretty sure this isn't a hardware issue either if that helps because randomly after flashing CWM one time it actually booted up and I was able to use the phone. But after rebooting, it bootlooped again :\. I haven't been able to replicate this again sadly.
Related
I tried rooting my phone, but when I flashed CWM my Nexus S stopped booting... it freezes on the Google screen in the intro. I can boot into Fastboot, and cwm, but I cant connect the Internal memory to the computer without it booting like it is supposed to. Does anybody know of anything I can do to fix my phone and bring it back to stock??
There are guides for returning to stock stickied in the Nexus S 4G Android Development forum.
Before you do that though, try flashing a different recovery, like the one linked to here or here.
Btw, which guide did you use? You're not the first person to have this problem, and it's really bugging me (though probably not as much as it's bugging you :-o).
Maximilian Mary: I tried to post the link, but since I'm a new member I have to wait 8 posts before I can post a URL.... :/
I will try a different recovery, but how would I flash a rom if I can connect my phone via usb mount?
deadzunehd said:
Maximilian Mary: I tried to post the link, but since I'm a new member I have to wait 8 posts before I can post a URL.... :/
Click to expand...
Click to collapse
What's the title of the thread?
.
I will try a different recovery, but how would I flash a rom if I can connect my phone via usb mount?
Click to expand...
Click to collapse
I'm a little out of my depth here, but I think it's
fastboot flash system system.img.
You don't need to put the rom image on the sdcard. Just put it in the same folder as fastboot.
It was titled "How to Root Nexus S!"
And I will try to flash recovery and try that rom command, thank you )
deadzunehd said:
It was titled "How to Root Nexus S!"
And I will try to flash recovery and try that rom command, thank you )
Click to expand...
Click to collapse
Hmmm. I can't find that exact title. Could you pm me the link?
deadzunehd said:
thank you )
Click to expand...
Click to collapse
There's a button for that.
I got the link. Thanks. I looks like you flashed a boot image that is incompatible with your phone. That guide was for the T-Mobile Nexus S. (Why they're screwing with the boot.img to begin with, I really don't understand.)
Download the attached file, and unzip it to the same folder as fastboot. The md5 sum is d4a9508f9321eb25df3383f00f571e8b. Then
Code:
fastboot flash boot boot.img
You'll probably also want to use one of the recoveries listed above to
Code:
fastboot flash recovery recovery.img
, but leave system alone for now. Flash that only as a last resort.
deadzunehd said:
I tried rooting my phone, but when I flashed CWM my Nexus S stopped booting... it freezes on the Google screen in the intro. I can boot into Fastboot, and cwm, but I cant connect the Internal memory to the computer without it booting like it is supposed to. Does anybody know of anything I can do to fix my phone and bring it back to stock??
Click to expand...
Click to collapse
I had this problem after flashing the wrong ROM onto my phone. I got the phone back to stock using ODIN.
My thread can be found here
http://forum.xda-developers.com/showthread.php?p=14172335#post14172335
hope it helps
Acnescar said:
I had this problem after flashing the wrong ROM onto my phone. I got the phone back to stock using ODIN.
My thread can be found here
http://forum.xda-developers.com/showthread.php?p=14172335#post14172335
hope it helps
Click to expand...
Click to collapse
OMG!! im having the same issue. could you please post the link for ODIN so i can return to stock and take it from there please? I rely on my phone so much and i need it asap thank you.
same problem with me.
but in my case, the phone not only freeze after the google logo before boot. I tried several times to pull the battery and start the phone again, it took several times until the phone can boot normally again.
After that, my nexus s can work as usual. but it only takes 3-4 hour until it freeze/hangs or reboot automatically and show image of green robot lay down with red alert triangle...
sometimes I noticed all application force closed like gmail, gtalk, etc. (its a basic apps instead of 3rd party app)
History :
- root GB 2.37 using superoneclick
- upgrade OTA to ICS 4.04
- problem happens
- root using guide : nexusshacks.com
- unroot using guide : nexusshacks.com
- back to factory setting on GB 2.34
- upgrade OTA to ICS 4.04
- Still got that problem.....
I'm using Nexus S 4G Sprint, pls help me guys...
nexus s won't boot
I had the same problem and read elsewhere that heating the phone with a hairdryer solves the problem.
I must say, indeed it did.
I removed the battery and the SIM card, then heated up the phone (so it really feels warm) put back the battery and sim and simsalebim the phone started again. and is still working since (now already a few day's)
It seems that a component in the phone is heat sensitive, the question in my mind is when will this show again and do I need to consider buying a new phone.
But sofar it works
PS I also tried hard reset factory reset the lot, but in the end only heating up helped.
Good luck, David
I fixed this problem! but I had to wipe all user data by rooting it using nexusrootICS. It finally boots up and the phone works now... that's all I need.
When it comes down to it here's the order to get ext4 and nameless kernel on your GB rom only.
MUST HAVE THE FOLLOWING FILES.
EP1H ON PC http://www.multiupload.com/MU_PRZ9RUD9ZZ
NEW CWM ON PC http://www.multiupload.com/31963EOUA0 *MUST DELETE MD5 EXTENSION
EXT4 FORMAT ALL ON SD http://www.mediafire.com/?6hx7f8g7c8vv6xz
KERNEL CLEANUP SCRIPT ON SD http://www.mediafire.com/?302ofs64v4ibp9l
NAMELESS KERNEL ON PC. http://www.multiupload.com/M7UYRWDE4R *MUST DELETE MD5 EXTENSION
Wipe all
Odin EP1F/H Leak
Odin new CWM (orange) *MUST REINSERT BATTERY BEFORE YOU ODIN THIS
Wipe all again
In CWM Flash ext4 format all
In CWM Mount system, data, etc. NOTE* MUST MOUNT EXTSTORAGE
In CWM Flash your rom one that supports this... (preferably Eclipse touchwiz)
In CWM Flash kernel cleanup script
Odin Nameless Kernel *MUST REINSERT BATTERY BEFORE YOU ODIN THIS
reboot...samsung will flash about 6 to 8 times before it boots
P.S. Forget the quadrant score once you get this you can feel the power your device was meant to have. However I score in the 1500s.
And here I thought I tried every combination of things lol. I will give this a try once my childrens go to bed. How is that eclipse rom btw? Everything stable and working? If you have time will you provide links to all the necessary files. If not I can rewrite the OP for you with all of them in there.
I would greatly appreciate if the OP had links to all the necessary files. I'm dying to get the most out of this amazing device but this site is somewhat difficult to navigate even with the attempts to establish a template for naming threads.
skydeaner said:
And here I thought I tried every combination of things lol. I will give this a try once my childrens go to bed. How is that eclipse rom btw? Everything stable and working? If you have time will you provide links to all the necessary files. If not I can rewrite the OP for you with all of them in there.
Click to expand...
Click to collapse
Will get those links for you rite now....
brandonaspencer said:
Will get those links for you rite now....
Click to expand...
Click to collapse
Just got done doing all the steps now and am waiting for it to boot up.
I can't thank you enough if this works right lol.
And this thread is going to be sooooo useful to EVERYONE once them links are up.
I already had most of the files sitting on my drive where I have been trying every combination to get it working, but you sir have figured it out and I am infinitely thankful.
I'm on the galaxy S screen now, so it looks like everything is going to go well.
EDIT:::
And everything booted fine and the mount command displays my partitions as EXT4! Great job OP.
skydeaner said:
and here i thought i tried every combination of things lol. I will give this a try once my childrens go to bed. How is that eclipse rom btw? Everything stable and working? If you have time will you provide links to all the necessary files. If not i can rewrite the op for you with all of them in there.
Click to expand...
Click to collapse
eclipse is awesome and stable. The only reason it has a bug or 2 (nothing major) is because the gb leak came like that. I am very picky and extremely happy with this setup. Now that im on this i will never return to ee4.:d
skydeaner said:
Just got done doing all the steps now and am waiting for it to boot up.
I can't thank you enough if this works right lol.
And this thread is going to be sooooo useful to EVERYONE once them links are up.
I already had most of the files sitting on my drive where I have been trying every combination to get it working, but you sir have figured it out and I am infinitely thankful.
I'm on the galaxy S screen now, so it looks like everything is going to go well.
Click to expand...
Click to collapse
The Galaxy S is a sign of success enjoy.
marcucci217 said:
I would greatly appreciate if the OP had links to all the necessary files. I'm dying to get the most out of this amazing device but this site is somewhat difficult to navigate even with the attempts to establish a template for naming threads.
Click to expand...
Click to collapse
I understand where you are coming from...I have never been more happier with my device than since I first got it. I wish I knew how to dev. But for now all I can do is assist with what I know to all loyal droid charge soldiers lol
i've found everything but the orange cwm. i only found the blue, and using blue cwn i cant seem to find a mount ext storage option. =\
Do I need to reboot at any time before the very end?
This worked like a charm. I do really appreciate all the files being located in one area. I've been wanting to give this a try, but this was a no brainier! Thank you thank you!
FroyoBaggins said:
i've found everything but the orange cwm. i only found the blue, and using blue cwn i cant seem to find a mount ext storage option. =\
Click to expand...
Click to collapse
http://www.multiupload.com/31963EOUA0
Jstevenett said:
Do I need to reboot at any time before the very end?
Click to expand...
Click to collapse
Do not reboot the device until the end
Sorry this is extremely noob but what is "wipe all"?
marcucci217 said:
Sorry this is extremely noob but what is "wipe all"?
Click to expand...
Click to collapse
In recovery you can see the option to wipe data factory reset, wipe cache and in advanced recovery you will see wipe dalvik. Doing this is what i mean by wipe all.
brandonaspencer said:
In recovery you can see the option to wipe data factory reset, wipe cache and in advanced recovery you will see wipe dalvik. Doing this is what i mean by wipe all.
Click to expand...
Click to collapse
Thanks. That's what I thought but wasn't sure because you had "wipe all" before you have Odin latest Clockwork
These are the exact steps I took last night to get on ext4. Great post.
Sent from my SCH-I510 using Tapatalk
Ok another question:
Why would you want the new recovery (minus the md5 extension) on the SD card when you are using ODIN to push it to the phone? Wouldn't you want it on the phone? In the steps it says on SD.
Sorry I've never flashed kernels only roms so this is new for me.
marcucci217 said:
Ok another question:
Why would you want the new recovery (minus the md5 extension) on the SD card when you are using ODIN to push it to the phone? Wouldn't you want it on the phone? In the steps it says on SD.
Sorry I've never flashed kernels only roms so this is new for me.
Click to expand...
Click to collapse
The new CWM stays on your PC and you Odin it. You have to erase the MD5 extension for it to work. Just follow those steps exactly and you will be fine. The dev that created the CWM created it to be flashed thru Odin.
brandonaspencer said:
The new CWM stays on your PC and you Odin it. You have to erase the MD5 extension for it to work. Just follow those steps exactly and you will be fine.
Click to expand...
Click to collapse
I understand that. I erased the md5 extension and it turned into a zip file. The instructions say on SD in the OP. That's why I was confused. So I shouldn't put it on the SD card, correct
EDIT:
It turned into a tar file when I deleted the extension, not zip
So long story short, my tab was running stock ICS (rooted, with temp CWM/cwm.zip). I decided to try a new rom (paranoid android) so I backed up everything via CWM and I flashed the new rom. But I forgot to do a factory reset before doing so which resulted in a bootloop. I returned to CWM to try to restore the previous ROM, all seemed to be fine and the tab restarted but was also bootlooped. Now I can't even access the stock recovery to acess CWM, I get an error message:
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC code : THL
Successfully applied multi-CSC
E :failed to mount / system (invalid argument) <in red.
Is there anything I can do to return to my stock ROM?!
Do I have the Brick Bug?
rumpypumpy said:
So long story short, my tab was running stock ICS (rooted, with temp CWM). I decided to try a new rom (paranoid android) so I backed up everything via CWM and I flashed the new rom. But I forgot to do a factory reset before doing so which resulted in a bootloop. I returned to CWM to try to restore the previous ROM, all seemed to be fine and the tab restarted but was also bootlooped. Now I can't even access the stock recovery to acess CWM, I get an error message:
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC code : THL
Successfully applied multi-CSC
E :failed to mount / system (invalid argument) <in red.
Is there anything I can do to return to my stock ROM?!
Click to expand...
Click to collapse
Can it get into download mode? If so try flash a stock rom with odin. Im not a sgt user but i am a samsung phone user and usualy when i forget to wipe all i have to do is go back into recovery. Then wipe everything and flash the same rom. NEVER go straight to a backup unless you pass setup. Then it can create a link almost so it supports going back. Or so thats what ive been told by devs on other forums...sounds kinda wierd tho but anyway if you forget to do something while flashing roms then go back indo recovery and do it again
Sent from the phone of Gamers
gmaster1 said:
Can it get into download mode? If so try flash a stock rom with odin. Im not a sgt user but i am a samsung phone user and usualy when i forget to wipe all i have to do is go back into recovery. Then wipe everything and flash the same rom. NEVER go straight to a backup unless you pass setup. Then it can create a link almost so it supports going back. Or so thats what ive been told by devs on other forums...sounds kinda wierd tho but anyway if you forget to do something while flashing roms then go back indo recovery and do it again
Sent from the phone of Gamers
Click to expand...
Click to collapse
It loads the amination for the stock recovery, then I get the error message I posted above. I need to get onto the stock recovery to get into CWM. Im not too sure what to do at the moment...
rumpypumpy said:
It loads the amination for the stock recovery, then I get the error message I posted above. I need to get onto the stock recovery to get into CWM. Im not too sure what to do at the moment...
Click to expand...
Click to collapse
Thats a messege saying the system has broke basicly because you went straight to a backup. Download mode and odin are your only hope
Sent from the phone of Gamers
gmaster1 said:
Thats a messege saying the system has broke basicly because you went straight to a backup. Download mode and odin are your only hope
Sent from the phone of Gamers
Click to expand...
Click to collapse
I forgot about download mode. I'll have a go then I'll report back.
Thanks
Now I'm stuck at the "<ID:0/005> factoryfs.img" stage!
I'm a bit scared of unplugging the tab, what would be the best thing to do now?
EDIT: If I flash a kernel or CWM, would this solve my problem?
Thanks in advance
EDIT:I managed to get CWM working, a step in the right direction
rumpypumpy said:
Now I'm stuck at the "<ID:0/005> factoryfs.img" stage!
I'm a bit scared of unplugging the tab, what would be the best thing to do now?
EDIT: If I flash a kernel or CWM, would this solve my problem?
Thanks in advance
EDIT:I managed to get CWM working, a step in the right direction
Click to expand...
Click to collapse
From CWM wipe data, cache & dalvik & reboot.
And flash this ICS zip file from CWM. if yours is 6800.
http://forum.xda-developers.com/showthread.php?t=1796866
rumpypumpy said:
Now I'm stuck at the "<ID:0/005> factoryfs.img" stage!
I'm a bit scared of unplugging the tab, what would be the best thing to do now?
EDIT: If I flash a kernel or CWM, would this solve my problem?
Thanks in advance
EDIT:I managed to get CWM working, a step in the right direction
Click to expand...
Click to collapse
If cwm works then we both know theres hope
Sent from the phone of Gamers
lsherif said:
From CWM wipe data, cache & dalvik & reboot.
And flash this ICS zip file from CWM. if yours is 6800.
http://forum.xda-developers.com/showthread.php?t=1796866
Click to expand...
Click to collapse
I did everything you said, but the progress bar has been stuck at 75% for over an hour, this has happened with all the ROMs I've tried to install. Is there anything else I could do? I red somewhere that a low battery doesn't allow ROMs to be installed properly.
Although I have no idea of my battery life, I'm just gonna leave it to charge for a bit. I hope everything turns out fine eventually
rumpypumpy said:
I did everything you said, but the progress bar has been stuck at 75% for over an hour, this has happened with all the ROMs I've tried to install. Is there anything else I could do? I red somewhere that a low battery doesn't allow ROMs to be installed properly.
Although I have no idea of my battery life, I'm just gonna leave it to charge for a bit. I hope everything turns out fine eventually
Click to expand...
Click to collapse
Battery life has nothing to do with it. People just say make sure you have high battery incase something happens. I think that it might be a very expensive brick now. Unless anyone else knows then i habe no idea
Sent from the phone of Gamers
gmaster1 said:
Battery life has nothing to do with it. People just say make sure you have high battery incase something happens. I think that it might be a very expensive brick now. Unless anyone else knows then i habe no idea
Sent from the phone of Gamers
Click to expand...
Click to collapse
:crying:
I was reading the following articles:
http://www.xda-developers.com/android/samsung-diligently-working-towards-hardbrick-fix/
http://forum.xda-developers.com/showthread.php?t=1810954
Could this Brick Bug be the source of my problems?
I was running a leaked version of ICS AND I have been using the cwm.zip so there is the possibility
Being unable to flash through either Odin or CWM surely sounds a lot like the brickbug.
If I were you, I'd reboot to download mode, and install a full ROM with repartition + PIT file. If it works, install locerra's CWM (it's one of the few recoveries for our tablet that's confirmed to be brickbug-free), and work as usual. But remember to wipe everything before installing anything through CWM...
If Odin doesn't work, you probably have been hit by the brickbug. However, all is not lost: this guy seems to have found a "fix" for many devices. It involves giving up on all your data and making your onboard storage a couple of GB smaller than it used to be, but it can make your device work again. Read the thread, try to understand it, and (if you can't find another way out) use the PIT file for the GT-6800 provided. If your tab isn't the international WiFi+3G GT-P6800, you may have to ask the guy (hg42) for a PIT tailored to your device.
The other option, in the case of a eMMC-related brick, is to remove all traces of CWM, go to a Samsung store and repair it under warranty, saying "its broke down when I were running that backie upppe thing in kies".
The other option is the better one, as i bricked my note. When i am able to revive it, i am left with 8GB space and it seems real laggy. Change a new motherboard would be better if still cover undr warrantly.
Sent from my GT-P6800 using xda premium
Thanks for the replies guy.
I have decided I will return it as faulty, in the hope it is repaired. I haven't been able to boot into CWM anymore, only the download mode, so I am guessing it is fine to return it as it is?
Thanks
rumpypumpy said:
Thanks for the replies guy.
I have decided I will return it as faulty, in the hope it is repaired. I haven't been able to boot into CWM anymore, only the download mode, so I am guessing it is fine to return it as it is?
Thanks
Click to expand...
Click to collapse
If I were you, I'd return it to something as close to stock as possible.
One suggestion: grab the latest Odin-flashable ROM for your country. You'll get a .tar.md5 file, such as P6800UBLA2_P6800ZTOLA2_ZTO.tar.md5. Try to flash it through Odin, just to see if it works; if it doesn't, write down the name of the .img file that gave you problems. If it works, congratulations, you have your tablet back, and you can stop reading.
Now, Rename that file to .tar (or, remove the .md5 extension), and open it in WinRAR/7zip/whatever. You'll see a lot of .img files inside, including the one that gave you problems. Remove it, and try to flash this new .tar file. If the flash works, proceed to the next paragraph. If it doesn't, write down the name of the .img file that gave you problems, and repeat this paragraph using your new .tar file.
After a flash that works, your device should be as close to stock as possible. Maybe it will even boot, but I wouldn't count on it (try anyway). I'd send it to the repair centre only when it is at this stage.
Steve_max said:
If I were you, I'd return it to something as close to stock as possible.
One suggestion: grab the latest Odin-flashable ROM for your country. You'll get a .tar.md5 file, such as P6800UBLA2_P6800ZTOLA2_ZTO.tar.md5. Try to flash it through Odin, just to see if it works; if it doesn't, write down the name of the .img file that gave you problems. If it works, congratulations, you have your tablet back, and you can stop reading.
Now, Rename that file to .tar (or, remove the .md5 extension), and open it in WinRAR/7zip/whatever. You'll see a lot of .img files inside, including the one that gave you problems. Remove it, and try to flash this new .tar file. If the flash works, proceed to the next paragraph. If it doesn't, write down the name of the .img file that gave you problems, and repeat this paragraph using your new .tar file.
After a flash that works, your device should be as close to stock as possible. Maybe it will even boot, but I wouldn't count on it (try anyway). I'd send it to the repair centre only when it is at this stage.
Click to expand...
Click to collapse
The tab gets stuck at 'factoryfs.img'. I'm a bit cautious since it is the biggest file in the .tar. Isn't the tab 'stock' stock enough as it is?:silly:
rumpypumpy said:
The tab gets stuck at 'factoryfs.img'. I'm a bit cautious since it is the biggest file in the .tar. Isn't the tab 'stock' stock enough as it is?:silly:
Click to expand...
Click to collapse
Thats...a...problem...if it takes longer then 15 mins its bricked...i have been a gt user and devs on other sites told me it was bricked. Maybe there is a solution but...i havnt found one. It should never take too long on one thing in odin.
Sent from the phone of Gamers
rumpypumpy said:
The tab gets stuck at 'factoryfs.img'. I'm a bit cautious since it is the biggest file in the .tar. Isn't the tab 'stock' stock enough as it is?:silly:
Click to expand...
Click to collapse
Even so, flash the other .imgs. You want to be closest to stock, including the recovery (imagine the guys at the Samsung centre manage to enter recovery, just to see CWM: your warranty is now gone). Having all partitions on stock, or at least most of them, can only help your case.
Steve_max said:
Even so, flash the other .imgs. You want to be closest to stock, including the recovery (imagine the guys at the Samsung centre manage to enter recovery, just to see CWM: your warranty is now gone). Having all partitions on stock, or at least most of them, can only help your case.
Click to expand...
Click to collapse
The warrenty is not void unless they find proof of tampering with system files. So basicly yeah...everything that guy said. Get it as close to stock as possible and send.
Sent from the phone of Gamers
Right OK, I definately don't want my warrenty void!
So would it be ok if I flashed 'P6800OXALQ1_P6800XXLQ1_HOME.tar.md5' (minus the factoryfs.img) to my tab?
Thanks
Hey guys, I am sorry if I posted this in the wrong thread but I urgently need help from you guys!
So now I am having a china tablet, it is Ployer MOMO5 (if you guys know) and after using for awhile, it has stop working and I decided to upgrade its firmware.
I used Micro SD and I dowloaded the firmware from Ployer website.
After upgrading, everything went smoothly but it stucks at the 'android' word screen, and it is forever!!!
Anyone here can guide me regarding this?
I need this urgently thanks!
em0kia said:
Hey guys, I am sorry if I posted this in the wrong thread but I urgently need help from you guys!
So now I am having a china tablet, it is Ployer MOMO5 (if you guys know) and after using for awhile, it has stop working and I decided to upgrade its firmware.
I used Micro SD and I dowloaded the firmware from Ployer website.
After upgrading, everything went smoothly but it stucks at the 'android' word screen, and it is forever!!!
Anyone here can guide me regarding this?
I need this urgently thanks!
Click to expand...
Click to collapse
Any idea why it stopped working before you upgraded the firmware?
Not sure, maybe i did not use it for too long already.
Then when I on it initially, it showed all the RAM ROM and numbers (Not sure what it is called)
SunnyChrono6 said:
Any idea why it stopped working before you upgraded the firmware?
Click to expand...
Click to collapse
Then I decided to upgrade it by downloading the latest firmware, insert it into my micro SD and insert it into my china tablet to upgrade.
Everything worked fine.
But now I cant on it.
How did you install the firmware?Using a custom recovery or the pre-installed recovery of the tablet?And do you happen to have a backup of the working OS?
em0kia said:
Hey guys, I am sorry if I posted this in the wrong thread but I urgently need help from you guys!
So now I am having a china tablet, it is Ployer MOMO5 (if you guys know) and after using for awhile, it has stop working and I decided to upgrade its firmware.
I used Micro SD and I dowloaded the firmware from Ployer website.
After upgrading, everything went smoothly but it stucks at the 'android' word screen, and it is forever!!!
Anyone here can guide me regarding this?
I need this urgently thanks!
Click to expand...
Click to collapse
1. reboot to cwm
2. Wipe cache
3. Wipe dalwik
Reboot again. That all
babykristal70 said:
1. reboot to cwm
2. Wipe cache
3. Wipe dalwik
Reboot again. That all
Click to expand...
Click to collapse
How do you know he has CWM?
SunnyChrono6 said:
How did you install the firmware?Using a custom recovery or the pre-installed recovery of the tablet?And do you happen to have a backup of the working OS?
Click to expand...
Click to collapse
Not so sure what you are talking, but are you asking me whether i created the firmware myself, or download it from somewhere?
If yes, then I downloaded the firmware from the main website of it and I put into my micro sd
em0kia said:
Not so sure what you are talking, but are you asking me whether i created the firmware myself, or download it from somewhere?
If yes, then I downloaded the firmware from the main website of it and I put into my micro sd
Click to expand...
Click to collapse
How do you flash your firmware?
babykristal70 said:
How do you flash your firmware?
Click to expand...
Click to collapse
I downloaded the firmware and extracted them into the root directory of my micro sd. Then i hold the power button while inserting the micro sd card into me tablet. Then it update itself.
The tablet showed that the update is complete at the top left corner.
In that case,try flashing it again.
SunnyChrono6 said:
In that case,try flashing it again.
Click to expand...
Click to collapse
No effect.
I tried lots of times already.
em0kia said:
No effect.
I tried lots of times already.
Click to expand...
Click to collapse
Try to reformat again your sd card. After that copy back the firmware and others suporting file to your sd card. Reboot. Hopefully it can be solve.
babykristal70 said:
Try to reformat again your sd card. After that copy back the firmware and others suporting file to your sd card. Reboot. Hopefully it can be solve.
Click to expand...
Click to collapse
You beat me to it lol.Well,I was going to post asking you to use a different SD card,but I guess you could try the above too.
SunnyChrono6 said:
You beat me to it lol.Well,I was going to post asking you to use a different SD card,but I guess you could try the above too.
Click to expand...
Click to collapse
tried. No use.
Any more powerful way to shock my tablet alive?
Flash the non updated version of the ROM, if that's available. There's not much else you can do.
Chinese GALAXY note 2 was stuck on the logo please help
I'm a Chinese Note 2 Page loaded you are stuck rooted android phone font you've installed the software, reset the Why
Windows 8. Backup did. Above Let me go, but I can not hold on to power the factory settings Brhltfa can help me to learn my phone .mediatek
Hey guys, Im new to this but I got a phone. Its a Samsung Infuse 4G for AT&T. It was running cyanogen... it was jellybean 4.2.1 I believe? Anyway, now it is stuck on "CW based Recovery v6 .0.3.2" and Im stumped!!
It also isn't registering on my PC so I cant drag any files to it. It comes up that there is 2 drives, but they are grayed out, like I cant open or click on them. Ive heard of NVflash but cant figure out how to use it, not sure if I can since I cant drag and drop files on my droid.
Please help me...
Bender9406 said:
Hey guys, Im new to this but I got a phone. Its a Samsung Infuse 4G for AT&T. It was running cyanogen... it was jellybean 4.2.1 I believe? Anyway, now it is stuck on "CW based Recovery v6 .0.3.2" and Im stumped!!
It also isn't registering on my PC so I cant drag any files to it. It comes up that there is 2 drives, but they are grayed out, like I cant open or click on them. Ive heard of NVflash but cant figure out how to use it, not sure if I can since I cant drag and drop files on my droid.
Please help me...
Click to expand...
Click to collapse
Here is what it looks like...
Bender9406 said:
Here is what it looks like...
Click to expand...
Click to collapse
Try wiping data & cache if possible and then system reboot..
Hit thanks rather than typing it
parkourkarthik said:
Try wiping data & cache if possible and then system reboot..
Hit thanks rather than typing it
Click to expand...
Click to collapse
I wish it was that easy. No restore option. Reboot just sends me back to same thing. The cache has been cleared so many times.... no luck
Bender9406 said:
Hey guys, Im new to this but I got a phone. Its a Samsung Infuse 4G for AT&T. It was running cyanogen... it was jellybean 4.2.1 I believe? Anyway, now it is stuck on "CW based Recovery v6 .0.3.2" and Im stumped!!
It also isn't registering on my PC so I cant drag any files to it. It comes up that there is 2 drives, but they are grayed out, like I cant open or click on them. Ive heard of NVflash but cant figure out how to use it, not sure if I can since I cant drag and drop files on my droid.
Please help me...
Click to expand...
Click to collapse
I got the same problem.. have you figured out how to fix it?
Same thing here
I've got exactly the same problem with my LG P720 (3D MAX) after installing the ICS ROM (and I'm already looking for a new phone). But I'm willing to donate to whoever can help me with this. :crying::crying::crying:
endeavor2908 said:
I've got exactly the same problem with my LG P720 (3D MAX) after installing the ICS ROM (and I'm already looking for a new phone). But I'm willing to donate to whoever can help me with this. :crying::crying::crying:
Click to expand...
Click to collapse
Reflash the boot loader of you device using Odin if you can. It will solve the problem. Since im on a different device I can't tell where you can find it. Just search for it.
Sent from my GT-I9001 using xda premium
About odin
Sewrizer said:
You can go in cwm recovery->mounts and storage-> mount sd card or usb storage then connect phone to PC. After connecting it, you copy a rom to sd card and gapps if necessary and then perform a full wipe and flash the rom along with gapps.
If the mounts and storage thing doesn't work, put your sd card in an adapter or another phone and connect it to pc and move the rom and gapps there then put the sd card back in your phone, full wipe and flash.
If this doesn't work, do a restock with odin with a rom from sammobile. If you don't know how to do it, send a reply to my post and I will give you some instructions.
Click to expand...
Click to collapse
Ok so, I've download ODIN and I have the ROM in a zip file in the internal memory but ODIN just takes .tar, .md5, smd, gz and tgz and I don't get odin to cominucate with the phone, ID COM never gets blue and Sammobile seems to be for Samsung phones
I would just perform a factory reset, wipe cache and dalvik cache. then try a reboot, if that doesn't work then you can mount the SD Card via mounts and storage> mount usb storage and then try a few different roms and if possible try find a stock recovery that someome else has posted and the correct Gapps. Try reflashing CWM too. Hope that helps