Database Info

Rebooting problem while in recovery

So i started by downloading the new gingeritis 3d beta 5. I rebooted into recovery, wiped data, cache, and dalvik cache. installed the rom just fine. I rebooted the phone and it just kept showing the splash screen and going black then splash again. I did a battery pull and went to bootloader then to recovery. When i try to install a different rom or do a restore the phone reboots right in the middle of the install/restore.
What do you think the problem is. Can i flash a different rom from the bootloader? is the recovery bad?
Or as a last resort do I have to flash the "Custom upgrade PG05IMG_MR1_upgrade.zip" from the "root your thunderbolt" thread in the bootloader?
Thanks

Ianxcom said:
So i started by downloading the new gingeritis 3d beta 5. I rebooted into recovery, wiped data, cache, and dalvik cache. installed the rom just fine. I rebooted the phone and it just kept showing the splash screen and going black then splash again. I did a battery pull and went to bootloader then to recovery. When i try to install a different rom or do a restore the phone reboots right in the middle of the install/restore.
What do you think the problem is. Can i flash a different rom from the bootloader? is the recovery bad?
Or as a last resort do I have to flash the "Custom upgrade PG05IMG_MR1_upgrade.zip" from the "root your thunderbolt" thread in the bootloader?
Thanks
Click to expand...
Click to collapse
Try going back into recovery and wipe the three you've stated again, also "format /system" in mounts and storage. It could be something's not getting wiped properly and creating your problem. Then try installing a ROM. If that doesn't fix your problem then replace your recovery with the one I've attached. Copy it to the root of your SD card and install it from the bootloader. If your recovery is the problem that should fix it. Once you've done that try installing a standard ROM like one of the rooted OTA http://forum.xda-developers.com/showthread.php?t=1161251

Thanks for the help and the attachment. I will try it whe n i Get home since im at work. Whenever i try to wipe anything its like im on a time limit where it will restart ofter like 30 seconds no matter what i do.

Ianxcom said:
Thanks for the help and the attachment. I will try it whe n i Get home since im at work. Whenever i try to wipe anything its like im on a time limit where it will restart ofter like 30 seconds no matter what i do.
Click to expand...
Click to collapse
I just remembered that another person had the same problem as you and it turned out that the Micro SD card was the problem. It makes sense since your installing the ROM from the Micro SD card and then the card craps out causing the reboot. If you don't have another Micro SD card you could format the one you have and that might fix it. Of course you would lose any data on the card.

I tried the new recovery, a new sd card, still same problem. Is there something i can flash in bootloader? like the PG05IMG_MR1_Upgrade? or something else?

Ianxcom said:
I tried the new recovery, a new sd card, still same problem. Is there something i can flash in bootloader? like the PG05IMG_MR1_Upgrade? or something else?
Click to expand...
Click to collapse
You could download an RUU http://dougpiston.com/ThunderBolt/R..._NV_8k_1.41_9k_1.64_release_182727_signed.zip and rename it to PG05IMG.zip. That will do a factory restore from the bootloader. You would then need to root the phone again. It's possible the memory on your phone is damaged creating the reboots, Lets hope that's not the case.

Thanks! at least that worked.

Ianxcom said:
Thanks! at least that worked.
Click to expand...
Click to collapse
Awesome, glad you're up and running again. Remember to delete or rename the PG05IMG.zip on your SD card or next time you go into your bootloader it will try to install the restore RUU again. I've done that before.

[Q] Can't get PIT file in ODIN

I read teddy's faq in the dev forum and am trying to odin to stock. I'm on odin right now and already downloaded the pit file, but when I click pit to insert the file, I can't find the file. Or...odin can't find it (cause its not a .pit file?). anyway, whats goin on with this?
EDIT: nevermind, i'm an idiot. i got it.

first odin to stock - successful.
one problem, redownloaded rom manager and i can't get to the orange cwm recovery screen. forgot what i had to do and its not in teddy's noob faq. supwiddit?

did you remember this part ?
krylon360 said:
You will need to modify your stock recovery binary to be able to use CWM.
Kernel Devs can also compile CWM into their kernel by extracting the update.zip and building it into their initramfs.
To replace your stock recovery binary with the modified binary:
download this file
http://www.krylon360.com/file_host/sk4g/recovery.zip
Exatract and take the recovery binary file inside of it and use root explorer or adb push the file to /system/bin.
DO NOT delete the current one there, or rename any files.
Just overwrite it.
Click to expand...
Click to collapse

thanks ted, completely forgot. just did it but now i can't get to red cwm even after applying updates/using sdu's debugging trick/etc. im gonna try and flash anyway from orange cwm, cross your fingers

Jabrutal said:
thanks ted, completely forgot. just did it but now i can't get to red cwm even after applying updates/using sdu's debugging trick/etc. im gonna try and flash anyway from orange cwm, cross your fingers
Click to expand...
Click to collapse
Just check your mounts
Sent from my SGH-T839 using XDA App

ayoteddy said:
Just check your mounts
Sent from my SGH-T839 using XDA App
Click to expand...
Click to collapse
ugh, forgot that. anyway - flash was fine, but someone on the dev page told me to wipe dalvik cache after restoring data. i did that then rebooted, and the creepy GLaDos wannabe said something like "(something something) partition...system not found" and now shes shut up and i've been sitting at the samsung sk4g screen for like 5 minutes.
i remember when i first got a kernel then it took a long time to boot, but im not sure if its just doing that again or if its softbricked again. i'm also not sure if the softbrick is due wiping the dalvik cache before everything was installed or if its cause i didn't change my mounts?

Jabrutal said:
ugh, forgot that. anyway - flash was fine, but someone on the dev page told me to wipe dalvik cache after restoring data. i did that then rebooted, and the creepy GLaDos wannabe said something like "(something something) partition...system not found" and now shes shut up and i've been sitting at the samsung sk4g screen for like 5 minutes.
i remember when i first got a kernel then it took a long time to boot, but im not sure if its just doing that again or if its softbricked again. i'm also not sure if the softbrick is due wiping the dalvik cache before everything was installed or if its cause i didn't change my mounts?
Click to expand...
Click to collapse
likely because you didnt change your mounts!
when on the orange recovery it is usually on mount/system and you have to change to unmount/system
and when you flash let it boot up before restoring data and wiping dalvik cache etc..

i keep pwning myself... trying to wipe data and im getting this error
E:format_volume: make_extf4fs failed on dev/block/mmcblk0p2
and its stuck there.

Jabrutal said:
i keep pwning myself... trying to wipe data and im getting this error
E:format_volume: make_extf4fs failed on dev/block/mmcblk0p2
and its stuck there.
Click to expand...
Click to collapse
You have to odin with repartion checked. Then when installing the ROM, ALWAYS check your mounts if your in the orange recovery
Sent from my SGH-T839 using XDA App

I did have repartition checked when I odin'd. Should I odin again and start fresh or could it possibly be something else?

Jabrutal said:
I did have repartition checked when I odin'd. Should I odin again and start fresh or could it possibly be something else?
Click to expand...
Click to collapse
I'm sure the install would have went fine if you checked your mounts, its possible that since your mounts weren't correct that when Linda was trying to convert your partitions they got currupt somehow. So just start fresh, and don't forget the checking mounts. If you plan to restore data from a nandroid backup then wait til the ROM loads up, then reboot into recovery and wipe data and then restore your data. Wipe caches then reboot and your good
Sent from my SGH-T839 using XDA App

teddy, i odin'd to stock, repartitioned, and got everything up to orange cwm. went to wipe data and got the same /dev/block error. i think i need to use red cwm, can't figure out how to get there though...

Red CWM comes from the Bali kernel, as it includes the Voodoo options in that CWM. to get that, you just flash the Bali kernel.

sdu i flashed the kg2 bali kernel and got a softbrick on the samsung loading screen. odin'ing now, im thinking its cause i repartitioned when i odin'd. not gonna do that this time.
if you could suggest another way to get to red cwm thatd be awesome

that is the only way to get into Red CWM. Red CWM is the same as regular orange CWM, it just includes the voodoo tweaks. Which odin file are you restoring with?

sduvick said:
that is the only way to get into Red CWM. Red CWM is the same as regular orange CWM, it just includes the voodoo tweaks. Which odin file are you restoring with?
Click to expand...
Click to collapse
the kg2 that was in the noob faqs...i was able to odin with out re-partitioning earlier today, let me give it another shot.

i think im stuck somehow...i keep getting softbricks when trying to flash bali v1.2. i've tried with both partitioned and non partitioned odins (if that matters). i read in the bali thread to use the deodexed stock kg2 rom then flash bali, but i can't even flash the kg2 rom without getting into red cwm.
i'm starting to wonder how i did this in the first place...help me dev gods; i despise this slow, stock rom

Jabrutal said:
i think im stuck somehow...i keep getting softbricks when trying to flash bali v1.2. i've tried with both partitioned and non partitioned odins (if that matters). i read in the bali thread to use the deodexed stock kg2 rom then flash bali, but i can't even flash the kg2 rom without getting into red cwm.
i'm starting to wonder how i did this in the first place...help me dev gods; i despise this slow, stock rom
Click to expand...
Click to collapse
ODIN
then
download rom and put it on your sd card
download:
http://www.krylon360.com/file_host/sk4g/recovery.zip (This is the recovery.)
http://www.krylon360.com/file_host/sk4g/update.zip (this is the update)
Root Explorer can't share the link because it is a paid app but you can use astrid i believe or find root manager somewhere such as 4shared.
open the first file on your computer and take out the recovery file inside it and place it on the sd card.
place the second file on the sd card
and install your file manager.(root explorer or astrid etc..)
now open file manager scroll down and find sdcard,
now open it and find recovery and long press on it. hit copy. now hit the back button once.
now find system. open it.
find bin. open it.
hit on the top mount r/w
hit paste and overwrite the file.
next, power down the device and instead of powering on regularly, press volume down+volume up+ power button you should be in the recovery mode.
choose reinstall packages
now you should have an orange recovery
wipe data/factory reset
wipe cache
wipe dalvik cache (adavanced menu)
go to mounts and storage
if it says mount/system (4th one on list) then click it
if not leave it
install zip from sd card
go to mounts and storage
if it says mount/system (4th one on list) then click it
wipe dalvik cach
reboot system
this should take 5-10 mintues
you will here a robot girl (linda talking) then after that you should get the boot up logo and that should take a few minutes then you should be good!

EDIT: Pwned/ninja'd by tyler.
Ok, so partitioning in Odin only matters if you had the creepy converting voice (linda) talk to you in Red CWM. Don't worry about flashing bali 1.2, that's included in the stock deodexed rom I posted.
From Stock:
Enable USB Debugging in Settings > Applications > Development Settings.
You'll root using superoneclick, then use my script http://forum.xda-developers.com/showpost.php?p=15831175&postcount=124
to push the correct modded recovery and update.zip, and it will reboot you into the modded stock recovery (blue).
Press "Reinstall Packages" and that will take you to orange CWM.
In orange CWM, you can flash any rom that you'd like, it has the same flashing functions and abilities as the Red CWM.
Make sure your mounts read :
/System unmount
/data unmount
/cache unmount
BEFORE AND AFTER you flash, before you reboot.
you'll hear the creepy linda voice telling you it's converting your partitions, then you should be booted into the ROM you flashed.

Sdu and tyler,
I understand what you guys are saying and what I have to do, my Main problem is that in orange CWM, whenever I wipe data I get an error (stated somewhere in this thread) and the flash fails. The only solution I can think of is to get into red CWM (where I Never get that error), but I can't get into red without Bali, BUT I keep getting softbricked when I flash Bali!
The only other thing I can think of is to flash the deodexed stock KG2 rom to give me Bali, but I can't even do that cause I can't wipe data. Would it be safe for me to flash without wiping data?
EDIT: The error is
E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p2

[Q] I am Bricked....i think

Ok, So i rooted my T-mobile G2x 2.3.3 and there were difficulties when i flashed the Cyanogen 7mod. The Rom worked but the only default was i didnt get data. Like i couldnt even get Edge. The only way to use internet and stuff was through wifi. SO then i reflashed it thinking it was a bad flash. But when i reflash through rom manager it gives me the option to downoad with google apps. so i clicked that option. It downloaded fine but on the reboot it stayed stuck on the 2nd LG screen. Am i bricked or if anyone can help id appreciate it alot.

U can't do it via rom manager. U have to flash recovery using nv flash, then u can try to flash custom rom. Remeber to wipe data and format system before flashing any rom.
U r not bricked yet
Check here to nv flash the cwm
http://forum.xda-developers.com/showthread.php?p=13330067
Sent from my LG-P999 using xda premium

Did you flash CWM via NV Flash. If not, do that. Then boot into recovery by holding down the power + volume down keys until you get the second boot logo. Then wipe the dalvik cache and the regular cache. That is usually why a phone refuses to boot.
Also, if your phone turns on it is not bricked. Bricked means when you press the power button nothing happens at all. You can be soft-bricked like you are, but it can be easily fixed. Nothing to panic about.

I did all of that im sorry if i gave you info wrong. Like i cant do anything it turns on but goes to the first LG screen then goes to the new LG screen with the blue streaks and it stays there. Then when i try to go into CWR it shows the LG with a blue and black loading bar below then shows as if its loading something then it just goes back to the blue LG screen and im stuck there.

iSpooNz said:
I did all of that im sorry if i gave you info wrong. Like i cant do anything it turns on but goes to the first LG screen then goes to the new LG screen with the blue streaks and it stays there. Then when i try to go into CWR it shows the LG with a blue and black loading bar below then shows as if its loading something then it just goes back to the blue LG screen and im stuck there.
Click to expand...
Click to collapse
You have stock recovery on the recovery partition, not CWM. You MUST flash CWM onto the physical recovery partition using NVFlash with the One Click flasher. You used Rom Manager and that doesn't install CWM onto the recovery partition. Once you have CWM properly installed you can enter recovery and revive your phone.

jboxer said:
You have stock recovery on the recovery partition, not CWM. You MUST flash CWM onto the physical recovery partition using NVFlash with the One Click flasher. You used Rom Manager and that doesn't install CWM onto the recovery partition. Once you have CWM properly installed you can enter recovery and revive your phone.
Click to expand...
Click to collapse
Ok so from CWM do i wipe everything?

jboxer said:
You have stock recovery on the recovery partition, not CWM. You MUST flash CWM onto the physical recovery partition using NVFlash with the One Click flasher. You used Rom Manager and that doesn't install CWM onto the recovery partition. Once you have CWM properly installed you can enter recovery and revive your phone.
Click to expand...
Click to collapse
@OP, this is is correct. Use tga gunmann's nvflash tool from the development section. The process is super easy. Just make sure to follow his instructions closely. Just fyi, most people get errors during the nvflash process because they don't install the apx drivers appropriately, so take your time and read the instructions carefully.

iSpooNz said:
Ok so from CWM do i wipe everything?
Click to expand...
Click to collapse
Start off by wiping cache and then go to Advanced and wipe dalvik cache. If you still can't boot after that then try a full factory reset.
Just remember the first boot after wiping dalvik cache can take several minutes as android rebuilds the dalvik cache. All subsequent reboots will be MUCH faster.

phburks said:
Start off by wiping cache and then go to Advanced and wipe dalvik cache. If you still can't boot after that then try a full factory reset.
Just remember the first boot after wiping dalvik cache can take several minutes as android rebuilds the dalvik cache. All subsequent reboots will be MUCH faster.
Click to expand...
Click to collapse
Ok so i ended up having to do a factory reset yet im still getting the same results. Im still stuck on the 2nd lg screen when booting up

iSpooNz said:
Ok so i ended up having to do a factory reset yet im still getting the same results. Im still stuck on the 2nd lg screen when booting up
Click to expand...
Click to collapse
Did you do as phburks said and go into advanced and wipe the Dalvik Cache. Most issues of not booting are related to the Dalvik Cache not being wiped after flashing a new rom. That is essential to getting your phone to boot again. A factory reset DOES NOT clear the Dalvik Cache.

iSpooNz said:
Ok so i ended up having to do a factory reset yet im still getting the same results. Im still stuck on the 2nd lg screen when booting up
Click to expand...
Click to collapse
Boot back into cwm, go to Mounts and Storage, format /system and then reflash your rom.

phburks said:
Boot back into cwm, go to Mounts and Storage, format /system and then reflash your rom.
Click to expand...
Click to collapse
Ok ill try that.
jboxer said:
Did you do as phburks said and go into advanced and wipe the Dalvik Cache. Most issues of not booting are related to the Dalvik Cache not being wiped after flashing a new rom. That is essential to getting your phone to boot again. A factory reset DOES NOT clear the Dalvik Cache.
Click to expand...
Click to collapse
Yea i wiped Dalvik cahce and the same result came up. So i factory resetted and same result. So im going to try what phburks said and see what happens.

Im still stuck in the second LG screen :/

iSpooNz said:
Im still stuck in the second LG screen :/
Click to expand...
Click to collapse
Could be a bad download. I'd try downloading again. Use your computer to download again and save it to your microsd card. Then reinsert the sdcard, boot back into cwm and try again.

phburks said:
Could be a bad download. I'd try downloading again. Use your computer to download again and save it to your microsd card. Then reinsert the sdcard, boot back into cwm and try again.
Click to expand...
Click to collapse
download the rom right?

iSpooNz said:
download the rom right?
Click to expand...
Click to collapse
Yea the rom. Is it cm7 that you're wanting to flash?

phburks said:
Yea the rom. Is it cm7 that you're wanting to flash?
Click to expand...
Click to collapse
The reason I ask is that with cm7 you have to flash 2 separate zip files. First you flash the actual cm7 zip which installs the rom and then you flash the gapps zip which installs the Google apps (market, gmail, etc). Make sure you have both on your sdcard and then flash the rom first and gapps second.

phburks said:
The reason I ask is that with cm7 you have to flash 2 separate zip files. First you flash the actual cm7 zip which installs the rom and then you flash the gapps zip which installs the Google apps (market, gmail, etc). Make sure you have both on your sdcard and then flash the rom first and gapps second.
Click to expand...
Click to collapse
Im glad you brought that up because when i first flashed Cyanogen i did also flash gapps but after i flashed gapps thats when i wouldnt get data. Do you know the reason for this? or was it could have been another bad flash?

iSpooNz said:
Im glad you brought that up because when i first flashed Cyanogen i did also flash gapps but after i flashed gapps thats when i wouldnt get data. Do you know the reason for this? or was it could have been another bad flash?
Click to expand...
Click to collapse
Not sure. I'd just play it safe, re-download both, wipe data, and reflash both. Sometimes its hard to determine which step went wrong and its best and quicker to just start with a clean slate and redo everything.

I wont be able to post for a while so good luck.

MikRom Bootlooping on evo shift - HELP!!

This just started yesterday and i cant stop it. My phone reboots and says that memory is nearly full, then goes into a bootloop. I cant stop it long enough to back up texts, phone contacts and call log which is REALLY important; is there a way to back that up through recovery?
i'm really desperate here!
Edit: I can get the phone working through a format, but i need to be able to get contacts and sms backed up

Alternitavely, is there a way to run a clockword mod backup on an android emulator on my comp, so i can back up my important stuff?

what you should try doing is putting your sd card directly into your computer and delete stuff you don't need to get back so memory and then once you do that out it back into your phone

i cleared up the memory, internal and external. the stupid ROM is still broken

if its just the rom go to a different one and redownload mikrom later to make sure nothing happened in the initial download

If you haven't already, try removing some apps through adb, then reflash the ROM only wiping dalvik and cache. You shouldn't lose any of your text, call logs or contacts if you don't wipe data.
Sent from my PG06100 using Tapatalk

From The Hacker Manifesto:
I made a discovery today. I found a computer. Wait a second, this is cool. It does what I want it to. If it makes a mistake, it's because I screwed it up. Not because it doesn't like me... Or feels threatened by me.. Or thinks I'm a smart ass.. Or doesn't like teaching and shouldn't be here...
Click to expand...
Click to collapse
I love it sooooo the rom isnt stupid, the team of developers supporting it are amazing and you should setup adb and get a logcat, also you should nandroid before you flash so in case it goes wrong you can flash back, like insurance but you actually get something from this without paying..
if you did nandroid boot into bootloader and select recovery (hold volume down and power on use volume button to highlight recovery and power button to select)

I'm not sure if mikrom wipes or not but there's always that advanced restore option in cwm recovery flash rom, restore data and sd-ext if you have a ext partition with important data on it.

crump84 said:
If you haven't already, try removing some apps through adb, then reflash the ROM only wiping dalvik and cache. You shouldn't lose any of your text, call logs or contacts if you don't wipe data.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
I managed to get some apps removed, its no longer giving me the memory-full error, but its still bootlooping a minute or so after loading. going to try the cache and davlik wipes, then a another install....
JKILO said:
From The Hacker Manifesto:
Click to expand...
Click to collapse
thanks I always do a nandroid backup before doing a format; doesnt help. I can load the clean rom just fine, but when i restore, it goes into bootloop again....
sparksco said:
I'm not sure if mikrom wipes or not but there's always that advanced restore option in cwm recovery flash rom, restore data and sd-ext if you have a ext partition with important data on it.
Click to expand...
Click to collapse
ok, ill try this.
Also, how do i set up an sd-ext to automatically backup texts and call history etc to it?

crump84 said:
If you haven't already, try removing some apps through adb, then reflash the ROM only wiping dalvik and cache. You shouldn't lose any of your text, call logs or contacts if you don't wipe data.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
did not work - goes back to bootloop. how do i install ADB?

Jedman67 said:
did not work - goes back to bootloop. how do i install ADB?
Click to expand...
Click to collapse
http://developer.android.com/sdk/index.html
Beginner's Guide to Installing the SDK and Getting Started with ADB
If nothing else, like Jkilo said, provide a logcat and maybe someone could take a look.

Did you ever get this fixed?
The usual way of fixing this is formatting /system, wiping dalvik, wiping cache, and reflashing the rom.

VICODAN said:
Did you ever get this fixed?
The usual way of fixing this is formatting /system, wiping dalvik, wiping cache, and reflashing the rom.
Click to expand...
Click to collapse
no. what i did was a backup, complete factory reset, wipe, dalvik wipe, etc - several times each, including a full on sd-card format, which took me hours to reload everything back on - and then reflashed MikShift. It worked fine for about a day, but then it started to go into bootloops again, so i again did a backup, full reset and all wipes, and restored data only to the new flash of mikshift. Once again its bootlooping.
LOG: ive been off the forums for several months, how do i get this log?
IMAGE: When i go into bootloader and enter recovery, it shows me a message in green text
"PG06diag.zip
No image!
PG06diag.nbh
No image or wrong image!
PG06img.zip
No image!
PG06img.nbh
No image or wrong image!"
At this point, im ready to RUU back to factory unrooted, so i can take it back to sprint and get it replaced.
I should not need to reflash the ROM every single day.

Jedman67 said:
no. what i did was a backup, complete factory reset, wipe, dalvik wipe, etc - several times each, including a full on sd-card format, which took me hours to reload everything back on - and then reflashed MikShift. It worked fine for about a day, but then it started to go into bootloops again, so i again did a backup, full reset and all wipes, and restored data only to the new flash of mikshift. Once again its bootlooping.
LOG: ive been off the forums for several months, how do i get this log?
IMAGE: When i go into bootloader and enter recovery, it shows me a message in green text
"PG06diag.zip
No image!
PG06diag.nbh
No image or wrong image!
PG06img.zip
No image!
PG06img.nbh
No image or wrong image!"
At this point, im ready to RUU back to factory unrooted, so i can take it back to sprint and get it replaced.
I should not need to reflash the ROM every single day.
Click to expand...
Click to collapse
OK
0) Run a backup with titanium backup.
1) First of all go to clockwork -> mounts storage -> FORMAT /SYSTEM.
2) Wipe /cache, wipe dalvik, wipe/data, factory reset, repartition sd card.
3) Redownload the rom or try a proven ROM like UKE or CM7-255. If AOSP MAKE SURE TO FLASH GAPPS.
NO NEED TO RUU.
4) DO NOT RESTORE YOUR BACK UP. See how stable the phone runs.
5) If the phone is still unstable try a different battery.
6) Do not flash a custom kernel.

i formatted my backup SD card, and copied the essential data to it, and i have it running in the phone now. it seems to be running fine so far, i suspect the other SD may have gotten corrupt or physically damaged

Vic: every single time this has happened, i first went to clear the data and dalvik caches and ran a factory reset, all through the CWM recovery interface. Then when i reinstall mikshift, i restore the data using advanced restore, wait 24-48 hours, bootloops start all over again.
after two days of running on the new sd card, i start getting bootloops again. it must be a problem with the phone or the OS, but at this point i dont care anymore.
Is there a guide to RUU back to stock unroot? this phone is going back to sprint by weeks end, period.
thanks for the help folks.

Jedman67 said:
Vic: every single time this has happened, i first went to clear the data and dalvik caches and ran a factory reset, all through the CWM recovery interface. Then when i reinstall mikshift, i restore the data using advanced restore, wait 24-48 hours, bootloops start all over again.
after two days of running on the new sd card, i start getting bootloops again. it must be a problem with the phone or the OS, but at this point i dont care anymore.
Is there a guide to RUU back to stock unroot? this phone is going back to sprint by weeks end, period.
thanks for the help folks.
Click to expand...
Click to collapse
Here's the 2.2 RUU zip http://forum.xda-developers.com/showthread.php?t=971550 Just put it on the root of sd, boot in hboot and let it do its thing.
Or you can run the RUU exe, just download and run from your pc. It's pretty self explanatory http://forum.xda-developers.com/showthread.php?t=1335068

Jedman67 said:
Vic: every single time this has happened, i first went to clear the data and dalvik caches and ran a factory reset, all through the CWM recovery interface. Then when i reinstall mikshift, i restore the data using advanced restore, wait 24-48 hours, bootloops start all over again.
after two days of running on the new sd card, i start getting bootloops again. it must be a problem with the phone or the OS, but at this point i dont care anymore.
Is there a guide to RUU back to stock unroot? this phone is going back to sprint by weeks end, period.
thanks for the help folks.
Click to expand...
Click to collapse
The problem is you didn't format /system.

Redownload the Rom. Then follow THIS GUIDE when you flash.

VICODAN said:
The problem is you didn't format /system.
Click to expand...
Click to collapse
Exactly 10 char
---------- Post added at 12:34 AM ---------- Previous post was at 12:31 AM ----------
prboy1969 said:
Redownload the Rom. Then follow THIS GUIDE when you flash.
Click to expand...
Click to collapse
Yeah that guide is great for flashing sense roms since "most" sense roms don't format/wipe the system partition correctly. Aosp roms you just do a data facotry wipe and everything installs just fine

[Q] Bricked P5100? Help please!

My P5100 had CM10 nightly on it and was running fine until I upgraded to the latest version of CM10 after wiping the cache & Dalvik cache. After the upgrade I couldn't get Google Play to run even after wiping its data and fixing permissions so I tried to do a CWM restore. Unfortunately there was a fault restoring the Data partition and now my tablet is stuck at the animated bootscreen. If I long-press the power button it powers off but immediately restarts. There is no way to start in in recovery or flash mode. I've plugged it into my PC and the Samsung Android ADB interface is showing but the other references to the tablet all have a yellow triangle in Device Manager. I'm hoping some clever person can help me rescue the tablet with ADB. Thanks!

dwl99 said:
My P5100 had CM10 nightly on it and was running fine until I upgraded to the latest version of CM10 after wiping the cache & Dalvik cache. After the upgrade I couldn't get Google Play to run even after wiping its data and fixing permissions so I tried to do a CWM restore. Unfortunately there was a fault restoring the Data partition and now my tablet is stuck at the animated bootscreen. If I long-press the power button it powers off but immediately restarts. There is no way to start in in recovery or flash mode. I've plugged it into my PC and the Samsung Android ADB interface is showing but the other references to the tablet all have a yellow triangle in Device Manager. I'm hoping some clever person can help me rescue the tablet with ADB. Thanks!
Click to expand...
Click to collapse
IF CWM is not working use Odin to flash CWM again then use CWM to flash CM10,
You may need to do a factory reset (full wipe) from CWM.
If all else fails use Odin to flash stock JB ROM

DigitalMD said:
IF CWM is not working use Odin to flash CWM again then use CWM to flash CM10,
You may need to do a factory reset (full wipe) from CWM.
If all else fails use Odin to flash stock JB ROM
Click to expand...
Click to collapse
Thanks but Odin cannot see the tablet to re-flash the recovery.

Downlods mode
Then flash new firmware

sembre said:
Downlods mode
Then flash new firmware
Click to expand...
Click to collapse
That's the problem - I cannot access download mode
UPDATE - it just started in download mode! I can manage from here!!

Just for the record you can install adb on the pc and run the command 'adb reboot recovery'. This will force the tablet to reboot in recovery mode.
Sent from my GT-I9300 using xda app-developers app

Jeez, this has taken up most of the day to fix. I came across many problems I have not previously experienced:
1. When the tablet was stuck at the boot animation and I tried to turn it off by long-pressing the power button it immediately restarted. The only way I could get it to turn off was by long-pressing the power button whilst it was connected to my PC.
2. Flashing the stock ROM with Odin appeared to complete successfully but it would never fully boot, it always got stuck at the black & white Samsung screen. Same problems turning it off as above.
3. Flashing CWM with Odin caused the tablet to reboot into the stock ROM which would not load, in the end I had to untick the "reboot" button in Odin, power it off then manually restart with the Vol- & power buttons.
4. The only way I could get a bootable ROM was by flashing CM10 with CWM. I tried to restore 2 previous CWM backups but on each occasion there was an error restoring the Data partition and I got stuck at the scenario at (1). The backups were made to the external SD card with CWM Touch - is the Touch version unreliable?
I would be really interested if anyone could shed any light on any of this stuff!

For how long did you let it install during the first reboot? It happened to me too, and it took about 10 minutes, maybe even more...
Also, did you try in the "Mount and storage" cwm menu the options "format system", "format data", "format cache" and "format preload" options, prior to re-flashing a ROM? I have read somewhere that for a clean install it's better to do this, as it really clears everything that could mess up the system between two different bases ROMs (like CM and stock).
What I do everytime is using in CWM these 4 "format" options, plus "wipe" system, cache and dalvik, then immediately after this I flash with cwm the new "zip" copied on the card. Then the first reboot is much longer than usual, as at this stage it installs the files, rebuild the dalvik cache etc.
Good luck
dwl99 said:
2. Flashing the stock ROM with Odin appeared to complete successfully but it would never fully boot, it always got stuck at the black & white Samsung screen. Same problems turning it off as above.
Click to expand...
Click to collapse

I think I gave it a good 20 mins to boot. When I got up this morning there was an error message saying that there was no room to install any more apps even though I had very few installed. Settings -> Storage would not calculate the space available so I figured that the partitions had become corrupted. I did the step by step format you described and reflashed & it all seems to be OK now.