so i tried to install the simply galaxy 3.0 n it went into a bootloop and made crazy noises and colors every time it tried to boot. so i flashed ji6 through odin and no it will only boot to recovery. any help please?
tjhill01 said:
so i tried to install the simply galaxy 3.0 n it went into a bootloop and made crazy noises and colors every time it tried to boot. so i flashed ji6 through odin and no it will only boot to recovery. any help please?
Click to expand...
Click to collapse
Did you do a nandroid back up?
Try this
1 Flash just the .tar and check only auto reboot and F. Reset time
2 when it boots up and gives you an error in recover thats fine!
3 pull battery and put it into download mode again
4 flash a JFD tar with the 512 pit and check re partition, auto reboot, f reset time, phone efs clear, and phone bootloader update.
5 when it finishes let it sit for about 15 minutes and boot, and you should be back to stock, then you can root and away you go with your favorite rom!
Let me know if this works
Related
So i had flashed my Tmobile vibrant to trigger a couple months back and i was going to do the same for my moms vibrant today so i downloaded trigger 3.3.3 and put it in sdcard file then after backing up everything i put it into recovery mode and hit install from SD then chose the file i put there. it installs it then i hit reboot system then it shows the vibrant logo for 10ish seconds then reboots to recovery mode again. ive tried everythign to get it out of recovery mode but only thing that worked was restoring it. ive tried it 3 times so far all with the same results. i get ann error message though when i try to do it saying E: cant mount /dev/block/mmcblk1p2 (file exists) any help?
My solution to everything odin back to stock, then root ur phone. Flash clock work recovery flash rom again. Wiping data fixes most probs ive come to know
Sent from my SGH-T959 using XDA Premium App
Update:
i noticed that when it reboots after the vibrant logo after i flash it it goes into normal recovery not clockwork (blue/purple text not green)
if its blue then u need to install update package. Reinstall twice and it should turn green recovery! then flash rom.
follow this guide to root
http://forum.xda-developers.com/showthread.php?p=9375927 and then get clock work recovery and then flash
its green when I try to flash it goes back to blue after rebooting
MustangFTW said:
its green when I try to flash it goes back to blue after rebooting
Click to expand...
Click to collapse
I would start over odin back to stock and try again. You can use the toolbox
http://forum.xda-developers.com/showthread.php?t=954509
Okay, as the thread title states and as I had searched for a Samsung Vibrant related thread about this issue I haven't found any. My issue as stands is when I try to perform a Factory Data Reset on my Samsung Vibrant t959VUVKD1, 2.2.1 Froyo, it only comes up with this set of words on the recovery screen.
-- Wiping data...
Formatting DATA:...
Data wipe failed.
Formatting CACHE:...
Formatting DBDATA:...
Db data wipe Failed.
-- Appling Multi-CSC...
Installing Multi-CSC
Install default apk;files, please wait
E: Can't mount /dev/block/mmcblk0p2
(No such file or directory)
E:copy_data_default_apk:Can't mount DATA:
your storage not prepared yet, please use UI menu for format and reboot actions.
Click to expand...
Click to collapse
So, as one can see this is evidence of my attempt at rooting and using Clockworkmod Recovery.
What I used was SuperOneClick 2.2 and successfully rooted my phone but then I decided to unroot after finding out ClockworkMod Recovery wasn't able to create a backup on my phone, also, I used a 3e_recovery_installer batch file I found somewhere which managed to unlock my Android system recovery so I could get into Clockworkmod Recovery but ever since I unrooted and uninstalled Clockworkmod Recovery it won't allow me to perform a factory data reset. I was able to do it TWICE after unrooting my phone but now I can't perform the factory data reset and I do not understand why.
Have you tried to odin back to stock or use the toolbox?
http://forum.xda-developers.com/showthread.php?t=954509
Never used Odin or Toolbox before because I've never found a concrete tutorial on how to correctly flash/root my vibrant. I would like to flash but I just don't feel safe about it even though I had downloaded a supposedly stock rom of the UKVD1 rom for Vibrant.
nomadrider123 said:
Have you tried to odin back to stock or use the toolbox?
http://forum.xda-developers.com/showthread.php?t=954509
Click to expand...
Click to collapse
Erm, I used the Toolbox to use "Flash to Stock" and when Odin opened up I selected Pit.pit and it showed a yellow to green color on the first box and my phone turns off then nothing happens. What does this mean?
1. When odin opens select pit
2.click the Pit.pit file after screen change and click open
3.You should be returned to odin main.
4. click pda
5.click pda file and click open.
6.you are returned to main odin.
7.set phone down, click start and do not unplugg
8 let it run till pass, and auto reboot
Sugartibbs said:
1. When odin opens select pit
2.click the Pit.pit file after screen change and click open
3.You should be returned to odin main.
4. click pda
5.click pda file and click open.
6.you are returned to main odin.
7.set phone down, click start and do not unplugg
8 let it run till pass, and auto reboot
Click to expand...
Click to collapse
I did all that just now but now I'm stuck on a looping charging screen or a looping Samsung Vibrant screen. However, this isn't the same as the original T-Mobile screen and even so how do I get past the looping screen?
1. pull the battery
2. insert the battery
3.hold down volumeup/ volumedown buttons
4. insert the usb cable, you should enter download.
5 reset toolbox and select flash to stock, odin should appear,
My experience.
When you are facing boot loop, it's very hard to get in to download mode.
I tried button trick for download mode, but I failed.
So I used adb and tried to reboot into download mode by command.
I repeated it until I could get into the mode.
Anyway, download Toolbox and once u get into the mode,
try to go back to stock. That 'll fix everything.
I also know that the logo changed after I flashed back to stock.
I faced I9000 logo which wasn't before.
FYI: + the version will be eclair, and I couldn't get the official update.
Anyway good luck.
---------- Post added at 03:09 AM ---------- Previous post was at 03:02 AM ----------
If you never get into download mode.. Try to use JIG.
Another way is to disassembly your phone and do something.
I suggest you buy a JIG.
Problem is, I can easily get into Download mode by:
1. Remove USB Cable
2. Pull battery and re-insert
3. Plug in USB cable
4. Hold Volume - and +
And it's in Download mode
But I want to get the original Smasung Vibrant 2.2.1 UVKD1 Rom back on but it appears the provided files aren't it?
Btw, what is a Pit and and PDA file supposed to be, I'm a complete noob at this point.
The pit and pda files in aio toolbox are the stock rom the vibrant is shipped with, if you want anythig else on it you have to download it and flash it through odin, rom manager, or cwm.
Sugartibbs said:
The pit and pda files in aio toolbox are the stock rom the vibrant is shipped with, if you want anythig else on it you have to download it and flash it through odin, rom manager, or cwm.
Click to expand...
Click to collapse
I see. But now when the phone starts up it shows a buncha dots in consecutive order to the Samsung Vibrant screen after I flashed to stock using the pit and pda files and it just loops continuously until I pull the battery. Is there anything that can be done to get past the looping?
Does the pitcure look like a phone....!....computer? If so then you are softbricked and just get back in download mode and re-Odin, but make sure that when you Odin, you DO NOT have the repartition checked. Probably what happened.
If it is not the above, can you get into recovery? Can you now do a factory reset? Wipe cache, dalvik and reset usually clears the bootloop problem.
Woodrube said:
Does the pitcure look like a phone....!....computer? If so then you are softbricked and just get back in download mode and re-Odin, but make sure that when you Odin, you DO NOT have the repartition checked. Probably what happened.
If it is not the above, can you get into recovery? Can you now do a factory reset? Wipe cache, dalvik and reset usually clears the bootloop problem.
Click to expand...
Click to collapse
Unfortunately I can't get into recovery. I also Odin'd with the given Pit.pit and PDA.tar files with Repartition unchecked but that didn't change anything.
I cant figure how you could be in a bootloop coming out of odin. Is the AIO you downloaded for vibrant. I think theres one for fascinate and captivate.
Sugartibbs said:
I cant figure how you could be in a bootloop coming out of odin. Is the AIO you downloaded for vibrant. I think theres one for fascinate and captivate.
Click to expand...
Click to collapse
I used the AIO Toolbar for Vibrant as provided by the link by the person earlier. The loop just continues forever and ever until I remove the battery.
The three button method of entering recovery hasnt worked?
You mean hold Power and Vol + and -?
No, it doesn't work.
i am hesitant to advise anything, the fact that factory reset didnt work, and recovery has been removed is troubling. when i get a fail message when flashing to stock ive used eugenes froyo that does not brick. If all else fails you might google it and read the op. Its a pda file used by odin.
What I find strange is that download mode works perfectly fine but nothing else.
what I find strange is coming out of odin and looping, you should come out in recovery with an error message. a cannot mount data or bdata. storage not ready. Removing recovery may have removed more than was expected. check the op on eugenes froyo you have to get back to stock.
Hi,
I tried to root (first time) my S3 using this method http://forum.xda-developers.com/show....php?t=1703488
My S3 is the international version: GT-I9300.
I followed all the steps, except for one bit. In the prompts, I could not find the exact version of my S3. The guide said to use the closest one so I did. My build is JRO03C UBDLJ1 but I used number 9 (see guide photo 2). All went well until my phone won't reboot anymore. Odin and the root application says that everything is fine, except my S3 is stuck at the boot screen (Samsung Galaxy S3 GT-I9300 with black screen). I can still get into Download or Recovery modes. How do I fix this?
Any help is appreciated. Thanks in advance.
Recovery factory reset .
Fails then download mode and flash stock rom via Odin .
jje
JJEgan said:
Recovery factory reset .
Fails then download mode and flash stock rom via Odin .
jje
Click to expand...
Click to collapse
I'll try that tomorrow since it's already past midnight here where I live. Is there any way to turn the phone off? Cos it just keeps on rebooting up everytime I close it. Or is it okay if I just leave it on the boot screen. Will the battery run out?
simple take the battery out
in cwm
Delete cache,dalvik cache and it should boot! If it refuses flash stock and it will boot normally again!
I Think You Should Check This checkrom.com/threads/resurrection-odin-checkrom-evohd™-v4.896/
Please Report If It Worked
OK I managed to get this thing back working finally. What I did was flash it back to a stock ROM. I couldn't find my original version but close enough, except this version, 4.1.1 doesn't seem to be available (but thats not a big deal).
Now I'm too scared to try root it again lol...
And thanks for all the suggestions!!!
Follow up question:
Root attempt 2 = successful
I tried to install CyanogenMod 10 (via Odin). Except the device got stuck in the CyanogenMod spinning boot screen. Restored it via backup for now. Any idea why this is happening?
onevivip said:
Follow up question:
Root attempt 2 = successful
I tried to install CyanogenMod 10 (via Odin). Except the device got stuck in the CyanogenMod spinning boot screen. Restored it via backup for now. Any idea why this is happening?
Click to expand...
Click to collapse
I remember it takes some time for everything to load first time,maybe 5 or 10 minutes,also I think it`s better to use cwm to flash custom roms! just use odin for root and stock roms!
just move the file on the sdcard and boot in cwm,let it do his thing and then wait a bit!
blooxx said:
I remember it takes some time for everything to load first time,maybe 5 or 10 minutes,also I think it`s better to use cwm to flash custom roms! just use odin for root and stock roms!
just move the file on the sdcard and boot in cwm,let it do his thing and then wait a bit!
Click to expand...
Click to collapse
Yeah tried again via CWM and everything is working fine. Thanks for the advice!
Hey everyone. I'm hoping that someone can help me out.
I rooted my daughter's YP-G70 without issue and then tried to install a custom rom. It appeared to go okay but upon reboot, it just hangs at the Samsung logo and then reboots again about 5-10 seconds later in a loop at that point. I searched around and tried to restore to a stock rom including the PIT file using ODIN but that hasn't worked (even though is says that it completed successfully).
My other daughter's YP-G70 is still a completely stock ROM. Is there a guide somewhere that I could take a full backup of her Player 5.0, ODIN it over to the soft bricked player so that I can then just do a data wipe and have it back to stock?
Frodo56 said:
Hey everyone. I'm hoping that someone can help me out.
I rooted my daughter's YP-G70 without issue and then tried to install a custom rom. It appeared to go okay but upon reboot, it just hangs at the Samsung logo and then reboots again about 5-10 seconds later in a loop at that point. I searched around and tried to restore to a stock rom including the PIT file using ODIN but that hasn't worked (even though is says that it completed successfully).
My other daughter's YP-G70 is still a completely stock ROM. Is there a guide somewhere that I could take a full backup of her Player 5.0, ODIN it over to the soft bricked player so that I can then just do a data wipe and have it back to stock?
Click to expand...
Click to collapse
I guess you could still flash a custom kernel with CWM, then do a nandroid backup and restore that backup over the soft-bricked device. It could work.
You might want to try wiping data via recovery after flashing the rom.
For some reason, Odin didn't work for me either. I had to factory restore it with Heimdall.
TheKryptonite said:
For some reason, Odin didn't work for me either. I had to factory restore it with Heimdall.
Click to expand...
Click to collapse
What firmware package did you use and where did you d/l it from?
Frodo56 said:
What firmware package did you use and where did you d/l it from?
Click to expand...
Click to collapse
The one that Meticulus posted (http://www.4shared.com/rar/XkZ-pDCc/...EKI8_MIN.html?) in this topic: http://forum.xda-developers.com/showthread.php?t=2361763
-Add the pit file from the "Flash" tab (top)
-Change the partition name "FactoryFS"
-Click "Browse" (top)
-Add the previous pit file that you just added (bottom) (ignore the message that pops up)
-Click on "Start"
After that, it should boot and everything should be fine (and nothing was wiped, may I add). You may want to add recovery, too.
Like I told the OP where I posted that file. You should boot into recovery mode and do some wiping!
Everytime I flash a new Rom, my phone will not go past the galaxy note screen, I'm on bonsai 0.5 and it happens with every Rom I try no matter what recovery I use and with full wipes. Any help would be greatly appreciated...also when I flash those and get stuck it will let me reflash bonsai 0.5 and boot right up
robbievengence said:
Everytime I flash a new Rom, my phone will not go past the galaxy note screen, I'm on bonsai 0.5 and it happens with every Rom I try no matter what recovery I use and with full wipes. Any help would be greatly appreciated...also when I flash those and get stuck it will let me reflash bonsai 0.5 and boot right up
Click to expand...
Click to collapse
Try booting into download mode... then reboot when given the option. I had a similar issue, this worked for me.
emazzy72 said:
Try booting into download mode... then reboot when given the option. I had a similar issue, this worked for me.
Click to expand...
Click to collapse
I have actually tried that to no avail. Thanks tho. Still looking for what could cause this issue. It makes no sense. I've been flashing since the first Droid came out I've never experienced this.
robbievengence said:
I have actually tried that to no avail. Thanks tho. Still looking for what could cause this issue. It makes no sense. I've been flashing since the first Droid came out I've never experienced this.
Click to expand...
Click to collapse
Ok, from what I can tell, if you're on Bonsai v0.5, then you're still on MJ4. If you try to flash any Kit-Kat based ROM, it's not going to work. You need to go to the stock Kit-Kat bootloader and ROM before you can flash any KK-based custom ROM. I don't fully understand why that's the case, but it is.
I have previously written up instructions on how to do this, which I have copied-and-pasted below. The links should still work, although the files may have been updated to newer versions. They should still work.
Detailed instructions on upgrading from a MJ4 (Jellybean) to NAB (KitKat) Rom.
Downloaded all files required. I will provide a link to the files. For all ODIN file flashing, I had "Auto Reboot" and "F. Reset Time" checked.
Backed up all "important" files off of the internal memory to the MicroSD card. Copied the fre3 Rom file to the MicroSD Card.
Use ODIN 3.07 "PDA" to flash the MJ4 Stock TAR file (filename: N900PVPUBMJ4_N900PSPTBMJ4_N900PVPUBMJ4_HOME.tar.md5). Took 5-10 minutes.
Once phone reboots, allow a few minutes for things to get settled. Reboot into Download Mode.
Use ODIN 3.07 "PDA" to flash the NAB Stock TAR file (filename: N900PVPUCNAB_N900PSPTCNAB_N900PVPUCNAB_HOME.tar.md5). Took 5-10 minutes.
Once phone reboots, allow a few minutes for things to get settled. Reboot into Download Mode.
*Optional Step* Use ODIN 3.07 "Bootloader" to flash the NAB Engineered Bootloader TAR file (filename: nabfirmware.tar). Took 1 minute.
Once phone reboots, allow a few minutes for things to get settled. Reboot into Download Mode.
Use ODIN 3.07 "PDA" to flash the TWRP 2.7.0.0 TAR file (filename: openrecovery-twrp-2.7.0.0-hltespr-4.4.img.tar). Took 1-2 minutes.
Once phone reboots, allow a few minutes for things to get settled. Reboot into Recovery Mode.
Made a TWRP Backup of the Stock NAB Rom, set backup location to the MicroSD Card. Took 5-10 minutes.
Did an "Advanced" Wipe on TWRP. Checked all options except MicroSD Card.
Once done, go back to "wipe" menu in TWRP. Choose "Format Data" and had to type in "yes" to wipe.
Rebooted to Recovery. Do not try to install SuperSu, since you have no ROM loaded yet.
Install the ROM in TWRP.
Rebooted to ROM and allowed a few minutes for everything to settle down.
Rebooted ROM to make sure everything is running fine.
All-in-all, took only about 45 minutes, but with writing this down, I'd say it took a total of 1 hour. Not too shabby.
Click to expand...
Click to collapse
I hope this helps!
Edit:
Note: As far as I'm aware, once you go to a Kit-Kat based ROM, you will not be able to go back down to a JB ROM. I think some people were trying to figure out a way to do this, but I haven't heard if they've solved it.