Related
I am following these instructions to bring my phone back to stock, before I send it in for a replacement (Alt key isn't working):
1. get the original SPL for your phone, go to the SPL thread at the top
2. rename it to update.zip and flash it to your phone
3. download the DREAIMG.nbh from the thread where you rooted your phone
4. place DREAIMG.nbh on the root of your SD card and start phone in bootloader(camera+power)
5. hit power to start the update DO NOT INTERRUPT!! i can not stress this enough
6. hit action(trackball down) and your phone will reboot
7. YOU NOW HAVE STOCK FIRMWARE, it will update on it's own in a little bit
I downloaded G1OrigBootloader_nocheck.zip, copied it to my SD card, renamed it to "update.zip", turned the phone off, powered up holding HOME and POWER and then pressed ALT+W for wipe and then ALT+S to apply the update. So far, so good.
Then I deleted update.zip from the SD card and moved DREAIMG.nbh onto it. I powered off the phone, then pressed the camera button and power. It has the white screen with the blue text "Loading..." and then the screen briefly flashes with "No image file!" before going to the bootloader screen.
Help! I don't know what to do next. Many thanks!
ETA: Should I install the DREAIMG.nbh *before* installing the stock SPL?
ETA 2: I formatted my SD Card just for grins (I could swear I had done that before) and now it's working fine. So. For anyone else who gets the No Image File error, try formatting your SD Card and then transferring files. Also, I re-downloaded the DREAIMG.nbh file so it might've even been that which fixed it. At any rate, I no longer need assistance and I don't know how to delete a post. I'm assuming you can't.
In case anyone else comes across this thread while having this problem...
I had the same problem with my Rhodium. The problem disappeared when I switched from formatting that particular SD card with FAT to FAT32.
So, try FAT32 and see if that helps!
captbunzo said:
So, try FAT32 and see if that helps!
Click to expand...
Click to collapse
Yup^ android cant read fat partitions.
Also why do you want to unroot?
I was helping a friend unroot for a warranty return and I encountered this problem. While I realized that it was a simple, and some what dumb typograpghical error in my case. Have you checked, and I mean really checked the filename? I realized that I had a space in between the "G" and the "." (DREAIMG .nbh, rather than DREAIMG.nbh) I have the RC29 and RC30 .nbh images backed up on my home computer for just such purposes and I have them labeled accordingly (example: DREAIMG RC29.nbh). So when I went use it, I copied the file, edited the name, and forgot to take the space out. It therefore displayed no image for me as well. Just something simple to check.
It happened yesterday when I upgraded to xrom. I have formatted and repartitioned my sd card. Nothing is working. When I connect my sd card to my computer I noticed a lot of weird files were being stored on it. They reappear every time I delete them.
My phone is creating files like this "qxdm_20090910_184004_3.dm" (32 megs!)
hmm....very interesting... reboot into recovery and repair the ext files? it might work. most likely not, but its worth a shot.
I though about trying that but I don't have cyanogens recovery .
Mine just did the "sd card has been removed" thing half an hour ago.
I just copied a new theme .zip to my sdcard and then rebooted into recovery.
I could not apply the update since it could not mount the mmcblk0p1 partition. When boot all the way up to android i get the icon saying that the sdcard has been removed.
i just did an adb push of a file to my /sdcard from the recovery console and it returned no errors...but i cannot see any files on the card.
wtf.
Any ideas?
Yeah my problems still not fixed. I have searched the XDA, forums, Google, none have offered any solution. I have found a lot of people with this same problem.
are you using swapper? if you dont turn it off, this could happen.
i would recommend getting cyans recovery image, it has a lot of tools to debug.
get a live cd of linux/gparted and see if you can see all your partitions. if not, your sd card is most likely dead. try reformatting. if that doesnt help, you may need to get a new card.
if it does show up on your pc, but doesnt work on your phone, then post here again
Have the same problem. Got it right after updating cyanogenmod 4.1.2 I've also been looking for answers and I think I'm just gonna get a new one
I have never used swap. I tried installing cyans recovery image through terminal but it can't find my sd card. I can still update my rom through jfs utility. My sd card works perfectly fine on my computer.
Something like this happened to me a while ago. It first said Sdcard was damaged and i couldnt access it via any file manager. I rebooted and turned out all my apps went up in the air and dissapeared and my fat32 partition was gone to. i reccomend backing up your sdcard and reformatting your card then go froom there
I have already tried all that. Nothing so far has worked :-(. Man this is horrible. I can't even take pictures!
Hi team,
Having some trouble rooting my g1 and upgrading to CM 4.2.4
I have been following a tutorial from here: http://androidandme.com/2009/08/news/how-to-root-a-t-mobile-g1-and-mytouch-3g-android-phone/
... to achieve my goal. Followed all of the steps fine and to a tee. Installed all of the suggested files from the suggested places.
Succesfully upgraded the radio image, then moved onto upgrading the SPL. Ran through and rebooted phone, until the never ending "Formatting Cache" notice came up on the automatic boot into the Recovery Mode.
(FYI: radio and SPL images were from http://code.google.com/p/sapphire-port-dream/)
Moved on to installing CM 4.2.4 after realising that the format was complete... Alt-W then Install from zip. Installed CM. Waited for prompt for completion... pressed reboot... then the boot hangs on the G1 startup screen.
Only way I could get out was to remove the battery. Went through the process again (Alt-W, SPL install, reboot, Alt-W, CM install, reboot, hang) numerous times, all with the same outcome.
Only thing that I can think of that I am doing wrong is pulled straight from CyanogenMod Wiki explanation: "I've noticed on some devices that when you fresh install the first time and you update with the rooted adp package from htc, reboot and then update to latest CM, some people get stuck at the tmobile logo. What I did was install the rooted adp package from htc, reboot and sign in all the way to home screen, then rebooted and installed the latest CM. That should get you past the first screen freeze if it happens to you."
As I am a noob, I have been unable to try this for the following reasons: 1. Where can I find the HTC rooted adp? and 2. How do I get this image onto the SD card when I can't boot in? I have tried without booting and my computer won't let me access via USB...
I was going through the process from factory settings. Is this my problem... Very confusing.
Realise that there are currently two active threads running in this section that are similar... but these guys seem to have done the wrong thing and are trying to right the ship... I can't seem to figure where I've gone wrong.
Thank you in advance for your assistance.
As well: could booting with camera + power get me into the Dreaming.nbh OS to get HTC root OS onto the SD card?
http://developer.htc.com/adp.html
Download the 1.6 recovery image. It is actually the 1.6 Android Dev Phone ROM, flash that via recovery console... then flash the cm update. Make sure you wipe before you start flashing.
As well, do you have your SD card partitioned? It would be a good idea to do that as well. Two ways to do it, manually, or download and update to RA's recovery image 1.2.3:
http://forum.xda-developers.com/showthread.php?t=566669
I would update to that recovery first, use the option to part my SD card, upgrade to ext3, wipe, flash 1.6 recovery, flash cm update, good to go!
Thanks for the quick reply! Very handy info... How do I get the images onto my SD card without being able to boot though?
Do you have another device like a camera, or mp3 player that can take a microsd? If so just hook it up and transfer.. otherwise you may need some additional devices.. I bought an adapter so my sd can plug directly into a usb.. other than those couple options, I haven't any more suggestions to offer ya. If you cant get past the boot screen to mount, I don't see how you can do it through your G1.. there might be some terminal commands you can try to mount to a computer.. but that's beyond me.
Nathanial said:
Thanks for the quick reply! Very handy info... How do I get the images onto my SD card without being able to boot though?
Click to expand...
Click to collapse
You take it out of the phone, while the battery is pulled, put it in an micro SD card reader, plug that into your computer, tada! If you computer doesn't have a slot for the standard SD card adapter, you can get microSD to USB adaptors most everywhere that sells electronics.
Or if you have cyan's recovery installed... you can hold Home+power
go to console, press enter and type
ums_enable
Click to expand...
Click to collapse
and it will mount the sd on your pc.....
put ums_disable to unmount
Sorry to be a noob, but what benefit does partitioning do?
If you have an EXT3 partition, you will have app2sd. If you also have a linux-swap partition, you will be able to have a swap file (in simple terms its like adding more ram)
The ext partition is for apps2sd, and the Linux-swap partition is to give a little extra memory for the ROM.
Thanks for all of your help lads! Up and running. Muchly appreciated!
My Boot will not boot no matter what I do. I encountered this issue after flashing to phiremod v4, which worked beautifully until I decided to free up some storage space on my SD card and format it through the Nook. The next time I tried to boot, I got the dreaded black screen.
I've burned Clockwork Recovery (4gb v .7) onto the SD card and copied the Nook Color V1.1.0_r2 rom (found here http://forum.xda-developers.com/showthread.php?t=932145). From there, I formatted the data, system, and cache, then installed the rom from the SD card. Everything went through smoothly, until I rebooted the Nook (with the SD card out). Nothing happens! The Nook simply will not reboot without the SD card inserted. Even if it boots (with the SD card) it just sends me back to Clockwork Recovery.
I also tried recovering the Nook through ADB (using the steps found here http://mrm3.net/2011/01/24/113/). I install everything, but I cannot locate the ADB device in the device manager. I've even used the .bat file to auto installs ADB, but it is still not found in the device manager.
I've read that it is nearly impossible to brick a Nook, but I'm not sure what else to try. I'm a Android noob, so please bear with me. TIA!
Fairly certain I read about a bug with formatting the SD card on the NC, that it would format the internal memory instead. I would imagine you will need to flash a new image to the internal memory (should be stock image floating around here somewhere).
No worries, you are most likely NOT bricked. There are hundreds of posts about people thinking they bricked their device.
First thing is first, IF YOU READ THE POST IT SPECIFICALLY STATES DO NOT FORMAT THE SDCARD USING THE NOOK AS IT WIPES THE /BOOT
My suggestion to you is do some research on XDA there are PLENTY of posts about "unbricking" your device.
I have only seen 1 nook be bricked, and it was hardly bricked because it could be booted from an SDCard.
Try following the instructions here to return back to the stock OS:
http://nookdevs.com/Flash_back_to_clean_stock_ROM
Reneg4d3 said:
No worries, you are most likely NOT bricked. There are hundreds of posts about people thinking they bricked their device.
First thing is first, IF YOU READ THE POST IT SPECIFICALLY STATES DO NOT FORMAT THE SDCARD USING THE NOOK AS IT WIPES THE /BOOT
My suggestion to you is do some research on XDA there are PLENTY of posts about "unbricking" your device.
I have only seen 1 nook be bricked, and it was hardly bricked because it could be booted from an SDCard.
Try following the instructions here to return back to the stock OS:
http://nookdevs.com/Flash_back_to_clean_stock_ROM
Click to expand...
Click to collapse
Yeah, I realize that was a big no no. I am unable to perform any of the steps in the link you provided because my nook doesn't even reach the 'Welcome to the future of reading' screen. Also, I can't try method 2 because ADP is not working properly.
I should mention that I also tried samuelhalff's first method to no avail. Any other ideas?
So you CAN boot from an SDCard correct? Only way to boot again is to flash the boot file...
Reneg4d3 said:
So you CAN boot from an SDCard correct? Only way to boot again is to flash the boot file...
Click to expand...
Click to collapse
Yes, I can boot (to Clockwork Recovery) if the SD card is inserted and the power cord is inserted and I hold the power button for 10 seconds. If I install a rom from the SD card, doesn't it flash the boot file? If not, how do I flash the boot file?
I know you said you tried Sams method, I would re-read how to flash his boot repartition file found on his froyo on emmc thread
thadeus_d3 said:
Yes, I can boot (to Clockwork Recovery) if the SD card is inserted and the power cord is inserted and I hold the power button for 10 seconds. If I install a rom from the SD card, doesn't it flash the boot file? If not, how do I flash the boot file?
Click to expand...
Click to collapse
Here's the link to the boot file. I did the same thing not long ago (formatted SD from within CM7) and I fixed it by flashing this file to repartition the boot.
It's the last link in the OP of this thread (repartition-boot-with-stock.zip):
http://forum.xda-developers.com/showthread.php?t=914690
If that doesn't work, he has a couple of restore to stock methods in that thread as well.
C Dippa said:
Here's the link to the boot file. I did the same thing not long ago (formatted SD from within CM7) and I fixed it by flashing this file to repartition the boot.
It's the last link in the OP of this thread (repartition-boot-with-stock.zip):
http://forum.xda-developers.com/showthread.php?t=914690
If that doesn't work, he has a couple of restore to stock methods in that thread as well.
Click to expand...
Click to collapse
YES! This did it! I missed this link somehow. Many thanks to all that helped.
Ok, now I'm stuck on the screen that says "Contains Reader Mobile technology by Adobe Systems Incorporated". Did this happen to you C Dippa? I'm going to try a reset and see if that helps.
thadeus_d3 said:
Ok, now I'm stuck on the screen that says "Contains Reader Mobile technology by Adobe Systems Incorporated". Did this happen to you C Dippa? I'm going to try a reset and see if that helps.
Click to expand...
Click to collapse
Nope...it just booted up, may have taken a little longer.
Any luck with it?
Yeah, I had to do the 8 failed boot attempts to bypass that screen, then re-root. Now, I'm all set! Phiremod is installed again.
Glad to have helped! Happy nooting!
Sent from my Droid using Tapatalk
Data wipe error, Can't mount /dev/block/mmcblk0p1, or Vibrant screen boot loop even after flashing stock odin JFD phone will not boot. Phone will only boot Eugenes JK2 but internal and external storage will still list as corrupted and Lists 0.00 MB in storage.
Internal storage has been destroyed, I’ve been able to fix a phone using this technique to be mostly working. The external SD card will always have to be in the phone for this to work.
1. Partitioning the MicroSD Card
Get an 8gb(or larger) micro sd card. Class 10 would be better here. Put it into a Card Reader, then run Gparted.
Gparted (usb method is easiest) - http://gparted.sourceforge.net/liveusb.php
Using Gparted, delete everything else and create 2 partitions and :
6000mb FAT32 as PRIMARY
1607mb(remainder) Reiser as PRIMARY
2. Flash to Stock
Open up Odin flash stock JFD with pit file and repartition checked.
After phone boots completely, power off.
3. Flashing CM9
Take MicroSD out of phone an put it in pc, then copy update.zip, GAPPS, Cyanogenmod Rom all to the FAT32 partition that we created earlier. In Windows it should show up where all of your drives are listed in.
update.zip (https://www.dropbox.com/s/ju5eg5ernxcaqpt/update.zip),
GAPPS (www.goo-inside.me/gapps/gapps-ics-20120317-signed.zip)
CyanogenMod Rom Zip(http://download.cyanogenmod.com/get...e-cm-9-20120520-NIGHTLY-vibrantmtd-signed.zip)
Enter recovery mode with volume buttons and power.
Reinstall packages twice.
Install zip from sd card select update-cm-9-20120520-nightly-vibrantmtd-signed.zip phone will boot loop on vibrant screen so take out the battery then enter recovery a second time installing the cm9 update again.
Then flash Gapps zip the same way.
When phone boots up camera, and gallery will not work until the next step.
4. Edit Vold.Stab file
Downlad ES File Explorer from play store.
Hit Menu button, settings, Check box for Root Explorer, Check box for mount file system, check box for Up to Root
Press Up once, you should now be at "/"
Open system directory, open etc directory, scroll to bottom and select Vol.fstab, select Text, Select ES Note Editor, update text to the following:
#internal sdcard dev_mount emmc /mnt/sdcard 1 /devices/platform/s3c-sdhci.0/mmc_host/mmc0
#external sdcard dev_mount sdcard /mnt/emmc auto /devices/platform/s3c-sdhci.2/mmc_host/mmc2
After edits, click back and click yes to save changes. Exit out of es file explorer and restart phone. Post results:
Should work with any version of CM9, newer nightlies would obviously be preferred. Will make more detailed guide soon.
Credit to these guys for providing the solution -
http://www.youtube.com/watch?v=zdMhYYdMB08
http://forum.xda-developers.com/showthread.php?t=1447303
...and to think that I've "lost" a Vibrant about a year ago because such tecniques had not developed yet (back then we had no CM and the modding scene was all about samsung roms).
If that works, "thanks" on behalf of all those which are in the position that I was in. If only I still had the phone, I would had probably made it working one way or another
Yea luckily for me the phone's internal died about 3 days ago.
Hmm... oddly enough this fixed the internal storage.
This time i made two partitions on the microsd, fat32(6gb) and ext4 (1.6gb)
Flashed to stock through odin. Flashed Overstock through odin(http://cmw.22aaf3.com/aries/sgh-t959/root/cmenard-t959-cwm.tar)
Linda started talking about converting data parition.
After a while it sounded like it stopped converting so i popped out the battery. Took out the micro sd card and oddly enough recovery was booting normally without the card. Flashed to stock again, this time without the micro sd card in, phone booted up, all my old pictures showed up and everything was working perfect. Glad I found this fix, and I hope it works for others.
For reference sake overstock is Cmenard's kernel with ClockworkMod Recovery and voodoo lagfix
ferhanmm said:
Hmm... oddly enough the internal started working again.
Click to expand...
Click to collapse
Good news about this. You are back full and completely. Can you please go to this thread and read the OP and post your findings in it?
The error came up from a phone that was boot looping that was running stock kb5 with the "stock + voodoo kb5" kernel.
I tried flashing stock jfd then ics in attempts to fix the unmountable internal SD data. After that I did receive the encryption bug but only with the initial fix that I applied. But after the second fix I applied the internal was surprisingly brought back to life so I haven't had to deal with the encryption issues yet and I hope never again lol.
Regardless, I'll run those adb commands for you and post them when I see her again. Which should be soon.
ferhanmm said:
Hmm... oddly enough this fixed the internal storage.
This time i made two partitions on the microsd, fat32(6gb) and ext4 (1.6gb)
Flashed to stock through odin. Flashed Overstock through odin(http://cmw.22aaf3.com/aries/sgh-t959/root/cmenard-t959-cwm.tar)
Linda started talking about converting data parition.
After a while it sounded like it stopped converting so i popped out the battery. Took out the micro sd card and oddly enough recovery was booting normally without the card. Flashed to stock again, this time without the micro sd card in, phone booted up, all my old pictures showed up and everything was working perfect. Glad I found this fix, and I hope it works for others.
For reference sake overstock is Cmenard's kernel with ClockworkMod Recovery and voodoo lagfix
Click to expand...
Click to collapse
how did you get this to work. i have followed every step. i did get the encryption error after the first step, but this second step must have been a fluke. i havent even heard lindas voice. what am i missing?
i already have stock jfd, i also have eugenes. i have stock pit. and the sd is formatted as you have it. but still no dice for me.
McBang2023 said:
how did you get this to work. i have followed every step. i did get the encryption error after the first step, but this second step must have been a fluke. i havent even heard lindas voice. what am i missing?
i already have stock jfd, i also have eugenes. i have stock pit. and the sd is formatted as you have it. but still no dice for me.
Click to expand...
Click to collapse
After following my typed up steps you shouldnt receive the encryption error, mine didnt come back after I made edits to the vold.stab file.
The second step may have been a fluke. What I did was.
1. Create two partitions in gparted, fat32(6.0gb) & ext4(1.3gb)
2. Flash to stock JFD.
3. Flash Overstock through odin
4. If linda starts talking after the overstock flash reboot then it worked, if not then it was a fluke and you would have proved that with your test.
please let me know how it goes, or if you want help pm me and we can gchat
ferhanmm said:
After following my typed up steps you shouldnt receive the encryption error, mine didnt come back after I made edits to the vold.stab file.
The second step may have been a fluke. What I did was.
1. Create two partitions in gparted, fat32(6.0gb) & ext4(1.3gb)
2. Flash to stock JFD.
3. Flash Overstock through odin
4. If linda starts talking after the overstock flash reboot then it worked, if not then it was a fluke and you would have proved that with your test.
please let me know how it goes, or if you want help pm me and we can gchat
Click to expand...
Click to collapse
i tried it exactly how you put it. it works fine (the ics fix) but the fix for internal sd card, must have been a fluke. i never even hear linda voice. so you must be extremely lucky.
McBang2023 said:
i tried it exactly how you put it. it works fine (the ics fix) but the fix for internal sd card, must have been a fluke. i never even hear linda voice. so you must be extremely lucky.
Click to expand...
Click to collapse
Hmm thats odd, well i hope after a few days yours starts to work also. And at least your phone is usable with this.
ferhanmm said:
Hmm thats odd, well i hope after a few days yours starts to work also. And at least your phone is usable with this.
Click to expand...
Click to collapse
absolutely. and thanks again
Bump for interest of knowing if anyone else recovered internal memory after doing these steps
So I'm pretty sure I've seen this error. I see it after I odin back to stock from ics...while wiping in recovery. However my internal sd is fine, everything on froyo works. Does this mean my internal is going?
Is there something close to this error I might be mistaking it for? I don't want to go a find out and mess anything up, but I remember seeing the dev/block error...
just not 100% sure it's ---> mmcblk0p1
accordex said:
So I'm pretty sure I've seen this error. I see it after I odin back to stock from ics...while wiping in recovery. However my internal sd is fine, everything on froyo works. Does this mean my internal is going?
Is there something close to this error I might be mistaking it for? I don't want to go a find out and mess anything up, but I remember seeing the dev/block error...
just not 100% sure it's ---> mmcblk0p1
Click to expand...
Click to collapse
If you can access your internal sd after flashing stock jfd, then yes your phones storage is fine.
If you flashed eugenes jk2, check storage if it lists as unavailable then yes its messed up.
i flashed eugenes and it says unavail. but when i flash jfd, my phone never actually boots. its goes to vibrant screen and phone turns off.
McBang2023 said:
i flashed eugenes and it says unavail. but when i flash jfd, my phone never actually boots. its goes to vibrant screen and phone turns off.
Click to expand...
Click to collapse
Can you try flashing my KB5 odin image I make for Moped_Ryder - LINK
If it loads for you... you can try this code to re-format you SDCard *2767*3855#
it's a Full EEPROM Factory Reset with SDCard format.... this WILL delete anything you had on your int SDCard... I use it to get a super clean install to make my Odin images.
fishman0919 said:
Can you try flashing my KB5 odin image I make for Moped_Ryder - LINK
If it loads for you... you can try this code to re-format you SDCard *2767*3855#
it's a Full EEPROM Factory Reset with SDCard format.... this WILL delete anything you had on your int SDCard... I use it to get a super clean install to make my Odin images.
Click to expand...
Click to collapse
i would be willing to try it....but the link is broken. so no valid download.
EDIT: i found a workaround. downloading and flashing now. i will post results later.
EDIT 2: after flashing, the phone does similar to if i flashed stock jfd. the only difference is it will restart after showing the vibrant splash scfeen back to the splash screen. on stock, it completely shuts down.
anybody ever try something like this with samsung tab sph-100..?
or think i could try this? what would i need to change?
I received this tab from someone over ebay and have never once been able to get past samsung boot screen.
I have the same errors in recovery mode, have tried a lot in odin but i came to believe from other xda members that there must be some internal memory / nand chip damage.
I just got an sd card in hopes i could try something with sd card.
Is this what i'm looking for?
mind, I've never worked with android before this.. noob status still.
sender said he never had any issues with it before sending, hoping to take his word for it, i think i can return it if nothing ends up working, but he's caught in hurricane at the moment, so i am willing to work on it a few more days.
wonder if somehow magnets thru shipping could have done something?
I doubt magnets messed anything up. My suggestion is go to the section here in xda for your device and ask your question there. I would also find out if the previous owner had a custom ROM?, if so which ROM. Is it rooted and does it have a custom recovery?
All will be important info to find a fix.
Sent from my SGH-T959 using xda premium
Basically what I need is to use this mod to boot my experimental builds on the external sd w/t wiping my main ROM (which would be installed to my phone). Is that possible?
So that whatever happens I could always boot back to stock (what I will have installed in my phone), with some minor tweaking through adb shell of course. It sounds doable, ain't it?