There doesn't appear to be anyone that has this problem, and I wasn't able to find anything in the development forum for CWM.
Per what everyone says, can't format /data or "factory reset" in CWM due to some sort of partition thing.
1. I boot to CWM
2. I go to mounts and storage and unmount /data
3. I plug the usb into the computer
4. Open Command Prompt and go to the adb directory
5. Enter Command adb shell and opens ~# at least that is what it looks like
6: I type "/sbin/mke2fs_static -t ext4 -b 4096 /dev/block/mmcblk0p30"
7: the response "/sbin/sh: /sbin/mke2fs_static: not found"
What am I doing wrong?
Edit: I figured it out. I ended up having to reinstall practically everything. But it worked
1 Loaded backed up rom from cwm
2 reinstalled adb
3 copied the backup recovery image back to it's original place.
4 factory reset
5 copy the cwm back
6 boot to recovery mode
7 adb commands work!!!
edit: I really should learn better grammar. I cleaned the wording up a bit.
edit2: I solved my own problem
The command not being recognized was a result of not having the latest CWM from bytecode installed. He updated it from his initial release to add support for these commands. Glad you figured it out! It can be frustrating when stuff like that happens.
Personally I'm avoiding CWM all together at this point. It's been almost a month with not a single problem (besides the BT incident) with no CWM installed, no boot loops, no reboots. There is something seriously wrong with current CWM...
[email protected] said:
Personally I'm avoiding CWM all together at this point. It's been almost a month with not a single problem (besides the BT incident) with no CWM installed, no boot loops, no reboots. There is something seriously wrong with current CWM...
Click to expand...
Click to collapse
You are right, i brick my phone today.
I was lucky that Bell change it for a brand new.
Rom development is not that safe with a so bad recovery...
HO!NO! said:
You are right, i brick my phone today.
I was lucky that Bell change it for a brand new.
Rom development is not that safe with a so bad recovery...
Click to expand...
Click to collapse
Indeed, but I have been ok since not touching /data via CWM. The manual format of /data works fine. I have flashed my own ROM zips over 20 times without issue.
Sent from my LG Nitro HD
[email protected] said:
Personally I'm avoiding CWM all together at this point. It's been almost a month with not a single problem (besides the BT incident) with no CWM installed, no boot loops, no reboots. There is something seriously wrong with current CWM...
Click to expand...
Click to collapse
I still feel CWM is a very important safety net if anything goes serious wrong ( I saw there is some download mode, but I still feel cwm is much easier to use than download mode).
For example, if you phone /system messed up, how do you fix, you only have download mode, right? If you have cwm, you will have one more option.
HO!NO! said:
You are right, i brick my phone today.
I was lucky that Bell change it for a brand new.
Rom development is not that safe with a so bad recovery...
Click to expand...
Click to collapse
I saw these unfortunately case several times in this forum, even though I never met for my self ( I following instructions never touched /data), so when you say brick, what happen exactly? Can you boot into cwm?
gte460z said:
The command not being recognized was a result of not having the latest CWM from bytecode installed. He updated it from his initial release to add support for these commands. Glad you figured it out! It can be frustrating when stuff like that happens.
Click to expand...
Click to collapse
I figured I just had a bad install. Because I think the version was the same...
but anyway, it was most definitely a fun experience.
I love CWM if it weren't for CWM I wouldn't be able to reset my phone. Which was way necessary...porting a new rom over existing data instead of a clean system caused some really interesting errors.
adb shell
umount /data
/sbin/mke2fs_static -t ext4 -b 4096 /dev/block/mmcblk0p30
/sbin/e2fsck_static -y /dev/block/mmcblk0p30
its working on LG SU640,you can try
Related
Long story short im a newb, im sorry for creating a new thread but ive exhausted my efforts looking for a solution to the problem im having. When the problem occured i had restored my original cwm backup that i created when first rooting my phone. I then did a factory wipe and reinstalled cwm and flashed my recovery. I went to install cm9 4-4-12 and i got a pop up that firmware update was available i clicked update system now and got sent to cwm recovery. Every time since then i cannot reboot into the android os, pulling battery. It doesnt matter what i do, ive tried to use a flash recovery zip i found in another thread to exit boot loop. Ive also tried restoring my original back ups and my recent back ups. I have the android sdk installed but having trouble getting adb to work not sure if i should go about trying to fix the recovery or trying to restore phone to its original state either way i think i need to get adb working before i can do either one. Any help is appreciated and im sorry if im wasting your time.
Did you try wipe cache, wipe dalvik cache, factory reset before flashing CM9?
Yes. The order i took was Wipe data/factory reset> Wipe cache partition> wipe dalvic cache> installed cm9 zip> installed gaps zip. still nothing got adb to work not doing much with it i know it has root access and when i got the state of the device it came up as unknown although im pretty sure im in recovery mode.
ok a few question and maybe a step by step to help you since i had a same promblem with a bad flash of CM9
1A. Can you boot into Recovery ? if not i can help you reflash your phone with the Kdz files took me forever to get it to work but i finilly found all the files needed.
1B. if it does boot into recovery run adb devices ... does it show the phone in recovery mode ? in the list.
If so then you can Download the following 6 files Dropbox Down link its not mine but was posted in another Nitro Recovery topic i will give credits once i re go threw the topic to see the poster
- recovery.img
- system.img
- baseband.img
- boot.img
- firmware.img
- pushall.bat
in your CWM recovery go to mounts or it may be under advanced and turn on usb mass storage and as long as all of those files are in your adb folder you can run the pushall.bat and it will place them on your sdcard.
After that turn off usb mass storage and run adb devices again to make sure you phone is still showing up. If so run these commands
Adb shell
****** notice the SU command isnt used here**** cant get super user in recovery but it will still let you run the commands and i can confirm it does work
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
dd if=/sdcard/firmware.img of=/dev/block/mmcblk0p1
dd if=/sdcard/system.img of=/dev/block/mmcblk0p27
dd if=/sdcard/baseband.img of=/dev/block/mmcblk0p14
You won't be able to issue a reboot command, so just hold power down on your phone til it's off and hold the volume down button so that it comes back up in factory data reset mode. You will want to pull your sdcard at this time if you don't want your data erased.
Hit power twice and your phone should go through its reset process and (hopefully!) come back up in a working (and rooted) AT&T "stock" rom
if not then try to follow this for the CM9 Adb Drivers Wiki for CM adb drivers i know its a little work but it dose the trick then go back up to the previous step and try that to get to stock rooted
i dont think i left anything out but i can help with anything else i know if that doesnt get you back up and running.
Credits to ???? for the drop box link with the godly files for our nitro
and to Malnilion for his guide on unbricking the nitro
edit: re-ran superoneclick for run and it worked! I should be good from here
Got everything to work. Wait spoke to soon tried to reinstall firmware update again got the same problem. oh well guess i should done fw update before installing cwm. Thanks for the help i should be able to repete this problem in the case of another brick... which just occured.
So after going through the process of unbricking my phone a second time my phone was rebooted into software update screen. Updating firmware then software and did not have to go through factory reset. Strange...
I pushed all images to my device via adb,but ota update gets an error when trying to install. At least its not bricked. Anyone know of another method?
Sent from my LG-P930 using XDA
lg nitro in recovery loop
toki, I tried your fix, but, it comes up /sdcard/boot.img is not found. any suggestions?
Tokie the dropbox links are not working
reverendyummypants said:
toki, I tried your fix, but, it comes up /sdcard/boot.img is not found. any suggestions?
Click to expand...
Click to collapse
re push the img file back to the sdcard
adb push boot.img /sdcard/ make sure that he boot.img file is in the same folder as your adb and then try the dd command for it it happened to me once
EdwinXVS said:
Tokie the dropbox links are not working
Click to expand...
Click to collapse
im uploading to my own dropbox bare with me ill posyt a live link as soon as it ready guys
cwm recovery loop
_Tokie, retried. still dd command cannot be done. file not found. The files ARE IN the adb folder. Not sure what else to do.
when you type adb push boot.img /sdcard/ what does it say ? i dont see why it will do the rest and not that one
dd: can't open sdcard\boot.img : no such file or directory
i was asking about when you pushed the boot.img to teh sdcard... if yyou want i can look at it threw teamviewer total up to you ... if you deside that pm me then info for it
Just take the SD card out and into your computer (assuming you have a card reader) and copy the files to it manually.
drumist said:
Just take the SD card out and into your computer (assuming you have a card reader) and copy the files to it manually.
Click to expand...
Click to collapse
im going to assume that he is booting into CWM its thats the case with teh usb cable hooked to the computer he can turn on mass storage from the CWM and just tranfer it that way .. if he doesnt have a reader .. i just dont see why its not copying the boot image
I'm sorry. The files are on the sdcard. When it comes time for the dd command, i get that error which i recently posted.
If you're in CWM you have to ensure your sdcard is mounted. I have got caught up on this step as well lol
Thank you to all that helped! XDA is awesome! Everything is back to normal. It also helps to have the right / or \ lol
USA Tmobile Galaxy S3
Ok so i soft bricked my phone after i flashed a rom and a kernel at the same time. They had originally worked one by one(flashing and rebooting one at a time) but i was fliddling around and decided to go back and flash them both at once with one reboot....well now i get a black screen after the galaxy S3 logo....and it hangs.
I have acess to recovery
I can ODIN but since that happened no flashed kernels or roms have made a difference
(all connections and flashes are successful in ODIN)
I have reverted to stock recovery and can access ADB through ADB shell in the SDK BUT i dont have permission to push files or even see inside data folder.... <su> issues a Segmentation fault, and <adb root> root all it does is restarts the session, ID's the port says successful and then issues a device not found and reverts to adb shell access to phone without permissions....
(should i flash a factory PIT file or maybe fix the partition tables? i say this because i assume a segmentation fault is the result of that?)
and where do i find a factory USA Tmobile Galaxy S3 Pit file? i found all these international ones in another thread but that doesn't help
So I have a recovery file on my SD card, Is there a Clockwork Recovery installation that has the ability to flash recoverys from the external SD? (this new touch version lets me mount the external SD but it doesnt pull any files up its formatted FAT32, but do i need to create certain folder names for CWM to see it?)
so that's where im at, In a nutshell:
Cant push via adb because no root permission, i have a recovery on an external SD that CWM does mount but doesn't pull it up and none of the Roms, and kernels i flash through odin(albeit successful without a hitch) make a difference on my boot situation.
thanks for any input i have over 19 flashes on my counter, and 2.5 days of 8-10 hours researching various things ive no decided to ask the community for help....
So far i got ahold of the previous Clockwork before the touch came out but it doesnt have options for external and internal im still allowed to mount externalSD card but whats the for if you cannot ADB with clockwork nor install from exernal SD?
Thanks for your time guys
xgp0006 said:
USA Tmobile Galaxy S3
Ok so i soft bricked my phone after i flashed a rom and a kernel at the same time. They had originally worked one by one(flashing and rebooting one at a time) but i was fliddling around and decided to go back and flash them both at once with one reboot....well now i get a black screen after the galaxy S3 logo....and it hangs.
I have acess to recovery
I can ODIN but since that happened no flashed kernels or roms have made a difference
(all connections and flashes are successful in ODIN)
I have reverted to stock recovery and can access ADB through ADB shell in the SDK BUT i dont have permission to push files or even see inside data folder.... <su> issues a Segmentation fault, and <adb root> root all it does is restarts the session, ID's the port says successful and then issues a device not found and reverts to adb shell access to phone without permissions....
(should i flash a factory PIT file or maybe fix the partition tables? i say this because i assume a segmentation fault is the result of that?)
and where do i find a factory USA Tmobile Galaxy S3 Pit file? i found all these international ones in another thread but that doesn't help
So I have a recovery file on my SD card, Is there a Clockwork Recovery installation that has the ability to flash recoverys from the external SD? (this new touch version lets me mount the external SD but it doesnt pull any files up its formatted FAT32, but do i need to create certain folder names for CWM to see it?)
so that's where im at, In a nutshell:
Cant push via adb because no root permission, i have a recovery on an external SD that CWM does mount but doesn't pull it up and none of the Roms, and kernels i flash through odin(albeit successful without a hitch) make a difference on my boot situation.
thanks for any input i have over 19 flashes on my counter, and 2.5 days of 8-10 hours researching various things ive no decided to ask the community for help....
Click to expand...
Click to collapse
You said you can ODIN, so ODIN the stock ROM and/or kernal does not work?
http://forum.xda-developers.com/showthread.php?t=1737855
Have you tried a simple wipe cache and dalvik, fix permissions?
I had tried a stock rom ealier. I shall try a stock rom and kernel in a few again and wipe caches and fix permissions and see what i get.
thanks for throwing that out there at least ill give this and another suggestion i got a shot and reply with my results....
B-Naughty said:
You said you can ODIN, so ODIN the stock ROM and/or kernal does not work?
http://forum.xda-developers.com/showthread.php?t=1737855
Have you tried a simple wipe cache and dalvik, fix permissions?
Click to expand...
Click to collapse
xgp0006 said:
I had tried a stock rom ealier. I shall try a stock rom and kernel in a few again and wipe caches and fix permissions and see what i get.
thanks for throwing that out there at least ill give this and another suggestion i got a shot and reply with my results....
Click to expand...
Click to collapse
If you're already running CWM, try the wiping and fix permissions before ODIN flash to stock with the TMobile image
So, I recently acquired an Incredible, the second one I've owned. The first one I rooted, turned S-off and installed CM7 with zero difficulties, after that I rooted/flashed my Xperia Play CDMA with all the issues that accompany that device. (after the ease with which I modded my first DINC, the hoops through which I had to jump to unlock my bootloader blew my mind)
This DINC, though, refuses to clear user data. Even after multiple wipes via CWM, and multiple updates using the PB31IMG method, user data remains. Attmepts to preform a factory reset via HBOOT result in a balck screen with a red triangle and exclamation point.
I tried to install MIUI, thinking maybe a fresh rom would fix it, but it gets stuck at the room splash screen.
I've even tried recovering a clean CM7 install from my old incredible, but it gets stuck in a bootloop at the rom splash, same story trying to flash the .zip in recovery.
I've seen a few threads that deal with a few of these symptoms, but not the issue as a whole
Thanks in advance for any answers you guys have!
Cheers
I found a solution, finally. Admittedly, it was a bit drastic, but it worked, nonetheless.
I ended up disassembling both DIncs and putting the motherboard of the working device (with the smashed screen) into the device that was unable to format /data.
It was a bit touch and go for a bit, but my new DIY refubished phone is up and running.
Thanks for the help guys!
What error do you get? Can you upload the logs from /cache/ recovery after trying to wipe?
Sent from my Galaxy Nexus using Tapatalk 2
I'm still a bit of a noob, if you could point me towards some basic instructions on how to do that, I'll post a log when i get back to the house.
Last time I tried to logcat something in recovery, I nearly bricked my phone somehow.
Edit: It either gives me the red error triangle/exclamation point if i use HBOOT, or it gives me an error when trying to format the data partition on a recovery attempt.
mattdubuc said:
I'm still a bit of a noob, if you could point me towards some basic instructions on how to do that, I'll post a log when i get back to the house.
Last time I tried to logcat something in recovery, I nearly bricked my phone somehow.
Edit: It either gives me the red error triangle/exclamation point if i use HBOOT, or it gives me an error when trying to format the data partition on a recovery attempt.
Click to expand...
Click to collapse
Re-flash CWM recovery. The red triangle is a problem with recovery most likely. You can flash the latest CWM for the incredible from the app.
If that doesn't work then pull all the files from /cache/recovery location, use a file explorer app that can read it and copy it to the /sdcard location and upload it in a zip.
tiny4579 said:
Re-flash CWM recovery. The red triangle is a problem with recovery most likely. You can flash the latest CWM for the incredible from the app.
If that doesn't work then pull all the files from /cache/recovery location, use a file explorer app that can read it and copy it to the /sdcard location and upload it in a zip.
Click to expand...
Click to collapse
The red triangle happens when you try to do a factory reset from hboot wile on cwm recovery. If you really need to do a factory reset, you will need to flash to the stock recovery first. http://dinc.does-it.net/Recoveries/Stock_4.08.605.15/PB31IMG.zip Then if it works or even if not flash back to cwm recovery http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip.
The weird thing is, that even after flashing PBG31IMG via HBOOT I'm retaining all the previous user data. I've tried formatting the internal drive, using a few different versions of the image, even manual formatting of /data via CWM, which only gives me an error. the same error as when I tried to restore a nandroid from my functioning DINC.
tiny4579 said:
If that doesn't work then pull all the files from /cache/recovery location, use a file explorer app that can read it and copy it to the /sdcard location and upload it in a zip.
Click to expand...
Click to collapse
So do i just make a .zip file out of the contents of /cache/recovery or is there something more to it?
mattdubuc said:
So do i just make a .zip file out of the contents of /cache/recovery or is there something more to it?
Click to expand...
Click to collapse
That should be fine. Try to wipe data in cwm again just so it logs it.
Sent from my Galaxy Nexus using Tapatalk 2
I'm having the same issue, even after reflashing a rom or hard reset my system is as it was before, but most apps don't work. After turning on device instantly shows many errors such as error in com.android.phone etc... While trying factory reset in Recovery (5.0.2.0) the only error that logs is "no app2sd partition found. Skipping format of /sd-ext ". What can you advise? Please help, tomorrow I'm going to another country and in this moment working phone is very needed Device S-OFF Rooted HBoot 0.92
zslashy said:
I'm having the same issue, even after reflashing a rom or hard reset my system is as it was before, but most apps don't work. After turning on device instantly shows many errors such as error in com.android.phone etc... While trying factory reset in Recovery (5.0.2.0) the only error that logs is "no app2sd partition found. Skipping format of /sd-ext ". What can you advise? Please help, tomorrow I'm going to another country and in this moment working phone is very needed Device S-OFF Rooted HBoot 0.92
Click to expand...
Click to collapse
Same error if you flash stock GB sense and factory reset from recovery? You have the errors when booting and the apps are still there?
Sent from my Nexus 7 using Tapatalk 2
Thank you for reply, I solved reset issue by installing Amon Ra recovery. But the problem with apps still exists, it looks like system is restoring back up after reboot, I can do everything with system but after reboot it's like it was before with no changes made. Additionally, it seems that the problem is with emmc, just because when I delete EVERYTHING on it, after restart all files appear again!
I'm also getting an error when I try to manually format the data partition under >mounts and storage in CWM, I'm assuming that may be to blame for retained user data?
When I run show log after running only a manual /data format it displays:
6 black groups
32768 blocks per group. 32768 fragments per group
8112 inodes per group
superblock backups stored on blocks:
32768. 98304. 163840
The filesystem already has a journal,
tune2fs 1.41.6 (30-May-2009)
Setting current mount count to 1
Failure while running mke2fs
Error formatting /data!
mtd: succesfully wrote block at 0
I:Set boot command ""
I have no idea what that means really, or even if it's pertinent.
I had to remove the user info (owner data, phone number, etc) from my inc after canceling my contract with verizon. After about 25 different attempts to wipe it, I finally found something that worked (at least for me)
Tried running the RUU, could not reboot into HBOOT (version error)
Tried the RUU again, this time starting it after manually booting the phone to HBOOT. Got a little farther than before, but still errored out. Did not work. Disconnected phone, pulled battery, rebooted to HBOOT.
Factory reset in HBOOT got me stuck on the stock recovery screen. Battery pulled, could not boot.
Flashed CWM in HBOOT (by renaming to PB31IMG.zip), was able to get into CWM recovery.
Tried to flash the 2nd GB OTA in CWM, did not take. Every option I clicked in CWM gave me about 7 errors after sitting on the logo for a moment. Battery pull, reboot. Boots into CM9. >.<
Booted to my rom, saw about 300 force closes. Tried to reflash CWM from Rom Manager, got a bunch of force closes. Updated Rom Manager from market, reflashed CWM, and this time it worked.
Rebooted to CWM, wipe data/cache/dalvik, reboot.
This time I booted in CM9, but to the initial ICS set up (click next to begin, wireframe pic of Andy)
After skipping thru initial setup, I checked Settings>About Phone>Status. My phone number was removed, network is Unknown, and all my data was removed. Activation prompt appears on each boot.
Not sure if this will help, but worth a try. I think that the HBOOT factory reset is what cleared my data, and then I just needed to fix CWM so I could get back to a working ROM.
Yeah that's what I did in june except I just got service on mine but I would think that would help getting your data out forever. If that does not work I wouldn't know what to tell u besides grab a magnet. Lol
Sent from my Droid Incredible using xda premium
Hi Guys,
I have a big problem! I forgot to flash the boot.img of "Jelly Bam 7.2.1" - it all ended in total chaos. I will try to describe everything I did, feel free to ask any further on points that seem to be more relevant than I thought.
To let you know: I have knowledge of flashing / custom roms and all that good jazz in general (with other phones before), but I am a total noob concerning all the One X specific stuff...
1.) rooted my One X. No problems so far, stock rom working fine after doing so, HBoot says "UNLOCKED" at the top, so no problems here.
2.) downloaded the custom ROM (JellyBam, endeavoru, 7.2.1), checked MD5, so no problems with the download - copied it to my phone
3.) went into recovery without fastboot, just the way via hboot and did the following in that order: "wipe data/factory reset", "wipe cache partition", formatted "/cache", formatted "/system", formatted "/data", "wipe dalvik cache", flashed the zip "jelly-bam-blabla.zip"
4.) tried to boot, which obviously did not work, because I forgot flashing the boot.img.... but in concrete: the phone first showed the normal "HTC"-Screen, then the JellyBam loading screen came on the screen, then the "Android Welcome Screen" showed up. after 0,5 seconds a pop-up came up saying "Unfortunately, System UI has stopped." and some 0,5 seconds after another pop-up places itself right over the other one. it says "Unfortunately, the process com.android.phone has stopped."... I tried to hit "OK" but it always came up again within 0,5 seconds or shorter.
5.) I went into hboot from there, because my first idea was, that the problem could have been me having forgotten the "fix permissions" after flashing the rom... so i did all the cache / formatting stuff again, flashed the zip again and then fixed permissions.
6.) tried to boot, exactly the same situation as described in "4"
7.) the boot.img-stuff came in my mind. slapped myself in the face several times. the "you should always fastboot flash your recovery if you want to flash anything on your phone"-advise also came in my mind. hurt my face for some more seconds.
8.) went into hboot again, then "fastboot", connected to my MBP and firstly tried to fastboot flash cwm-recovery. but the terminal said that my HOX is too low on battery life...
9.) the part I actually can't remember correctly. tried different advises on how to load the battery without having a rom up and running (from xda devs mainly) - which all did not work but somehow resulted in my HOX not even letting me boot up normally anymore. a (re)boot just kicks me directly into cwm recovery.
10) my battery went totally empty. and now the scary part i really do not understand begins: I connected my HOX via the usb cable to a power adapter. the orange light first started blinking, then it stood on for about 3 hours - I did not touch it. after these about 3 hours the device automatically booted into cwm recovery. i went into hboot which resulted in the normal error messages while connected via usb to a power adapter or a computer, so i unplugged the cable and rebooted recovery. again went in hboot, which now tells me I am too low on battery to flash anything. Because the orange light is only on in cwm recovery I thought that the phone charges there (I also read that, but the people said it would be veeery slow), so I tried to keep it in recovery. the problem is: it automatically shuts down after 20-30 minutes... I tried to avoid that as long as possible, always just hitting volume down once every 20 minutes - but even after doing that for about 6 hours, hboot still told me my battery is too low...
I really do not know what to do. I am never able to stay at home for longer than these 6 hours, so I do not know how I might get the battery high enough in order to flash the boot img or the zip in cwm again...
Please help me you genius people out there!
P.S.: The nerd video at registration is nicely done. I really like it. And I hope I did not overlook a thread that could solve my problem...
I'm not sure this is correct but I'd let it charge then in fastboot erase cache flash the boot then erase fastboot cache again.
A
Htc One X Viper 3.4.2
frontinsomething said:
Please help me you genius people out there!
Click to expand...
Click to collapse
At your service!!
Use this lil script to charge your device. It reboots the handset over and over again causing it to build up voltage. Once it prints out ~3750mV or higher, you should be good to flash.
http://forum.xda-developers.com/showthread.php?t=1658084
http://forum.xda-developers.com/showthread.php?t=1658084
Make this little script and execute it as a batch
Flash this recovery - http://download.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.4.0-endeavoru.img
Download the stock rom from here - http://forum.xda-developers.com/showthread.php?t=1546970
Fastboot flash the boot.img and `fastboot erase cache`
Wipe data and flash the rom.
You`ll at at least be in a working rom.
P.s you dont have to flash recovery all the time. Flash it once and leave it.
Iceax123 said:
I'm not sure this is correct but I'd let it charge then in fastboot erase cache flash the boot then erase fastboot cache again.
Click to expand...
Click to collapse
Yeah, my plan looked similar. The problem is you forgot the first stept. What I need is to
1.) somehow charge my phone to an adequate degree
2.) fastboot erase cache / flash boot.img / erase cache
3.) flash the zip again (just to make sure)
Can you help me for step one of that?
As described before the charging does not really work. In cwm it charges freakin slow, in hboot it does not seem to at all (I am not quite sure 'bout that)...
come on guys, you are way too fast in answering I knew why I like this place
I guessed people would come up with the script. the point is, that I tried that and failed at it... can somebody exactly tell me how to to that on Mac? I failed at it... (see step 9)
frontinsomething said:
come on guys, you are way too fast in answering I knew why I like this place
I guessed people would come up with the script. the point is, that I tried that and failed at it... can somebody exactly tell me how to to that on Mac? I failed at it... (see step 9)
Click to expand...
Click to collapse
I don't own a mac but it's really similar to Linux, so.....
Name it .sh instead of bat. And mark it executable by going to terminal as root and typing
Code:
chmod a+x [path_for_the_file]
Or use some gui to set it executable.
Then it should work by simply double clicking.
Good luck:good:
EDIT If fastboot commands different on mac, for example "fastboot-mac flash blablah", you need to modify the script accordingly.
TToivanen said:
I don't own a mac but it's really similar to Linux, so.....
Name it .sh instead of bat. And mark it executable by going to terminal as root and typing
Code:
chmod a+x [path_for_the_file]
Or use some gui to set it executable.
Then it should work by simply double clicking.
Good luck:good:
EDIT If fastboot commands different on mac, for example "fastboot-mac flash blablah", you need to modify the script accordingly.
Click to expand...
Click to collapse
Nice! At least the script works! Although it runs since 20:30 now and still only brought me up about 1mV... but let's see where I get. I will try to do all the good jazz if I get over 3680 - I will tell you as soon as it worked or if it did not.
See you later and thanks for the help so far!
frontinsomething said:
Nice! At least the script works! Although it runs since 20:30 now and still only brought me up about 1mV... but let's see where I get. I will try to do all the good jazz if I get over 3680 - I will tell you as soon as it worked or if it did not.
See you later and thanks for the help so far!
Click to expand...
Click to collapse
Nice ! Fingers crossed
Sent from my IceCold One X
TToivanen said:
Nice ! Fingers crossed
Sent from my IceCold One X
Click to expand...
Click to collapse
Just noticed, that I also need/want to flash the zip again - how much mV would I need for that?
Once you have flashed the boot image (fastboot batt warning vanished), you'll be good to flash the zip also.
Sent from my IceCold One X
You Are Epic, Guys!
Thank you for your help, not only, but mainly TToivanen!
Everything worked out fine! ROM is now up and running! yippieh!
Nice !
Enjoy the new ROM
Sent from my IceCold One X
Hi,
My GNEX is keep rebooting. I tried flash with stock rom or other custom rom and it is said in the CWM recovery that I have successfully flashed but then when reboot, it keeps using old rom. I already check the emmc block and i fsck some block which got problem and it is success. But then, after reboot, it still using old rom.
Behavior:
1) Keep rebooting to old rom although already flashed with stock rom, delete dalvik cache and so on.
2) When in adb shell, i tried push some custom rom in the /sdcard in my GNEX, it is transferred successfully. But when I reboot, the file i transferred gone and left old file. I already do rm -rf to /sdcard and check the /sdcard is empty. But when reboot, /sdcard is back to having old file.
3) My behavior is becoming stress with the issue.
Please help me guys.
Thanks in advance.
ariffisariff said:
Hi,
My GNEX is keep rebooting. I tried flash with stock rom or other custom rom and it is said in the CWM recovery that I have successfully flashed but then when reboot, it keeps using old rom. I already check the emmc block and i fsck some block which got problem and it is success. But then, after reboot, it still using old rom.
Behavior:
1) Keep rebooting to old rom although already flashed with stock rom, delete dalvik cache and so on.
2) When in adb shell, i tried push some custom rom in the /sdcard in my GNEX, it is transferred successfully. But when I reboot, the file i transferred gone and left old file. I already do rm -rf to /sdcard and check the /sdcard is empty. But when reboot, /sdcard is back to having old file.
3) My behavior is becoming stress with the issue.
Please help me guys.
Thanks in advance.
Click to expand...
Click to collapse
I have same problem. When i turn on my phone there is a google screen and then "X" screen. After 30 seconds it reboots again and again. I tried everything that i found on xda forum. Pls help !
ariffisariff said:
Hi,
My GNEX is keep rebooting. I tried flash with stock rom or other custom rom and it is said in the CWM recovery that I have successfully flashed but then when reboot, it keeps using old rom. I already check the emmc block and i fsck some block which got problem and it is success. But then, after reboot, it still using old rom.
Behavior:
1) Keep rebooting to old rom although already flashed with stock rom, delete dalvik cache and so on.
2) When in adb shell, i tried push some custom rom in the /sdcard in my GNEX, it is transferred successfully. But when I reboot, the file i transferred gone and left old file. I already do rm -rf to /sdcard and check the /sdcard is empty. But when reboot, /sdcard is back to having old file.
3) My behavior is becoming stress with the issue.
Please help me guys.
Thanks in advance.
Click to expand...
Click to collapse
This is the behavior that happens when your emmc dies. It gets stuck in a read only mode.
I'm sorry to inform you that nothing will fix it. It is DEAD!
If you check the forums you will find dozens of threads exactly like yours.
Even though flash storage lasts a lot longer than mechanical storage. It is not immortal.
DR3W5K1 said:
This is the behavior that happens when your emmc dies. It gets stuck in a read only mode.
I'm sorry to inform you that nothing will fix it. It is DEAD!
If you check the forums you will find dozens of threads exactly like yours.
Even though flash storage lasts a lot longer than mechanical storage. It is not immortal.
Click to expand...
Click to collapse
Erk.... No wonder sometimes when in fastboot mode, when flashing the userdata.img, it will failed with "Read Only Mode" error.
:crying::crying::crying:
But, thanks bro for your information.