I flashed my phone with the works. Installed CWM, overclock kernel, and the Saurom rom that's in the Dev's section.
I needed to take it back to stock, so I flashed my phone with the Stock boot from here: http://forum.xda-developers.com/showthread.php?t=1504999 and then I flashed with the stock recovery. I went to install the stock ODIN from here: http://forum.xda-developers.com/showthread.php?t=1506330 and it wouldn't take. It just locked.
I decided to try it again, and it locked again. Its hanging up when it is writing to the NAND. I tried flashing the boot again, and its hanging as well. I JUST got the phone, and I am most likely going to take it back and get an AT&T swap. Anyone have any thoughts on what I can try?
I am not new to flashing phones and working with them, but I can't develop them. My Captivate has been to hell and back, and its still kicking strong. I pulled the SIM card and threw it on there, which currently has ICS on it and is overclocked.
I'm just curious if there's anything I can try before I send it back to AT&T? It has the counters triggered (ironically when I attempted to take it back to stock).
Not sure about the note but on my galaxy s2. To get back to stock I just flashed one .tar file not everything you listed.
Did you do full wipe before?
Sent from the only smartphone designed for Chuck Norris
kevinjgray88 said:
Not sure about the note but on my galaxy s2. To get back to stock I just flashed one .tar file not everything you listed.
Did you do full wipe before?
Sent from the only smartphone designed for Chuck Norris
Click to expand...
Click to collapse
Yep, I did a full wipe both before flashing and when recovery worked.
Also I wanted to note, the NAND can't be written on the boot side from what I can see. I can flash and get into CWM, but that's about it.
I am locking up when flashing the single TAR file that's available for the Note. If I can get the boot NAND to write, I am sure I can finally flash with the stock .tar
keilbaca said:
Yep, I did a full wipe both before flashing and when recovery worked.
Also I wanted to note, the NAND can't be written on the boot side from what I can see. I can flash and get into CWM, but that's about it.
I am locking up when flashing the single TAR file that's available for the Note. If I can get the boot NAND to write, I am sure I can finally flash with the stock .tar
Click to expand...
Click to collapse
take out the battery for a couple hours and try again.
Also, what about using ADB?
orangekid said:
take out the battery for a couple hours and try again.
Also, what about using ADB?
Click to expand...
Click to collapse
I will give that a try. If that doesn't work, I'll see if I can take it back to AT&T.
I can use ADB through CWM but I have no idea what the command is to install the boot.img and I cannot seem to be able to access the SD card at the moment. CWM won't mount it.
Pretty sure that bug has not been fixed
No adb access from cwm
keilbaca said:
I will give that a try. If that doesn't work, I'll see if I can take it back to AT&T.
I can use ADB through CWM but I have no idea what the command is to install the boot.img and I cannot seem to be able to access the SD card at the moment. CWM won't mount it.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I717 using XDA App
00mred00 said:
No adb access from cwm
Click to expand...
Click to collapse
I've dd'd several radios over adb while in cwm on my Note.
Related
I have an AT&T Note that I rooted using the Odin method. I was running stock ICS and I know the root worked because I was able to install Google Now and it worked fine.
So I decided I wanted to try a different ROM. I just wanted to install bigfau's cleaned up stock rom found here. I put the zip file on my phone, booted into CWM, did a wipe, found the zip, said it installed fine and then I rebooted. At boot it just sits at the Samsung screen. I let it sit for 30 minutes, still nodda.
So I grab odin and flash back to stock ICS. Use the same method to root and I try a different ROM. This time the Pure Stock ICS from bigfau, same problem.
Odin back to stock, root, and I try parandoidandroid found here - same problem.
Do it all again and try a ROM from another site called HYFR Only One, which is a SGS3 based rom. Same deal.
The only thing I can get it to do is ODIN to stock. Am I missing something?
(I have another rooted galaxy note that I do not have any issues with flashing roms but it was already rooted when I got it.)
berdo said:
I have an AT&T Note that I rooted using the Odin method. I was running stock ICS and I know the root worked because I was able to install Google Now and it worked fine.
So I decided I wanted to try a different ROM. I just wanted to install bigfau's cleaned up stock rom found here. I put the zip file on my phone, booted into CWM, did a wipe, found the zip, said it installed fine and then I rebooted. At boot it just sits at the Samsung screen. I let it sit for 30 minutes, still nodda.
So I grab odin and flash back to stock ICS. Use the same method to root and I try a different ROM. This time the Pure Stock ICS from bigfau, same problem.
Odin back to stock, root, and I try parandoidandroid found here - same problem.
Do it all again and try a ROM from another site called HYFR Only One, which is a SGS3 based rom. Same deal.
The only thing I can get it to do is ODIN to stock. Am I missing something?
(I have another rooted galaxy note that I do not have any issues with flashing roms but it was already rooted when I got it.)
Click to expand...
Click to collapse
Rooted has nothing to do with flashing a ROM, having CWM or TWRP will give you the cap to flash a ROM.
I have used these Recovery types for flashing:
Touch CWM: http://forum.xda-developers.com/showthread.php?t=1584576
TWRP: http://forum.xda-developers.com/showthread.php?t=1647575
After you have CWM of some type ensure you are doing a clean wipe, this is how I perform my wipes:
1. Download to sdcard
2. Reboot to CWM-based Recovery
3. Wipe data/factory reset
4. Wipe Cache partition
5 Go into advanced> Wipe Dalvik Cache
6. Go into> Mounts & Storage
a. Format /data
b. Format /system
c. Format /cache
Install rom & Reboot
After the first boot up let it sit for a few min to build...then do your set ups.
btw there is a Q&A section.
bigjoe2675 said:
Rooted has nothing to do with flashing a ROM, having CWM or TWRP will give you the cap to flash a ROM.
I have used these Recovery types for flashing:
Touch CWM: http://forum.xda-developers.com/showthread.php?t=1584576
TWRP: http://forum.xda-developers.com/showthread.php?t=1647575
After you have CWM of some type ensure you are doing a clean wipe, this is how I perform my wipes:
1. Download to sdcard
2. Reboot to CWM-based Recovery
3. Wipe data/factory reset
4. Wipe Cache partition
5 Go into advanced> Wipe Dalvik Cache
6. Go into> Mounts & Storage
a. Format /data
b. Format /system
c. Format /cache
Install rom & Reboot
After the first boot up let it sit for a few min to build...then do your set ups.
Click to expand...
Click to collapse
I apologize if I did not make this clear but I have Rom Manager installed and CWM was updated to the latest version. I would reboot into CWM, do a factory reset, wipe cache, dalvik caceh, install rom and reboot. It would just sit at the samsung screen. I did not go into mounts and storage and do that but I will now. The process I use on my AT&T note is the same process I used on my Rogers note and I am able to install any ROM i want on my rogers note.
I have flashed roms probably over 100 times since my samsung captivate. I just didn't know if the note had another step involved. Like S-Off on HTC phones for example.
I have been using the standard version of cwm but I am trying the touch version now. Will update.
Same problem. I am uploading a video to youtube now. I will post in a minute or so.
did you check if bootloader is unlocked?
berdo said:
Same problem. I am uploading a video to youtube now. I will post in a minute or so.
Click to expand...
Click to collapse
U have busy box installed?
Sent from my SAMSUNG-SGH-I717 using xda premium
animatechnica said:
did you check if bootloader is unlocked?
Click to expand...
Click to collapse
elry567 said:
U have busy box installed?
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Animatechnica - It is my understanding that the bootloader is not locked on the Galaxy Note. I have not seen anything about unlocking the bootloader in any thread on the i717.
elry567 - do not have busy box installed - never saw anything requiring it to be installed. I will try that as well.
Well this time I got a status 7 error in CWM which can be a lot of different things. I am up to date on CWM, the rom I know works for the galaxy note (I am running it on my other one AND I have seen video of it working on an AT&T branded Note) so I don't know. I did a google search on the error and everything I found does not seem to apply. It is really starting to piss me off. Any help is appreciated.
Here is the video, sorry about my cam skills but you get the gist. I took this video with a i717r that is running the rom I want to install on the phone in the video.
Are you entering recovery with the phone off then using the buttons, or flashing from rom manager?
You should be doing it by the button method.
rangercaptain said:
Are you entering recovery with the phone off then using the buttons, or flashing from rom manager?
You should be doing it by the button method.
Click to expand...
Click to collapse
Done both, doesn't seem to make a difference. I will definitely use the button method from here on out though.
Try using TWRP? It seems CWM doesn't want to work for you, so try using TWRP instead.
Sent from my SAMSUNG-SGH-I717 using xda premium
Zwarx said:
Try using TWRP? It seems CWM doesn't want to work for you, so try using TWRP instead.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
HOLY F&(%*&G $&!t twrp may have worked. I had to go full back to 100% stock with 3e recovery and 0 flash counter. Use a new root method, flash twrp via goo app and so far so good.
Seriously I do not know who you are but I could kiss you. I wonder why CWM wouldn't work? I have used it to load custom roms on just about every other android phone I have had.
OH well, consider this solved.
Zwarx said:
Try using TWRP? It seems CWM doesn't want to work for you, so try using TWRP instead.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
+1
berdo said:
HOLY F&(%*&G $&!t twrp may have worked. I had to go full back to 100% stock with 3e recovery and 0 flash counter. Use a new root method, flash twrp via goo app and so far so good.
Seriously I do not know who you are but I could kiss you. I wonder why CWM wouldn't work? I have used it to load custom roms on just about every other android phone I have had.
OH well, consider this solved.
Click to expand...
Click to collapse
Sir, he is one of many, that is part of this great Community the GNote. As you can see we just provide the tools and point you to the way we went...it is up to you to get it going, and you did by the see of it....slap a thanks to all these that posted in your thread, (not me) due to the fact, I have seen threads go viewed many times that have no one replies to it, but not around here....
glad it worked out..
bigjoe2675 said:
+1
Sir, he is one of many, that is part of this great Community the GNote. As you can see we just provide the tools and point you to the way we went...it is up to you to get it going, and you did by the see of it....slap a thanks to all these that posted in your thread, (not me) due to the fact, I have seen threads go viewed many times that have no one replies to it, but not around here....
glad it worked out..
Click to expand...
Click to collapse
Done.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Ive found out how to fix this, but everywhere I go there are dead links. Damn megaupload. This isnt my phone and I dont know anything about voodoo. Any directions to where I may find usable links?
Flash back too stock and start over
Sent from my SCH-I500 using Tapatalk 2
If it is a fassy try this http://forum.xda-developers.com/showthread.php?p=23171859
Sent from my SCH-I500 using xda premium
mezster said:
If it is a fassy try this http://forum.xda-developers.com/showthread.php?p=23171859
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
That helps but Im always getting hung up on the movinand.bin when using odin.
slipmagt said:
That helps but Im always getting hung up on the movinand.bin when using odin.
Click to expand...
Click to collapse
I knew I had seen something about that before...
my search turned up this....
Basically make sure your doing the GB Bootloaders and recovery at the right time and proper way
Quote:
Originally Posted by ssewk2x View Post
The CI500_blahblahblah.tar file that you mention does, in fact, flash a bootloader to your phone: the old Froyo one.
The upshot is that every time you use this file to go back to stock, you should odin the GB bootloader again at some point during your process. I generally like to do this:
1. odin CI500blahblahblah.tar. reboot and let it come up.
2. power off and go back into odin. now do the gb bootloader. use PDA, check "update bootloader." reboot and let it come up.
3. power off and go back into odin. now do the old cwm for CM7 recovery. 3-finger reboot directly to that recovery (don't let stock rom boot or it will blow away that recovery you just flashed).
4. flash whatever ROM you are going to from that recovery.
5. Profit.
i actually do all my odin stuff without any reboots and never boot into stock. i flash all odin packages and then go straight to 3 finger recovery.
ThanksThanks
----------------------------------
Quote:
Originally Posted by Sheradrax View Post
i actually do all my odin stuff without any reboots and never boot into stock. i flash all odin packages and then go straight to 3 finger recovery.
It used to be important to let it boot through the stock recovery if you were re-partitioning the device, because the ext4 partitions were then built on top of the stock ones. ODIN couldn't create the MoviNAND partitions if they were corrupted, but the stock recovery could.
The new LVM formatter might be able to handle it, I'm not sure.
-------------------------------------------
.
I did a backup in TWRP before flashing the PA alpha ROM, realized I needed CWM, so flashed that over in TWRP. Fine. Installed PAalpha in CWM. Fine. Decided to go back to the ROM I'd backed up (Beans), so attempted to flash TWRP over in CWM. Rebooted recovery. Sent me straight to stock recovery. Still boots into PAalpha fine.
I've tried to install TWRP via goo manager, and it says it's successful, but I'm still on stock recovery. Did I f- something up? How can I get back to custom? Did I screw my unlock somehow (doesn't seem like it would...)?
I've been doing the flashing thing since the Eris, but have been out of the game for a cycle, and am wary of messing around with things now that I'm at a point I don't quite understand. Much thanks.
Unlocked and rooted.
vxkid said:
I did a backup in TWRP before flashing the PA alpha ROM, realized I needed CWM, so flashed that over in TWRP. Fine. Installed PAalpha in CWM. Fine. Decided to go back to the ROM I'd backed up (Beans), so attempted to flash TWRP over in CWM. Rebooted recovery. Sent me straight to stock recovery. Still boots into PAalpha fine.
I've tried to install TWRP via goo manager, and it says it's successful, but I'm still on stock recovery. Did I f- something up? How can I get back to custom? Did I screw my unlock somehow (doesn't seem like it would...)?
I've been doing the flashing thing since the Eris, but have been out of the game for a cycle, and am wary of messing around with things now that I'm at a point I don't quite understand. Much thanks.
Unlocked and rooted.
Click to expand...
Click to collapse
If you used the website in the twrp thread it does not work. I did the same thing. I had to odin the suck it verizon zip again. After that all was good. Hope this helps.
Sent from my SCH-I605
Android_Fr3ak said:
If you used the website in the twrp thread it does not work. I did the same thing. I had to odin the suck it verizon zip again. After that all was good. Hope this helps.
Sent from my SCH-I605
Click to expand...
Click to collapse
EDIT: I held my breath and flashed it over. Everything's great now. Thanks.
That's exactly what I used. Thanks so much. To be clear, flashing suck it verizon through odin is all i need to do (no need to mess with the other unlock steps?)
Best
vxkid said:
That's exactly what I used. Thanks so much. To be clear, flashing suck it verizon through odin is all i need to do (no need to mess with the other unlock steps?)
Best
Click to expand...
Click to collapse
yes...you should never need to relock bootloader.
I have a p4wifi that is stuck in a boot loop. I think the term is 'soft bricked'.
Basically, last night I turned my tab on for the first time in ages, and it all worked fine. I had rooted and flashed custom roms before (I'd been running a nightly of CyanogenMod for a long time, and it worked well), and I considered myself an expert. I updated loads of apps and stuff, and then realised I wanted a new font. I went into ROM manager and found the font I wanted, Ubuntu. It told me there was an update to ClockworkMod recovery so I wen ahead and updated it, checking the thing for Touch (I'd already bought it). That want ahead and it updated, throwing me back into the OS. I then went to get Ubuntu (I downloaded it within ROM manager), and didn't deem it necessary to create a backup, nor wipe anything. It processed it but returned an error, I though ok but never mind and I told it to reboot. Again that worked fine. I realised I was on a very old verson of CyanogenMod (probably ICS, it was around 201304). As I always do, I grabbed the latest version (again, in ROM manager), and elected to install it. I didn't wipe the delvik cache or whatever, and hit 'Reboot into recovery'. That was where the problem occurred. It wouldn't go any further than the 'Samsung Galaxy Tab 10.1' boot screen (see attachment) into recovery. A similar thing happened before, but it just eventually went away after an hour or so. This has been running for a day, and there has been no progress. I've tried various key combos, like the normal way to get into recovery, but they won't work.
If I need I could find the instructions I followed, but it would be hard.
Is it completely broken? Can a save my data? Will I have to factory reset it? Will I keep my root/ClockworkMod? Will I keep my rom?
Thanks in advance to the person who can answer this
Do you have any ROM zips in your SD card? If you do, boot into recovery, full wipe and flash it. Piece of advice, don't use the recovery in ROM manager. Download pershoot's version of cwm instead in here. www.droidbasement.com
Sent from my GT-P7500 using Tapatalk HD
I have a few nandroid backups, if that counts? I do have a few ROM zips on my SD card too, though. Will a full wipe delete photos etc? I'm guessing it'll get rid of the apps, but that's no problem. But how would I get into recovery? I've already tried to get in with no success.
FelixJ20000 said:
I have a few nandroid backups, if that counts? I do have a few ROM zips on my SD card too, though. Will a full wipe delete photos etc? I'm guessing it'll get rid of the apps, but that's no problem. But how would I get into recovery? I've already tried to get in with no success.
Click to expand...
Click to collapse
If you can find a way to get into recovery, then yes you can use your nandroid. You problem now is you can't get into recovery or download mode, right? Well can you try using adb? If you can then type adb reboot recovery in command prompt to reboot to recovery.
Oh yeah, full wipe won't delete photos etc unless you wipe your internal storage/SD card.
Sent from my GT-P7500 using Tapatalk HD
Oh, thanks. I've got ADB already installed (I used it in trying to root my HTC Hero). Have I said thanks? You're a life saver
Oh dear, it seems that it's not showing up as an ADB device. Are there any other ways to get into recovery?
FelixJ20000 said:
Oh dear, it seems that it's not showing up as an ADB device. Are there any other ways to get into recovery?
Click to expand...
Click to collapse
I don't know. The hold down power button + volume down didn't work? You have to hold for at least 10 seconds.
Don't just say thanks...hit my thanks button.
Sent from my GT-P7500 using Tapatalk HD
eushaun99 said:
I don't know. The hold down power button + volume down didn't work? You have to hold for at least 10 seconds.
Don't just say thanks...hit my thanks button.
Sent from my GT-P7500 using Tapatalk HD
Click to expand...
Click to collapse
Just tried that, when I selected recovery it just turned off
So you can get into download mode?
Download mode, yes. I've got it open now, in fact
Now that's easy. Your tab can't boot because it doesn't have any sort of recovery(don't ask me why I don't know ). Apparently ROM Manager wiped your recovery clean and didn't flash the new one. Just flash cwm or twrp via Odin and try to boot. If it still can't boot, then restore your nandroid. Ironically, the same thing happened to me yesterday when I tried to flash latest twrp using Mobile Odin.
Sent from my GT-P7500 using Tapatalk HD
What's odin?
Ok, It's all sorted now! Thanks for your help!
FelixJ20000 said:
What's odin?
Click to expand...
Click to collapse
You have never used Odin before? Then how on earth did you root?
Sent from my GT-P7500 using Tapatalk HD
eushaun99 said:
You have never used Odin before? Then how on earth did you root?
Sent from my GT-P7500 using Tapatalk HD
Click to expand...
Click to collapse
I actually have no idea. I think I used a program similar to Odin that did the job. I remember booting into download more before. Oh yes, I flashed the disk image for the root and CWM using the default windows tool. Anyway, I've fixed it now. I couldn't find a .tar to do the job so I converted a random file to a .tar and flashed it that way, tricking it into thinking it had a recovery and therefore booting. In the OS I used ROM Manager to get CWM.
FelixJ20000 said:
I actually have no idea. I think I used a program similar to Odin that did the job. I remember booting into download more before. Oh yes, I flashed the disk image for the root and CWM using the default windows tool. Anyway, I've fixed it now. I couldn't find a .tar to do the job so I converted a random file to a .tar and flashed it that way, tricking it into thinking it had a recovery and therefore booting. In the OS I used ROM Manager to get CWM.
Click to expand...
Click to collapse
Sent from my AWESOME Ponified HTC Sensation using Tapatalk 4
I flashed this with Cyanogenmod 11 soon after I got it 2 months ago. Well times are tough and I have to sell it on eBay. I want to remove Cyanogenmod 11 and revert back to stock. I know the thread where the stock ROM and PIT files are (http://forum.xda-developers.com/showthread.php?t=2192488) so thats half the battle there. Is it the same process as this (http://forum.xda-developers.com/showthread.php?t=1531850) or is there something else I need to do. Do I have to install GA APPS like you do with custom ROMs or is that not needed
This is all pretty new to me. I know how to flash custom ROMs and such but flashing the stock ROM seems tricky to me. Sorry if this has all been covered so many times that it makes you tired of seeing this, I just have to be sure I do this right and dont brick it (cant sell a paper weight on eBay for too much money lol).
Any help would be greatly appreciated! Thanks for all the hardwork that goes into making these ROMs as well
EDIT: Can I flash the stock ROM with the US Kernal, US PIT file and 2.3.5 gapps like I did with Cyanogenmod 11 or is that impossible?
Again sorry for the newbie question!
You need to wipe all data and use Odin to flash your gingerbread firmware.
Sent from my YP-G70 using XDA Free mobile app
troy5890 said:
You need to wipe all data and use Odin to flash your gingerbread firmware.
Sent from my YP-G70 using XDA Free mobile app
Click to expand...
Click to collapse
Okay that makes sense then. Do I boot into recovery, wipe data and then flash everything using Odin or is there a more preferred way to wipe data. Just making sure I have all this sorted before I do something bad.
catch_2030 said:
Okay that makes sense then. Do I boot into recovery, wipe data and then flash everything using Odin or is there a more preferred way to wipe data. Just making sure I have all this sorted before I do something bad.
Click to expand...
Click to collapse
I think after flashing a factory firmware by Odin, the device will AUTOMATICALLY boot into stock recovery, where you can wipe data in the correct format. At least that's what it said in the guide I read, and also happens on my Player 4.0 for both Froyo and Gingerbread.
Sent from Google Nexus 4 @ CM11
Now I have a boot loop.... I followed this guide with no success. http://forum.xda-developers.com/showthread.php?t=1850600
Any other ideas?
I am getting lots of errors in recovery mode. Lots of can't mount errors and everything else. I have no idea what to do now. So much for selling this to make some money.
Dude I had the same problem all you need to do is flash RJ cwm 14 kernel then go back in download mode go to Odin and I hate to say this but flash your gingerbread firmware. Tell me if this works or not because this happened to me 3 times Boot loop and brick status and semi brick.
Sent from my YP-G70 using XDA Free mobile app
troy5890 said:
Dude I had the same problem all you need to do is flash RJ cwm 14 kernel then go back in download mode go to Odin and I hate to say this but flash your gingerbread firmware. Tell me if this works or not because this happened to me 3 times Boot loop and brick status and semi brick.
Sent from my YP-G70 using XDA Free mobile app
Click to expand...
Click to collapse
No did not work. Still stuck in the boot loop. When I am in Recovery mode, I get unable to mount errors. It wont see my external SD card either.
catch_2030 said:
No did not work. Still stuck in the boot loop. When I am in Recovery mode, I get unable to mount errors. It wont see my external SD card either.
Click to expand...
Click to collapse
Well since you're getting mount errors, are you sure you flashed the correct PIT file? Mount errors are likely caused by a wrong pit file.
EDIT: I see you have pointed to a thread with correct PIT files. So I think you should flash the PIT file first, boot into download again and then flash the Stock ROM and Kernel. If it boot loops at the boot animation, boot into the stock recovery and wipe data.