I went from stock Froyo 2.2 to MIUI v3 using the following link.
http://forum.xda-developers.com/showthread.php?t=992251
Now when I startup my phone...
For one, it won't connect me to a network so I can't get phone calls or texts etc.
Also my volume up button is switched with my volume down button.
Trying to make a phone call it says "Mobile network not available".
Does anyone have any information to help me fix this problem? I am stuck.
Yea flash the miui version made for the vibrant in our development section
http://forum.xda-developers.com/showthread.php?t=992302
The one you flashed is for the International galaxy S
bfranklin1986 said:
Yea flash the miui version made for the vibrant in our development section
http://forum.xda-developers.com/showthread.php?t=992302
The one you flashed is for the International galaxy S
Click to expand...
Click to collapse
Ok sooo...
I downloaded
kernel-cm-7-INITIAL-Vibrant-signed.zip
renamed it to update.zip
copied the update.zip along with the MIUI 1.5.20 english pack one to the root of my SD card (internal sd root)
Went into recovery mode, and tried to flash update.zip. It gave me some assert error right away. Now my phone is in a cycle of rebooting where it reboots into the flashing thing, tries to load real quick and then reboots itself.
Any tips? I'm kinda scared.
Odin back to stock and then try again, this guide by s15274n has all the files you need and step by step instructions.
http://forum.xda-developers.com/showthread.php?p=13132341#post13132341
The vibrant files you flashed probably weren't compatible with the I900 kernel/recovery you had flashed.
GTASouthPark said:
Ok sooo...
I downloaded
kernel-cm-7-INITIAL-Vibrant-signed.zip
renamed it to update.zip
copied the update.zip along with the MIUI 1.5.20 english pack one to the root of my SD card (internal sd root)
Went into recovery mode, and tried to flash update.zip. It gave me some assert error right away. Now my phone is in a cycle of rebooting where it reboots into the flashing thing, tries to load real quick and then reboots itself.
Any tips? I'm kinda scared.
Click to expand...
Click to collapse
odin jfd, root, flash recovery then start over with the cm7 kernel then mui.
I'm having a problem following the guide...
Under 2 - Download 3 files..
Mount your phone and move the rom to the internal
AND the UPDATE.ZIP << DOWNLOAD
file if you wiped both internal/external or need to root.
Power down the phone, or pull the battery.
Click to expand...
Click to collapse
I don't know how I can get my phone mounted. Whenever I plug my phone into my computer (with the battery in), it automatically reboots itself and starts the crazy reboot thing. I also can't get back to recovery or downloading mode, it automatically goes back into the reboot thing.
And then in step 3 where it says start Odin, plug in your usb cable. With the battery out of your phone hold both volume buttons for a couple seconds and then plug in your USB cable. That doesn't take me to downloading mode.
EDIT:
Okay I figured out how to get it into downloading mode again. I need to do what it says above by holding the volume buttons with the battery out etc. Then you add the battery.
Hi guys. I got Odin to work. got back to stock.
Then got back into recovery mode to flash the cm7 kernel...
It is the same error as last time. Here's the actual error this time.
-- Installing: /sdcard/update.zip
Finding update package...
Opening update package...
Installing update...
assert failed: is_mounted("/mnt/sdcard")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
GTASouthPark said:
Hi guys. I got Odin to work. got back to stock.
Then got back into recovery mode to flash the cm7 kernel...
It is the same error as last time. Here's the actual error this time.
-- Installing: /sdcard/update.zip
Finding update package...
Opening update package...
Installing update...
assert failed: is_mounted("/mnt/sdcard")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Are you going under install zip from sdcard or just pressing reinstall packages? Instructions say to select reinstall packages after you rename it update.zip
bfranklin1986 said:
Are you going under install zip from sdcard or just pressing reinstall packages? Instructions say to select reinstall packages after you rename it update.zip
Click to expand...
Click to collapse
I boot into recovery mode. It takes me to the stock recovery mode. Then (with the update.zip and the miui zip in the root) I hit reinstall packages. It takes me to the clockwork recovery. Then I do install zip from sdcard. Trying to install the update.zip or the miui at this point gives me an error and then any kind of restarting will throw it into the reboot cycle.
EDIT:
When do I remove the battery? I do reinstall packages, and then after about a second or two it goes to the clockwork recovery, and then I removed the battery like it said. After I booted into recovery again and it took me to the clockwork recovery again, and then I tried to load the miui and again an error flashing.
EDIT 2:
For some reason Odin back to stock changed my phone to 2.1.. I upgraded it to version 2.2.1 (not using keis). I was able to get much further than normal when flashing the miui.zip.
My phone tries to startup, it gets to the Samsung loading image (which says i9000 under the samsung logo).
After that the screen goes (and stays) black. When I hit any of the buttons on the bottom, they glow white so I know that it is turned on.
I can't see anything on the screen, but I must be able to get it into downloading mode because I can get it to say 'added', and get try to start loading things, but then it starts never actually connets, it just hangs. Any ideas? Getting it back to stock right now would be fine so that it is usable again.
EDIT 3:
Ok, now I can see things again. For those who are wondering...
I had downloaded the 'Galaxy One Click Root' thing to try to root my phone before installing miui like it says. Well there's also a unroot button. I clicked that and I got it to go back into this custom recovery image. Once I did that, I navigated around a little and found something that said switch to Downloading mode. I did that, and then was able to use Odin to get back to stock. The screen is working, and so does the radio. It's back to 2.1 though. hmm..
ok so lets try this from the beginning
go ahead and odin to stock jfd (2.1)
now let phone boot as normal
no worries about letting it sit 10 mins or anything.
ok so you have the cm7 initial kernel as an update.zip correct?
3 button into recovery reinstall packages twice that should load you into clockwork
(orange clockwork menu)
1 Mounts and storage menu
Format system/cache/data (do all 3)
+Go Back+
wipe data/factory reset
Pull battery Or just press and hold all vol up + down + power
back in recovery.
install zip from sd Card
Install the Miui ROM reboot system.
lemme know how it goes.
boystuff said:
ok so lets try this from the beginning
go ahead and odin to stock jfd (2.1)
now let phone boot as normal
no worries about letting it sit 10 mins or anything.
ok so you have the cm7 initial kernel as an update.zip correct?
3 button into recovery reinstall packages twice that should load you into clockwork
(orange clockwork menu)
1 Mounts and storage menu
Format system/cache/data (do all 3)
+Go Back+
wipe data/factory reset
Pull battery Or just press and hold all vol up + down + power
back in recovery.
install zip from sd Card
Install the Miui ROM reboot system.
lemme know how it goes.
Click to expand...
Click to collapse
I was back at stock (which I'm not sure is 100% stock because when I turn on my phone, it has a samsung GT-i9000 image on the screen for a second or two before saying vibrant).
I have the update.zip and the miui on my internal sd root.
To get into recovery it's just the 2 button combo (volume - and power) for me.
I only have to hit reinstall packages once, and it takes me into clockwork.
I format the things you said and did the factory reset....
Pulling the battery and then trying to get back into recovery mode put my phone into a reboot cycle. (screen where it looks like after you do wipe data/factory reset) and then I have to odin back to stock.
The three button combo does the same thing. I can't get to the next step.
EDIT:
After the reboot cycle thing. I was able to get back into recovery mode even after it started its reboot cycle deal. Then I was able to install the miui rom. My phone has been on the Samsung Cyanogenmod boot screen for about 5-10 minutes. Not sure if it is trying to boot up miui or just stuck. I'll let it sit for another 15 minutes before thinking its stuck.
EDIT2:
Yep, It's been about half an hour. My phone is stuck on the cyanogenmod boot screen. I can't get it back into recovery or downloading either.
EDIT3:
After some serious playing around. I was able to get it back into recovery mode. Wipe everything, apply the update.zip again... and then was able to get back into downloading mode and reflash it to stock.
Does anyone know how to get to true stock, so I don't have the Galaxy-S GT-i9000 Samsung boot screen. I think that this has to do with why it is failing.
After searching around a lot more...
accidentally flashing an i9000 rom flashed the boot.bin and sbl.bin.
The files to odin back to stock jfd doesn't include the boot.bin or sbl.bin so that's why I get the extra boot screen, and why I 'brick' my phone everytime I try to flash another rom.
Apparently I will brick my phone anytime I try to flash a rom from now on, and that I need to find a boot.bin and sbl.bin combo for the vibrant if I want to be able to flash anything again or get any update past 2.1.
If anybody has any info on how to get this boot.bin and sbl.bin combo could you let me know. I can't find the files anywhere.
Related
So I'm having this problem with these 2 things.
If I install MDJs gingerbread nand rom after recovery, my recovery breaks and I can't backup or restore or pretty much anything useful in it. Nothing works and I keep getting errors like can't find MISC, can't mount cache/recovery/log or something like that and a bunch of other errors, so I reinstall the recovery but then my room gets an error loading from MAGDLR which says "nand kernel open failed" in red and my rom won't load so I have to reinstall the rom, and then recovery breaks again.
Any ideas on how to fix this? I don't think it's just a problem with MDJ's rom, but then again I don't know enough to figure out what the problem is. Any help is appreciated, thanks
You don't just find a nand build and flash it on... You need to use specific builds that support clockwork to be able to boot successfully. They're zip files, and there aren't many in the nand section.
To install it, you have to copy the zip file to your sdcard, and through magldr, Boot to SD by holding down the power button, using the volume rocker to navigate, and then through clockwork, flash the zip onto nand.
Moon2 said:
You don't just find a nand build and flash it on... You need to use specific builds that support clockwork to be able to boot successfully. They're zip files, and there aren't many in the nand section.
To install it, you have to copy the zip file to your sdcard, and through magldr, Boot to SD by holding down the power button, using the volume rocker to navigate, and then through clockwork, flash the zip onto nand.
Click to expand...
Click to collapse
So how do I get the clockwork recovery to work after installing the nand rom?
The mistake you're making is that you're flashing on a "NAND" build after installing clockwork. YOU DO NOT INSTALL A ROM WHERE YOU HAVE TO RUN a DFT.exe or AndroidInstaller.exe or anything of the sort.
To access clockwork again, reboot, hold down the power button, and choose boot Android from SD.
Note: Future magldr versions may have another menu for this build in.
James_Caliber said:
So how do I get the clockwork recovery to work after installing the nand rom?
Click to expand...
Click to collapse
Buddy if you are getting "All Done" message after installing a NAND rom through Clockwork Mod Recovery but still not able to boot( i faced this problem before), then I am afraid you will have to do what they call "task 29"...do some searching on xda for links, i'll give you the procedure -
Basically, task 29 is to cleanup the system completely and start all over again...which means that after doing task 29 you'll having nothing but hspl on the system. As scary as it sounds, since HSPL will not be wiped, you have nothinng to fear but only follow each instruction carefully:
1. back up and format your sd card to clean it up.
2. download Task29 and put your own RADIO file(if you don't want to use the provided radio file in Task 29 folder). e.g. i'll replace my radio rom 2.15.50.14's ".nbh" (new Radio) in the folder which had some 2.08.xx(.nbh)(older radio).
3.a. Restart phone by pressing volume down button and power button simulatenously, this would bring the red/green screen - connect USB to the pc and phone.
3.b. Run the update utility, after which white htc screen would boot and basically your system is completely clean. just pull out the battery and retart system by pressing volume down button and power button simulatenously, this would bring the red/green screen.
4. Now one by one install MAGLDR 1.11 (DAF.exe installation)
5. then install clockwork recovery for hd2 (DAF.exe installation, which gives you partition messages)
6. boot into clockwork recovery, you will notice the mounting errors will be not there now
7. Install your NAND rom from sd again and reboot, it shud work this time
Getting to Recovery in GB
Besides using a reboot into recovery app, you can also shut down the phone, then pull the battery, put the battery back in and the normal Vol Down + Power will get you into Clockwork Recovery. Seems like GB is in some kind of stand by mode even when you power it down.
WILL_B_WOODS said:
put the battery back in and the normal Vol Down + Power will get you into Clockwork Recovery.
Click to expand...
Click to collapse
No it won't, it will put you into bootloader.
I am currently trying to flash my vibrant back to stock 2.2. My latest attempt was done using the AIO tools. Every method I have tried has lead to the Vibrant boot screen appearing for a few seconds, and then rebooting. Any suggestions?
Have you tried Odin?
Sent from my SGH-T959 using XDA
whatever5 said:
Have you tried Odin?
Sent from my SGH-T959 using XDA
Click to expand...
Click to collapse
Yes, I have tried Odin with and without AIO tools. In all of the threads I have looked at, the answer seems to be flash back to 2.2 stock, but that is what I am trying to do. Thanks.
Try to boot into recovery and factory reset and see if that breaks the bootloop. If not, see below.
*********
Do you have a nandroid backup of the 2.2 you were on an using? If so, I suggest Odin-ing to stock (2.1), then pull the CWR from my signature put it on your internal card and label it Update.zip. Boot into recovery and hit Reinstall Packages. It will cycle through and you'll have to hit it again. It will cycle through again and your stock (blue) recovery will go to CWR (green). From there you can restore your nandroid backup of the 2.2 you last made (or should have).
You can go to 2.1 using the toolbox, as it has the correct pit/tar files to do so.
Woodrube said:
Try to boot into recovery and factory reset and see if that breaks the bootloop. If not, see below.
*********
Do you have a nandroid backup of the 2.2 you were on an using? If so, I suggest Odin-ing to stock (2.1), then pull the CWR from my signature put it on your internal card and label it Update.zip. Boot into recovery and hit Reinstall Packages. It will cycle through and you'll have to hit it again. It will cycle through again and your stock (blue) recovery will go to CWR (green). From there you can restore your nandroid backup of the 2.2 you last made (or should have).
You can go to 2.1 using the toolbox, as it has the correct pit/tar files to do so.
Click to expand...
Click to collapse
I currently can not get into recovery mode. I am holding the power, vol+, and vol- buttons, inserting the battery and then releasing them when the vibrant screen appears. But it just continues to boot cycle.
I flashed the pit and tar that came with AIO tools. No go. Still just boot cycles. Sorry for being a pain.
I do have a backup, but I am not sure what I can do with right now.
Try turning the phone off, plug in USB hold just volume up and power on the phone..... that should put it into download where you can run Odin and flash back to stock
Sent from my touchpad using XDA
related problem (sort of)
Solved: problem solved. I reflashed CM7 over the bootlooping mess, and it took. Then I was unable to get AIO Vibrant Toolbox to recognize that debugging mode was on, even though it was. So I just copied the files over and went through a massive round of forcing the zip files on again and again. I now have Slim 3.5 on my phone, so I can start playing with it.
*****************************************
I'm an extreme noobie, trying to upgrade my T959 to ICS. I've picked Slim 3.5 (latest release version as of this week) as my first attempt (but really any simple but well-functioning ROM will do for me).
I've rolled back to Eclair (from the official Tmo Froyo upgrade way back when), rooted, and numerous times followed various directions to install the zip for Slim -- sometimes trying CM7 as an intermediate step. The CM7 install failed in the same way as the ICS, as described below.
I've done it with and without AIO Vibrant Toolbox. I've used ClockworkMod Recovery 2.5.1.2 to wipe the data, clear both cache partition and Dalvik cache, and format system. I've popped the zip file in various folders and at toplevel, both external and internal SD.
In all cases, it gets off to a good start, and then I'm left with endless bootlooping: Vibrant logo, Mod logo, a textblock of about 15 lines, repeat. I've always been successful after that in using Odin3 v1.81 to get back to Eclair.
I got sucked into a tech vortex until 4:30 am last night trying again and again, and I'm way way too old for that!
Any thoughts?
Hello wonderful people of the S. Vibrant community. I come to you in order to diagnose and hopefully fix a problem with a friends samsung vibrant.
Basically here's the backstory... He wanted to root his Vibrant (2.2 i believe) to ICS so i sent him the AIO Vibrant toolbox and told him explicitly to read the instructions of the tool and any potentials roms he wants to put on his phone. Lo and behold! I proceed to take a 2 hour map and my phone is bombarded with text messages saying that he 'messed up' and the phone is 'looping' upon boot.
I absolutely do not know what the hell he did and he was intentionally vague on what steps he took and what roms he downloaded etc. He mentioned something about reformatting and downloading a new kernal ...
Anyways. As I'm an owner of a Sprint SGS2; i know that sammys are literally the hardest devices to hard brick so i proceeded to search up these forums and odin a stock tar so i can get this thing booted up.
I followed this guide
http://androidspin.com/2010/08/09/how-to-restore-or-recover-your-samsung-vibrant/ and proceeded to odin back the pit and tar and it was a success.
Then it rebooted and bam still a boot loop. I tried a KA6 tar and still the same results. So I'm stuck here on how to get this phone out of the boot loop and am wondering if you guys can direct me to where I can hopefully fix this problem.
Side note. AIO Vibrant toolbox says the phone has USB Debugging mode off... (SMFH!!!!).
Thanks guys!
Download the bionix V fish man ROM. Its froyo, its good and it has an Odin flashable file. It comes with Bali kernel.
May help you on your way.
http://forum.xda-developers.com/showthread.php?p=21324042
Even though its boot looping, if you can get into recovery, you may be able to flash about any ROM you want. Wipe data/factory reset, clear cache and dalvik, and flash a good solid ROM. I've gotten out of the situation using both of the options I've listed.
May the force be with you.
I'll try and see if this will work and report back.
Well i odin'd the rom according to instructions and it's on the bali screen now for 5 mins... How long does the first boot take
lilotimz said:
Well i odin'd the rom according to instructions and it's on the bali screen now for 5 mins... How long does the first boot take
Click to expand...
Click to collapse
It does take a while. I'd let it go at least another few minutes. Then update me.
---------- Post added at 11:51 PM ---------- Previous post was at 11:46 PM ----------
If your still stuck, pull battery and boot into CWM recovery. Find Voodoo lagfix in the options. Disable it and reboot the phone. That's most likely why its hanging on the first start.
After you get it booted the first time you can go later and reenable voodoo lagfix.
tried using adb reboot recovery cmd and still no dice...
I assume froyo bootloader, hold both volume buttons and power until you see Samsung text and let go. May take a couple tries.
there is no samsung text. It goes white screen then Bali screen and repeat... (boot loop i guess.. again)
Update : Flashed the second odin tar and it seems to be somewhat working now... got into recovery mode and wiped data / cache... rebooting now
Excellent. If that doesn't boot all the way go back to recovery and disable voodoo lagfix.
Well i got into samsung recovery and deleted user data & cache data.
It does indeed go white screen then Bali screen for some reason... same.
Boot loop. No option to disable voodoo lagfix. Recovery is not CWM but samsung recovery... ?!!
lilotimz said:
Well i got into samsung recovery and deleted user data & cache data.
It does indeed go white screen then Bali screen for some reason... same.
Boot loop. No option to disable voodoo lagfix. Recovery is not CWM but samsung recovery... ?!!
Click to expand...
Click to collapse
Hmm. If you have the update.zip on your phone you can click reinstall packages and it will be CWM recovery.
here's what it says...
Update media:
E: Can't mount /dev/block/mmcklk0p1
(no such file or directory)
E: copy_dbdata_media; Can't mount SD card:
your storage not prepared yet.Please use UI menu for format and reboot actions
E:Copy_dbdata_media:format SDCARD:
formatting Sd card:...
E: Can't mount /dev/block/mmcblk0p1
(No such file or directory)
E: copy_dbdata_media: Can't mount SDCARD:
your storage not prepared yet,please use ui menu to format and reboot actions
copy default media content failed
Your internal sd has been destroyed. Your only option is running the entire os off of an external microsd card. http://forum.xda-developers.com/showthread.php?t=1580902
At least it seems like this is the case. I also had this happen to my phone, but eventually it fixed itself after odining about 20times and installing other roms. Good luck. Heres what I did http://forum.xda-developers.com/showthread.php?t=1665123)
Didn't work for some people, so the fact that mine came back might have just been luck.
le sigh...
I guess i'll try some more tomorrow. Guess he did the unthinkable and 99.9% killed a sammy. Poor galaxy s...
I finally managed to follow your instructiosn and i installed CM9 for the first time and it's now boot looping. Your instructions state to reboot into recovery mod and install it again but I for my life cannot discover how to reboot this thing into recovery mod. What are the steps and buttons again if I may ask?
lilotimz said:
I finally managed to follow your instructiosn and i installed CM9 for the first time and it's now boot looping. Your instructions state to reboot into recovery mod and install it again but I for my life cannot discover how to reboot this thing into recovery mod. What are the steps and buttons again if I may ask?
Click to expand...
Click to collapse
Pull the battery and replace it, hold vol up, vol down and power until you see screen come on then release. That should take you to recovery.
sent from the depths of helly bean
Samsung Vibrant, unlocked, was rooted on SlimBean 4.2.1 beta2 OC'd to 1.2ghz. Anyways...
I was using my phone this morning and it suddenly just failed. Rebooted to initial "Vibrant SAMSUNG" screen with no warning, an then stuck at that screen. Pull battery, reboot. Pull battery, vol+ vol- pwr. Same results. Could get to Download though.
Got home in the afternoon. Tried to Odin to stock. After Odin kludging up and failing a few times, I manage to get it to succeed with the PIT and TAR that come with the AIO toolbox. Reboot... No dice. Now just loops the same initial screen, with a half-second blackscreen between. Reboot to recovery... Stock recovery, so can't flash anything. Use an external microSD adapter to put another SLimbean rom on there, name it 'update.zip." Flash zip. Fails at "Slim Bean v.whatever, formatting /system and /data..." More screwing around with Odin. Find stock bootloader in a .tar.md5, flash it with the same PDA (no PIT this time as it caused Odin to fail and I believe my partitions are correct), failure. Repeating this odin now, will update with results.
Any help would be greatly appreciated. You guys have helped me in the past, I know you can do it!
EDIT: More odining, got a quite scary message of "KERNEL PANIC UPLOAD MODE" with some red writing superimposed on it. Looks pretty damn dead. Might go to the last resort and try the UnBrickable Mod...
EDIT 2: Reboot recovery, wipe user data, try to install SLimbean zip again, fails. Reboot, stuck at same "vibrant" screen. Recovery again and Semaphore Recovery comes up! Try to flash zip, the file list thing is of my _external_ sd. Fails at same place, with generic error. Can't mount anything else, only external SD is visible. Weird...
Try booting after removing external Sd. Stuck at Vibrant screen.
Put in sdcard again, reboot to recovery. Trying things, hit "reboot recovery" from recovery. Similar error message to the kernel panic screen before: "POWER RESET or UNKNOWN UPLOAD MODE" with similar red text.
Okay, will work on this tomorrow. Again, any help would be very, well, helpful. Thanks!
Another EDIT: Few more details about recovery:
Installing slimbean fails with "status 0"
Mounting or wiping anything except USB storage results in a black "flicker" and recovery restarts
USB storage shows two drives on the PC: One that used to be internal SD that is now the external, and another that gives the "empty drive" message
I think the phone somehow swapped the SD cards.
When you flash to stock was it JFD? Did you hsave reparition checked?
Also - Pull the external sdcard out. I have found it causes boot loops when going from JFD to JB. That said pulling the sim card wont hurt either.
Moped_Ryder said:
When you flash to stock was it JFD? Did you hsave reparition checked?
Also - Pull the external sdcard out. I have found it causes boot loops when going from JFD to JB. That said pulling the sim card wont hurt either.
Click to expand...
Click to collapse
Sorry for the noob question- What is JFD? No, I did not have repartition checked as Odin would lock up and eventually fail if I did.
It doesn't seem to boot without the external SD. I could try Odin without it, (If I can get Odin to work) would that help?
EDIT: Just found http://forum.xda-developers.com/showthread.php?t=1665123 , looks right. Will try once I get a spare flash drive to GParted-ize.
yet another EDIT: Partitioned SD, still no download mode, still can't install from zip. I may be in the market for a new cell phone soon...
Finally SUCCESS!
After parting SD, held both vols, plugged in, download mode! Got odin to work, am now running absolute stock. Not sure if internal memory is OK though...
I have the Galaxy Note SGH-I717R (Rogers version), with the stock android 4.0.4 installed. I want to install a custom ROM but I cannot get TWRP Recovery to work on this phone. I have followed all the guides but it will not work, even though it appears to install correctly. I put my phone into download mode, start odin in admin mode, attach my phone, it is recognized by odin, then I choose PDA and select the TWRP Recovery tar file (which is the correct one for my device). After I click Start on Odin it goes through these messages as it installs and reboots my device:
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
and the box in the upper left corner turns green and says "Pass!".
After this, I have my phone usb disconnected and I reboot into recovery mode.. Only when it starts in recovery, it is the same stock recovery mode that comes with stock android! With this, I cannot flash the custom ROM because it gives the error that verification failed.
I have tried installing TWRP through goo manager as well, but when I choose the openrecoveryscript option, it says that nothing was found for my device.
What am I missing here? How can I install this custom recovery to allow me to flash a custom ROM?
I also tried this with 2 different versions of TWRP - 2.5.0.0-quincyatt.img and the latest 2.6.3.0-quincyatt.img
This may seem like a silly question but does the TWRP package include root in it? I have had to root with Clockwork mod tar first and then I have installed TWRP after that.
There are free utilities on Google Play that can tell you if you are rooted or not.
Download the 2.6.1.0.IMG.tar file and flash it. Also change the USB port you are using, and reinstall the Samsung USB drivers before attempting it again.
fraughtsigewulf said:
This may seem like a silly question but does the TWRP package include root in it? I have had to root with Clockwork mod tar first and then I have installed TWRP after that.
There are free utilities on Google Play that can tell you if you are rooted or not.
Click to expand...
Click to collapse
according to others, you do not need to be rooted to flash a rom.
I flashed a zip file for TWRP, just like a normal rom. once you flash, it replaces your cwm.
the error????????? if it is status 7, your recovery needs to be updated
OK, I've solved the problem. I followed another video that said to uncheck auto reboot on odin when installing TWRP, then remove the battery and unplug once it loads it on. I did this, and ended up bricking my phone, it wouldn't start saying need to fix bad firmware in kies recovery. Kies wouldn't even detect my phone at this point, so I started Odin again and was able to run a recovery from there by pressing start, it said it removed something, and was successfully recovered. I tried rebooting into recovery mode again on my phone, and magically it loaded into TWRP! From there I was able to flash the custom Revolt ROM and now my phone is running fine.
You got it. The Canadian phones have a script that reinstalls the 3e stock recovery on the reboot. So you have to pull the battery to stoo that script from running. When you rhen boot into recovery it makes it the default recovery.
ok, i've flashed via odin, pulled the battery and started it up but it still goes to stock recovery.
I've also flashed, shut it down, pulled the battery, rebooted and then selected reboot in recovery with no luck either.
Am I missing something?
Thanks
rangercaptain said:
You got it. The Canadian phones have a script that reinstalls the 3e stock recovery on the reboot. So you have to pull the battery to stoo that script from running. When you rhen boot into recovery it makes it the default recovery.
Click to expand...
Click to collapse
Thanks! I was trying to instal ClockworkMod Recovery with no luck, I have an Australian Version of GT-I9506, and your tip worked for me! Solved... :victory::victory:
can't get it done
rangercaptain said:
You got it. The Canadian phones have a script that reinstalls the 3e stock recovery on the reboot. So you have to pull the battery to stoo that script from running. When you rhen boot into recovery it makes it the default recovery.
Click to expand...
Click to collapse
I just can't get recovery to work after pulling the battery, it keeps on saying firmware error. What I am doing wrong?
rangercaptain said:
You got it. The Canadian phones have a script that reinstalls the 3e stock recovery on the reboot. So you have to pull the battery to stoo that script from running. When you rhen boot into recovery it makes it the default recovery.
Click to expand...
Click to collapse
mayoni said:
I just can't get recovery to work after pulling the battery, it keeps on saying firmware error. What I am doing wrong?
Click to expand...
Click to collapse
I'm having the same problem with an SGH-I717R. I flash TWRP with ODIN, pull the battery and disconnect the USB cable so the phone powers off. Then I hold Vol Up+Vol Down+Power until the phone vibrates, I see the "Samsung Note" logo on the screen for a fraction of a second, then it goes into "ODIN MODE", tells me how many custom binaries I've flashed, etc, and says "Firmware upgrade encountered and issue" and tells me to run recovery from Kies. If I restart the device normally, it goes into this mode as well. I can return the phone to a usable state by booting into download mode, flashing TWRP again with ODIN, then letting the phone reboot without holding any buttons down, but then recovery is back to stock 3e.
I've also tried this using CWM and Heimdall, as per the instructions on the CM wiki, with the same results. I've uninstalled and reinstalled the USB drivers and also enabled USB debugging on the device, since I read somewhere that might be an issue. I realize I'm replying to a 2-year old comment from rangercaptain, but do you have any more suggestions?
mdm_ said:
I'm having the same problem with an SGH-I717R. I flash TWRP with ODIN, pull the battery and disconnect the USB cable so the phone powers off. Then I hold Vol Up+Vol Down+Power until the phone vibrates, I see the "Samsung Note" logo on the screen for a fraction of a second, then it goes into "ODIN MODE", tells me how many custom binaries I've flashed, etc, and says "Firmware upgrade encountered and issue" and tells me to run recovery from Kies. If I restart the device normally, it goes into this mode as well. I can return the phone to a usable state by booting into download mode, flashing TWRP again with ODIN, then letting the phone reboot without holding any buttons down, but then recovery is back to stock 3e.
I've also tried this using CWM and Heimdall, as per the instructions on the CM wiki, with the same results. I've uninstalled and reinstalled the USB drivers and also enabled USB debugging on the device, since I read somewhere that might be an issue. I realize I'm replying to a 2-year old comment from rangercaptain, but do you have any more suggestions?
Click to expand...
Click to collapse
There is an Odin flashable cwm at rootgalaxynote. Once that is flashed you can load a su zip to your phone and flash or change to twrp by flashing it with cwm..not Odin. You then just reboot to recovery and you will be in twrp. You should probably use one from gimmeitorilltell version 2.8.0.0 or higher. I use 2.8.0.0 as it supports theming still. If you need more detail hit me up for the links. Searching the forum or googling should get you there though.
Sent from my SAMSUNG-SGH-I717
developweb said:
There is an Odin flashable cwm at rootgalaxynote. Once that is flashed you can load a su zip to your phone and flash or change to twrp by flashing it with cwm..not Odin. You then just reboot to recovery and you will be in twrp. You should probably use one from gimmeitorilltell version 2.8.0.0 or higher. I use 2.8.0.0 as it supports theming still. If you need more detail hit me up for the links. Searching the forum or googling should get you there though.
Sent from my SAMSUNG-SGH-I717
Click to expand...
Click to collapse
Thanks for the pointers! Would you say this tutorial[1] is more or less what you're suggesting I try? And then from there, flash TWRP 2.8.0.0 from CWM recovery?
[1] XDA won't let me embed a link because my account is too new, but it's a page on rootgalaxynote that ends with /galaxy-note-i717-roms/how-to-root-att-galaxy-note-sgh-i717-icsgingerbreadeasiest-method/
EDIT: Ugh, scratch that idea. I followed the instructions on that site and exactly the same thing happened. Flashing CWM through ODIN appears to work fine, but if I reboot immediately after flashing I end up with stock 3e recovery again, and if I hold Vol Up+Vol Down+Power to reboot immediately after flashing, I get the ODIN mode "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." message and can't get past it until I flash CWM with ODIN again and let the stock recovery overwrite on reboot.
EDIT #2: So I finally got it to boot CWM by holding Vol Up+Vol Down as ODIN reboots the device, but trying to flash the Superuser zip from that site results in an error and the instant you boot system, it overwrites recovery with stock again. Am I correct to assume that if I can get into CWM and flash a custom ROM, recovery will stop being reset to stock on every boot?
mdm_ said:
Thanks for the pointers! Would you say this tutorial[1] is more or less what you're suggesting I try? And then from there, flash TWRP 2.8.0.0 from CWM recovery?
[1] XDA won't let me embed a link because my account is too new, but it's a page on rootgalaxynote that ends with /galaxy-note-i717-roms/how-to-root-att-galaxy-note-sgh-i717-icsgingerbreadeasiest-method/
EDIT: Ugh, scratch that idea. I followed the instructions on that site and exactly the same thing happened. Flashing CWM through ODIN appears to work fine, but if I reboot immediately after flashing I end up with stock 3e recovery again, and if I hold Vol Up+Vol Down+Power to reboot immediately after flashing, I get the ODIN mode "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." message and can't get past it until I flash CWM with ODIN again and let the stock recovery overwrite on reboot.
EDIT #2: So I finally got it to boot CWM by holding Vol Up+Vol Down as ODIN reboots the device, but trying to flash the Superuser zip from that site results in an error and the instant you boot system, it overwrites recovery with stock again. Am I correct to assume that if I can get into CWM and flash a custom ROM, recovery will stop being reset to stock on every boot?
Click to expand...
Click to collapse
Did you repeat steps as instructed at this point?
If you get any errors at this point, don’t worry about it and repeat Steps 13 to Step 16 twice more and reboot. You will still get root.
Sent from my SAMSUNG-SGH-I717
developweb said:
Did you repeat steps as instructed at this point?
If you get any errors at this point, don’t worry about it and repeat Steps 13 to Step 16 twice more and reboot. You will still get root.
Sent from my SAMSUNG-SGH-I717
Click to expand...
Click to collapse
Yep, I was finally able to root the device doing that, but I still can't get CWM recovery to persist. I can flash it with ODIN, then hold down Vol Up+Vol Down as ODIN resets the device, which gets me into CWM recovery. From there I can do the usual CWM recovery stuff, and if I reboot, then hold down Vol Up+Vol Down immediately, I can get back into CWM recovery. I can do this as many times as I like and it always brings up CWM recovery. As soon as I let the phone boot the stock OS, CWM recovery is gone and I'm back to stock 3e. My end goal is to flash a custom ROM to this device; I assume if I do that, the stock recovery will stop being restored on every boot?
mdm_ said:
Yep, I was finally able to root the device doing that, but I still can't get CWM recovery to persist. I can flash it with ODIN, then hold down Vol Up+Vol Down as ODIN resets the device, which gets me into CWM recovery. From there I can do the usual CWM recovery stuff, and if I reboot, then hold down Vol Up+Vol Down immediately, I can get back into CWM recovery. I can do this as many times as I like and it always brings up CWM recovery. As soon as I let the phone boot the stock OS, CWM recovery is gone and I'm back to stock 3e. My end goal is to flash a custom ROM to this device; I assume if I do that, the stock recovery will stop being restored on every boot?
Click to expand...
Click to collapse
Sorry this didn't work for you, but I'll throw in the last bit anyway.
" With Android 4.0.4 update, your phone might overwrite the ClockworkMod Recovery you flashed in ODIN. To get around the problem, simply flash ClockworkMod Recovery again in ODIN, then when you see “PASS!”, immediately hold down Volume Up and Volume Down buttons, you should be in ClockworkMod Recovery instead of the Belly-up Andy Android figure."
Sent from my SAMSUNG-SGH-I717
Same Problem
Huge problem