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
Related
Just bricked my defy last nigh accidentally then flased a full nordic 2.2.2 via rsd lite everything went fibe BUT when i was going to install some roms via nandroid backup I get this errors.
tried flashing a 2.1 eclair but it wont boot up so I reflashed the 2.2.2 nordic for about 10x already
here's what cwm says when restoring
ClockworkMod Recovery v2.5.1.8
Checking MD5 sums...
Restoring System...
Restoring Data...
Restoring ,Android_secure...
Restoring Cache...
Restoring sd-ext
no app2sd partiton found. Skipping format of /sd-ext.
E:Can't mount /dev/block/mmcblk0p2 (file exists)
Can't mount /sd-ext/!
and more when on the stock recovery is says something that it can't mount etc2
please help me out guys this is really important
ive read through some forums and found that I need to repartition.how?what's the easiest way?
tried wiping dalvik cache but it fails too.
cant download from market too.
this sucks.
its my first android phone and now im messed up!!
I will really apreciate your help please
EDIT:now Im using MIUI but still unable to mount sd-ext
and these few errors
E:Can't mount /dev/block/mmcblk0p2
(File exists)
E:Can't mount CACHE:recovery/command
and log
what do O do pls?
sent from my MB525 using XDA Premium App
In stock recovery do factory reset wipe cache and reboot and flash ur SBF....
Sent from my MB525 using XDA App
bricked?
WTH happened?
are u able to go stock recovery? did you do a data & cache wipe?
it should all do it.after u can flash a different & clean SBF.
also try to format sdcard as well..dont bother losing the nand backup...
then just use rsd lite to reflash a different leaked/official 2.2 froyo
hi tnx all for ur help.
yes i am able to go stock recovery and even cwm recovery via 2init 1.4 its a stock clean froyo
im getting this error on stock recovery
it says
E:un able to read cahe/recovery/command and starter
anyone suggestion?
wiping dalvik cant be done due to errors posted above
Sent from my MB525 using XDA Premium App
After wipe and reset just flash SBF...Error is not problem according to me....
Sent from my toilet using my Motorola DEFY
Ok if you heve stock and second init recovery then nothing is lost. What CWM- says is totally OK. And stock recovery always unable to read /cache/recovery/command.
What firmware were you on when installed second init? You sould try to restore the nandroid of that firmware with CWM.
If you wiped your phone with stock recovery then CWM will not work then you should flash your stock sbf with RSD lite.
ok will try when I get back home and will post the results
note: im on cm7 beta 6 b4 this happened.
Sent from my MB525 using XDA Premium App
You have to go back to Nordic, via RSD Lite .
Flash the full rom, since you already flashed the whole sbf one time, you won't be worry about downgradability, it's lost.
Then wipe again, at the end the cwm should work as expected.
Just as a note after i flashed the full Nordic sbf i got stuck so i went into stock recovery and wiped data etc. This let me boot the nordic rom. Then just need to root, install 2nd init and reinstall cm7
yay! now im on cm7 and will check if the errors are still there
and btw how do I go back to 2.2.2 stock in order to install ephunord rom
edit:
custom recovery says
E:unable to read cahe/recovery/command
E:unable to read cahe/recovery/starter
then when wiping dalvik cache on cwm
when pressing wipe dalvik cache
E:unknown volume for path [/sd-ext]
then when I confirm it it says
dalvik cache wiped.
is it normal?
can't install the google apps package too downloaded many times but it always end up on bad installation or something
wew im so stressed with my phone right now
gonemad02 said:
yay! now im on cm7 and will check if the errors are still there
and btw how do I go back to 2.2.2 stock in order to install ephunord rom
edit:
custom recovery says
E:unable to read cahe/recovery/command
E:unable to read cahe/recovery/starter
then when wiping dalvik cache on cwm
when pressing wipe dalvik cache
E:unknown volume for path [/sd-ext]
then when I confirm it it says
dalvik cache wiped.
is it normal?
can't install the google apps package too downloaded many times but it always end up on bad installation or something
wew im so stressed with my phone right now
Click to expand...
Click to collapse
yah that appears on mine too,those unable to read things:i reformat my sdcard clean & i treat it normal since i've been flashing & experimenting a lot,& i dont do a backup of any of my nands i only back up my apps.
since IMO i will never go back to eclair for any warranty,only forward to the developments..
i trust my defy just like i trust the resources i get here in the forums ;D
my thing is i cant do a restore on nands. anyway what's the format of your sd card?is it fat32?
gonemad02 said:
my thing is i cant do a restore on nands. anyway what's the format of your sd card?is it fat32?
Click to expand...
Click to collapse
Have you tried to format your sd card with your phone?(not from pc)
yes tried it a couple of times already
anyone knows how do I wipe dalvik cache using adb?
these are the remaining errors I still have
E:Can't mount /dev/block/mmcblk0p2
(File exists)
E:Can't mount CACHE:recovery/command
Hi. I flashed sbf JRDNEM_U3_3.4.3-11. But my phone is stuck on animated bootlogo (with "blur"). I flashed back my 100% previously worked sbf - U3_3.4.2_155-002. And it stuck on animated "android". When i try to load recovery - green android robot with "!" and nothing. What i do wrong?
bomgavs said:
Hi. I flashed sbf JRDNEM_U3_3.4.3-11. But my phone is stuck on animated bootlogo (with "blur"). I flashed back my 100% previously worked sbf - U3_3.4.2_155-002. And it stuck on animated "android". When i try to load recovery - green android robot with "!" and nothing. What i do wrong?
Click to expand...
Click to collapse
try wiping cache factory and dalvik cache
gonemad02 said:
my thing is i cant do a restore on nands. anyway what's the format of your sd card?is it fat32?
Click to expand...
Click to collapse
most probably yes,my card would be on fat32 on default since its 4gb.
unless i force format it w/ fat16 from my pc.but it shouldnt be an issue.
well i get those kinds of errors too.i cant flash the gapps zip for the cm7
i even get failed write to SD whenever i download an app from the market or an unknown file out of the market.
bomgavs said:
Hi. I flashed sbf JRDNEM_U3_3.4.3-11. But my phone is stuck on animated bootlogo (with "blur"). I flashed back my 100% previously worked sbf - U3_3.4.2_155-002. And it stuck on animated "android". When i try to load recovery - green android robot with "!" and nothing. What i do wrong?
Click to expand...
Click to collapse
when u see the green robot:
press the volume up & down together to enter stock recovery.
use the volume up/down & power button to select.
tap ok button on the left corner to continue the process of wipe.
I see. we do really have the same issue.
Im now on MIUI.shame...can't even try roms via nandroid backups.
will parted work to fix/format my cache including the sd-ext one?
I cant mount it no matter what I do
I believe parted will work.
and whenever I try to root using super one click
it gives some error regarding cant mount etc2 file exists
but in the ened it's successful.
Sent from my MB525 using XDA Premium App
Errors in our sd card
Well yah.thats tthe reason why im back now on stock blur french..everything back to normal & ready to flash again...i dont know,maybe the card gets corrupted whenever im on a custom rom...
Ok so how's miui?any luck on that one? No time to flash now busy w/ my baby.... Im still longing for the cm7,maybe the nxt rel will be complete.
I have a updated g2x (gingerbread via Lg updater) installed NVflasher was able to boot into recovery performed a nandroid back up did a full wipe and was going to flash Xbroarders rom until i relized i put it on my internal instead of external so i then tried to flash my back up and got "no file found"did a reboot and all im getting is a black screen wit flashing keys. plz help
Try reflashing Clockwork Mod Recovery.
Sent from my LG G2X using XDA Premium for Android
Do that, and if you have the means, try to check out the external sd on some other device to see what's going on. I'd start with pulling the battery for a bit and try flashing the backup again.
Also, correct me if I'm wrong but if you didn't flash anything because of misfiling xboarder's rom, there was no reason to use the backup in the first place.
dachinaman said:
I have a updated g2x (gingerbread via Lg updater) installed NVflasher was able to boot into recovery performed a nandroid back up did a full wipe and was going to flash Xbroarders rom until i realized i put it on my internal instead of external so i then tried to flash my back up and got "no file found"did a reboot and all im getting is a black screen wit flashing keys. plz help
Click to expand...
Click to collapse
Where did you put your nandroid - internal or external SD? They would have been determined by the recovery option you chose - Internal or External SD. Your stock ROM would download the Xboarder ROM to internal in any case, but your nandroid location depends on the choice above.
Since you did a total wipe, you do not have a ROM installed, so you will not be able to boot up, but you DO NOT have a brick.
You could flash the Recovery again with the Oneclick Recovery tool and choose internal, and then you could flash the Xboarder ROM. After that, see if you can find your backup (in the clockworkmod folder).
gaww said:
Since you did a total wipe, you do not have a ROM installed, so you will not be able to boot up, but you DO NOT have a brick.
Click to expand...
Click to collapse
I didn't know that a wipe from cwm clears out the rom. I only ever wiped before flashing something else so I assumed it was more like a factory reset.
heysharon said:
I didn't know that a wipe from cwm clears out the rom. I only ever wiped before flashing something else so I assumed it was more like a factory reset.
Click to expand...
Click to collapse
As far as I know, the wipe data/factory reset is exactly that.
There's also a wipe system function, which wipes the entire ROM also. It seems he did that also.
As for fixing the phone, what gaww said haha. If xboarder's mod isn't there, then in recovery while the phone is plugged in, mount the sd card, and put a rom on there using windows explorer or whatever, then disconnect and you should be able to flash it.
dachinaman said:
I have a updated g2x (gingerbread via Lg updater) installed NVflasher was able to boot into recovery performed a nandroid back up did a full wipe and was going to flash Xbroarders rom until i relized i put it on my internal instead of external so i then tried to flash my back up and got "no file found"did a reboot and all im getting is a black screen wit flashing keys. plz help
Click to expand...
Click to collapse
Boot into recovery, go down to mount, and mount usb. Then find the file on your internal sd and move it over to the external sdcard. I have had to do that a few times when I forgot to move the file.
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.
Hi All,
I think my phone may be done for, but I wanted to ask all of you first. It all started when I booted up my phone, and it went into Stock GB and before I could do anything at all, everything started force closing (i.e. twlauncher, clock, 10 other things etc.) basically the entire OS and the phone would reboot and then again same problem. Sometimes it would get stuck on the ATT "Rethink Possible" screen for a while, and then immediately it would get to the Your phone is locked screen, and everything would be force closing again. I booted up into recovery mode and wiped user data and cache. Nothing. So then I decided to re load the firmware using jscott's completely stock rom. I used ODIN with PIT, PDA, and Phone and let it do its thing. PASS. Once again, phone did the SAME thing over and over. I then thought let me try either a custom ROM or rooted stock GB. I used jscott's "I997UCLB3-CWM-root-deodex.rar" and used ODIN. PASS. Cleared user data, cache, dalvik. Tried to boot. Still SAME problem. Then I thought maybe I could load ICS Custom ROM and fix the issue (a stretch I know, but no idea what else to do). So, I used ADB to push "Infinitum" ICS ROM to the /sdcard Booted to CWM Recovery and installed the zip. The phone rebooted with the blue android logo and then once again, got to the welcome screen and everything started force closing and the phone rebooted.
Am I just out of luck? Any advise would be greatly appreciated. Thanks in advance.
SuperG03
SuperG03 said:
Hi All,
I think my phone may be done for, but I wanted to ask all of you first. It all started when I booted up my phone, and it went into Stock GB and before I could do anything at all, everything started force closing (i.e. twlauncher, clock, 10 other things etc.) basically the entire OS and the phone would reboot and then again same problem. Sometimes it would get stuck on the ATT "Rethink Possible" screen for a while, and then immediately it would get to the Your phone is locked screen, and everything would be force closing again. I booted up into recovery mode and wiped user data and cache. Nothing. So then I decided to re load the firmware using jscott's completely stock rom. I used ODIN with PIT, PDA, and Phone and let it do its thing. PASS. Once again, phone did the SAME thing over and over. I then thought let me try either a custom ROM or rooted stock GB. I used jscott's "I997UCLB3-CWM-root-deodex.rar" and used ODIN. PASS. Cleared user data, cache, dalvik. Tried to boot. Still SAME problem. Then I thought maybe I could load ICS Custom ROM and fix the issue (a stretch I know, but no idea what else to do). So, I used ADB to push "Infinitum" ICS ROM to the /sdcard Booted to CWM Recovery and installed the zip. The phone rebooted with the blue android logo and then once again, got to the welcome screen and everything started force closing and the phone rebooted.
Am I just out of luck? Any advise would be greatly appreciated. Thanks in advance.
SuperG03
Click to expand...
Click to collapse
Have you tried qkster's hiemdall back to stock? http://forum.xda-developers.com/showthread.php?t=1524081
If it doesnt work, try using different computer/usb cable/usb slot
ibCurlyFry said:
Have you tried qkster's hiemdall back to stock? http://forum.xda-developers.com/showthread.php?t=1524081
If it doesnt work, try using different computer/usb cable/usb slot
Click to expand...
Click to collapse
+1
ibCurlyFry said:
Have you tried qkster's hiemdall back to stock? http://forum.xda-developers.com/showthread.php?t=1524081
If it doesnt work, try using different computer/usb cable/usb slot
Click to expand...
Click to collapse
Ok, I did that as well. Same thing happens. Everything completes successfully on the Heimdall 1 click, but when it boots, same problem...
I tried multiple times with multiple computers.
I also tried GTG Unbrick complete stock as well just in case. Same thing...
Anyone else know what I can try / do?
Thanks!
SuperG03
clean your power button?
qkster said:
clean your power button?
Click to expand...
Click to collapse
LOL! Guess we are running out of options...
My situation is the weirdest thing and makes no sense and I hate things that don't make sense...
SuperG03
I would suggest formatting EVERYTHING except the boot partition on the phone and try again to stock. Something is screwed up and is causing the force closes. If you do that and it STILL does this, then there is a hardware failure that is most likely causing the issue.
MrBooMY said:
I would suggest formatting EVERYTHING except the boot partition on the phone and try again to stock. Something is screwed up and is causing the force closes. If you do that and it STILL does this, then there is a hardware failure that is most likely causing the issue.
Click to expand...
Click to collapse
Sounds like a plan. How would I format absolutely everything?
SuperG03
SuperG03 said:
Sounds like a plan. How would I format absolutely everything?
SuperG03
Click to expand...
Click to collapse
Can you get into recovery mode at all? Forgot to mention that.
MrBooMY said:
Can you get into recovery mode at all? Forgot to mention that.
Click to expand...
Click to collapse
Yes, I can get into recovery or download mode.
When I ODIN or Heimdall into the stock, I have 3e recovery. If / When I add CWM entropy kernel then I have CWM red recovery mode.
I have tried wipe user data, cache, dalvik cache, etc. to no avail.
SuperG03
There should be a mounts and storage menu where you can format stuff. Format EVERYTHING except the BOOT partition. IF you format boot you are screwed! Also if you have IMPORTANT info on the external or internal SD card back that up first!!!!!
MrBooMY said:
There should be a mounts and storage menu where you can format stuff. Format EVERYTHING except the BOOT partition. IF you format boot you are screwed! Also if you have IMPORTANT info on the external or internal SD card back that up first!!!!!
Click to expand...
Click to collapse
Oh yes, I have done that several times already. I have mounted everything and then proceeded to format them all. It does keep telling me that sd-ext is not found... (not sure if that is normal)
So to recap, I have tried installing / flashing with the following:
ODIN GTG UCKD5: http://forum.xda-developers.com/showthread.php?t=1116251 Flash PASS - same problem exists
ODIN JScott UCLB3: http://forum.xda-developers.com/showthread.php?t=1705260 Flash PASS - same problem exists
Heimdall qkster UCLB3: http://forum.xda-developers.com/showthread.php?t=1524081 Flash Successful - same problem exists
ODIN JScott UCLB3 Rooted CWM (Entropy's Daily Driver): http://forum.xda-developers.com/showthread.php?t=1613523 Flash PASS - same problem exists
CWM Install ROM Infinity ICS - Successful Install - same problem exists
CWM Install ROM SlimBean (Jelly Bean) - Successful Install - same problem exits
Problem occurs no matter how many data/factory reset wipes I do. As soon as OS boots, everything immediately starts force closing (I can see the welcome screen, but can't get to it with all the force closes on top).
Example of some of the force closes: "android.process.acore has stopped" & "com.google.process.gapps has stopped", etc.
Ran EMMC Brick Find: http://forum.xda-developers.com/showthread.php?t=1823918 and it went through each MB up to 16 GB and said OK.
I think that covers it all.
Anymore ideas on what to try?
If it is hardware, what could it be?
SuperG03
I'm guessing you did let it do the bootloaders on the flash? Other than that it sounds like a serious hardware issue like a failing processor.
SuperG03 said:
Oh yes, I have done that several times already. I have mounted everything and then proceeded to format them all. It does keep telling me that sd-ext is not found... (not sure if that is normal)
So to recap, I have tried installing / flashing with the following:
ODIN GTG UCKD5: http://forum.xda-developers.com/showthread.php?t=1116251 Flash PASS - same problem exists
ODIN JScott UCLB3: http://forum.xda-developers.com/showthread.php?t=1705260 Flash PASS - same problem exists
Heimdall qkster UCLB3: http://forum.xda-developers.com/showthread.php?t=1524081 Flash Successful - same problem exists
ODIN JScott UCLB3 Rooted CWM (Entropy's Daily Driver): http://forum.xda-developers.com/showthread.php?t=1613523 Flash PASS - same problem exists
CWM Install ROM Infinity ICS - Successful Install - same problem exists
CWM Install ROM SlimBean (Jelly Bean) - Successful Install - same problem exits
Problem occurs no matter how many data/factory reset wipes I do. As soon as OS boots, everything immediately starts force closing (I can see the welcome screen, but can't get to it with all the force closes on top).
Example of some of the force closes: "android.process.acore has stopped" & "com.google.process.gapps has stopped", etc.
Ran EMMC Brick Find: http://forum.xda-developers.com/showthread.php?t=1823918 and it went through each MB up to 16 GB and said OK.
I think that covers it all.
Anymore ideas on what to try?
If it is hardware, what could it be?
SuperG03
Click to expand...
Click to collapse
Here are the steps I would try to bring the phone back to a working stock GB. I can only offer a Heimdall approach.
1. Take out your microSD card.
2. Boot into DL mode.
3. Flash this in heimdall: http://forum.xda-developers.com/showpost.php?p=23118162&postcount=3
4. Boot into recovery.
5. In cwm: factory reset. Wipe cache. Advance: wipe dalvik. In Mount: format -system, data, cache, SDCard.
6. Power off.
7: Heimdall UCLB3. http://forum.xda-developers.com/showthread.php?t=1524081. Read the op. Flash it once to complete. If successful, on the PC screen, click the boot loader flash and wait for the phone to complete booting up. After the phone finishes, go to /Settings/Privacy: factory reset and wipe SDCard again. Put it back into DL mode
8. Flash the UCLB3 Heimdall again, with the BootLoader box checked.
9. Once complete, let the phone boot up and run it as stock without the microSD card.
It should run as stock uclb3 - factory new. Go through the set up - do not accept GOGGLE BACKUP for now.
If the phone process continues to crash, you are sol.
gl..
ps..you can always sell the screen..it's worth at least $75-to another user with a broken screen.
qkster said:
Here are the steps I would try to bring the phone back to a working stock GB. I can only offer a Heimdall approach.
1. Take out your microSD card.
2. Boot into DL mode.
3. Flash this in heimdall: http://forum.xda-developers.com/showpost.php?p=23118162&postcount=3
4. Boot into recovery.
5. In cwm: factory reset. Wipe cache. Advance: wipe dalvik. In Mount: format -system, data, cache, SDCard.
6. Power off.
7: Heimdall UCLB3. http://forum.xda-developers.com/showthread.php?t=1524081. Read the op. Flash it once to complete. If successful, on the PC screen, click the boot loader flash and wait for the phone to complete booting up. After the phone finishes, go to /Settings/Privacy: factory reset and wipe SDCard again. Put it back into DL mode
8. Flash the UCLB3 Heimdall again, with the BootLoader box checked.
9. Once complete, let the phone boot up and run it as stock without the microSD card.
It should run as stock uclb3 - factory new. Go through the set up - do not accept GOGGLE BACKUP for now.
If the phone process continues to crash, you are sol.
gl..
ps..you can always sell the screen..it's worth at least $75-to another user with a broken screen.
Click to expand...
Click to collapse
Thanks. I did try exactly as you stated. No go. Still crashing.
I wonder what hardware failure it would be?
SuperG03
Not sure if this will help figure out anything, but if someone is really good at looking at a logcat file, I am attaching one that I obtained from ADB from when the phone started to boot at the ATT Rethink Possibilities Screen all the way through the constant unending force closes of everything as soon as the OS loads.
Thanks again for anyone willing to look this over.
SuperG03
SuperG03 said:
Not sure if this will help figure out anything, but if someone is really good at looking at a logcat file, I am attaching one that I obtained from ADB from when the phone started to boot at the ATT Rethink Possibilities Screen all the way through the constant unending force closes of everything as soon as the OS loads.
Thanks again for anyone willing to look this over.
SuperG03
Click to expand...
Click to collapse
Just a guess and I may be wrong but I looked briefly through the beginning of your logcat. The stock gb kernel should not be looking for /etc/init.d and there were some items listed for voodoo and lagfix and some mentioning of entropy. Is your OS messing up when you are trying to run Entropy's DD kernel?
If you are running a diagnostic with complete stock to make sure the phone and firmware is using complete stock and rfs file system, these items should not be a part of your logcat...
The only suggestion I have is wipe the sdcard and voodoo folder and try a complete re-partition and boot loader flash.
gl
qkster said:
Just a guess and I may be wrong but I looked briefly through the beginning of your logcat. The stock gb kernel should not be looking for /etc/init.d and there were some items listed for voodoo and lagfix and some mentioning of entropy. Is your OS messing up when you are trying to run Entropy's DD kernel?
If you are running a diagnostic with complete stock to make sure the phone and firmware is using complete stock and rfs file system, these items should not be a part of your logcat...
The only suggestion I have is wipe the sdcard and voodoo folder and try a complete re-partition and boot loader flash.
gl
Click to expand...
Click to collapse
This actually isn't with stock. This is with the Entropy DD kernel. I followed your earlier thread to go back to complete stock and same error. I needed CWM to do other things, so I installed the Entropy DD, but same errors. I just happened to dump the logcat during that run.
As far as your suggestion, I believe that is what was already happening with your earlier post? As for RFS file system, does your Heimdal One Click do that already? If not, what do I need to do to create that specific FS? I think it might actually be Fat32 and EXT4? Thanks!
SuperG03
Heya,
Did you ever have any luck with this issue? I've a phone with similar issues.
Odin to stock - force closes and/or boot loops
Heimdall to stock - force closes and/or boot loops
Install various roms through CWM - force closes and/or boot loops
(I followed all directions to the letter, multiple times)
the last attempt lead me through a series of odins/heimdalls/roms ... basically following a path to install the latest CM10, during which sometimes a rom would seem to be stable before I moved on to the next and other roms would bootloop / fc right off the bat ..
once on CM10, though, it was stable... I was able to install apps from the market, play with settings, etc .... I did experience a 2 or 3 random reboots though in the process and ultimately, when I put my sim card and sdcard in, it was stuck in a boot loop
It doesn't appear that I'm experiencing a power button failure like other people are having ... only reason I mentioned it is because of the random reboots
Got to the point in the How-to guide that says "Navigate to ‘wipe data/factory reset’ and select it.
Navigate to the ‘yes -- delete all user data’ and select it."
Trouble is I get "E: format volume: make_extf4fs failed on /dev/block/mmcblk0p2" and "Formatting /sdcard/ .android_secure..." and a non-functioning progress bar at the bottom.
Is this a battery pull, power off, reboot into recovery? Phone has been stuck like this for more than 30 minutes.
Edit:
Ok, after an hour I powered off and back on, seems like I have a brand new SK stock ROM again >.<
Another edit:
Tried again, same exact thing on wipe data/factory reset: "E: format volume: make_extf4fs failed on /dev/block/mmcblk0p2."
Do I need to flash the kernel like on this video? (https://www.youtube.com/watch?v=W33fcnWAgQg) If so, I'm not sure which kernel to use. I was hoping to flash to the JB ROM which says it contains Bali kernel.
This is no longer fun and all of my data is wiped. LOL even the Play Store is now Android Market like way back when and won't update!
kelltech said:
Got to the point in the How-to guide that says "Navigate to ‘wipe data/factory reset’ and select it.
Navigate to the ‘yes -- delete all user data’ and select it."
Trouble is I get "E: format volume: make_extf4fs failed on /dev/block/mmcblk0p2" and "Formatting /sdcard/ .android_secure..." and a non-functioning progress bar at the bottom.
Is this a battery pull, power off, reboot into recovery? Phone has been stuck like this for more than 30 minutes.
Edit:
Ok, after an hour I powered off and back on, seems like I have a brand new SK stock ROM again >.<
Another edit:
Tried again, same exact thing on wipe data/factory reset: "E: format volume: make_extf4fs failed on /dev/block/mmcblk0p2."
Do I need to flash the kernel like on this video? (https://www.youtube.com/watch?v=W33fcnWAgQg) If so, I'm not sure which kernel to use. I was hoping to flash to the JB ROM which says it contains Bali kernel.
This is no longer fun and all of my data is wiped. LOL even the Play Store is now Android Market like way back when and won't update!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1197533
Also, when flashing a custom ROM, use this CWM file in the root of your SD card (called update.zip)
shadowscott said:
http://forum.xda-developers.com/showthread.php?t=1197533
Also, when flashing a custom ROM, use this CWM file in the root of your SD card (called update.zip)
Click to expand...
Click to collapse
AWESOME. Thank you very much for the help, flashed and running neXus JB 1.3.2.
One more question if you don't mind:
* Do I need to flash the CWM you linked every time I want to flash a custom ROM, or once it's done that it?
kelltech said:
AWESOME. Thank you very much for the help, flashed and running neXus JB 1.3.2.
One more question if you don't mind:
* Do I need to flash the CWM you linked every time I want to flash a custom ROM, or once it's done that it?
Click to expand...
Click to collapse
Once you have CWM on your phone, you don't need to run the update.zip file every you want to flash a ROM. That's it unless you go back to stock via Odin or Heimdall.