So I was messing around with my Kindle Fire trying to get the first 3.0 kernel/rom build to work before we all found out it was a display panel issue and I was messing around with fastboot wiping. I managed to get it to fastboot wipe after several failed attempts however after doing so whenever I booted into recovery (twrp 2.1.0) and mounted usb storage I would double click the kindle fire under my computer and recieve a message that I needed to format the drive before I could use it. I couldn't get past the screen and into the device and tried to get in several times before I finally let windows format it, thankfully it appears to only have formatted the sd-card partition. Now instead of having 5.0 gb of free space I have 4.99gb of free space when it's completely empty, I also clicked use device defaults on the windows format screen hoping that it would be somewhat helpful. I know it was stupid to do but now my question is, will this be a problem and if so how do I return to normal state in reference to my partitions. I tried "fastboot oem format" and it didn't appear to do anything. I'd appreciate any help/advice you guys have to offer.
----------------EDIT----------------
So it appears that now after a twrp wipe I have 5.0 out of 5.0 gb free, i'm still a little concerned since windows did wipe the sd card in order to use it after my fastboot wipe experiments, however everything does appear to be working well now.
As long as you format it to a fat32 format you should be fine. The best way to do it is through recovery. But you should be fine
Sent from my Kindle Fire using Tapatalk 2 Beta-5
Related
Where to begin...
So I based my install off of this YouTube Video: youtube.com/watch?v=88qRbLLEAPQ and after I got done following everything to the T, I was not able to format /data. I feel this may be my problem. After doing all the steps minus that one I tried to install CM7 and it would boot the second time around in CM7 (Something I read was common). IT would get the the skateboard screen and then it would just stay there with the arrow continuously looping around and around. I let if sit for quite some time before I had to power it off.
I called up my buddy who told me I would more then likely have to install it manually with the Android Developer tools (Or whatever he called it). I did not have those tools so I kept poking around online. I found that sometimes the SD card caused problems so I bought a new 4Gb class 4 card. This was not the issue.
I poked around alittle more in CWR and I accidentally formatted /boot. The unit froze up so I restarted it. It booted into CWR just fine and after trying to wipe the /system, /data (Still not working) and /cache and rebooting, it has now just turned to a black screen that I can't even boot from a card.
Now before I just cash in on my protection plan, What can I do to get this running again? I hate having a paper weight sitting on my desk..
Thank you so much!
tl;dr, Tried to install CM7, can't format /data, tried new card and re installing, accidentally formatted /boot and now it won't boot at all.
Honestly, I can't watch Youtube at work so I am clueless what instructions you are following.
1. What version of your NC? 1.2? 1.1? 1.0?
2. What version of CwMR?
3. You tried to install CM7 in the eMMC or uSD?
I don't know which Nc it is... I just got it 2 weeks ago today.
I do believe that the cwr was 3.0.0.3 or something like that... it was supposedly the newest.
and it was the latest stable version of CM7.
My problem now is that my computer has totally crashed and it won't start in safe mode even. I am fairly sure it has something to do with having the files on my computer.. I just have to get that part figured out, then I can get the rest of it working..
Latest CW is 3.2.0.1 if I recall.
I know when I leave my imaged microsd card in my adapter on the laptop that the laptop won't boot. You don't have the card in an adapter on the system do you?
Also, I assume you are trying to install CM7 to internal memory?
You have to use CWR v. 3.2.0.1. Earlier versions will not wipe/clear everything. Do that and you should be ok....
If it has been around 2 weeks ago, then it most likely be v1.2 which you need CwMR v3.2.0.1, which reportedly fixes the format /data issue.
Give it a try again.
Ok, got the Nook to boot back to the Nook software. Won't get past the loading screen, but atleast it is booting..
I got my computer working finally after booting in Safe mode and deleting all the zip files and images from the computer. So now I am back to a clean slate.
Where do I get CWR 3.2.0.1? And then where do I get the CM7 latest release? I feel like I should be listening to you guys rather then listening to the YouTube video.. It was nice to see things happen on there, But it did not work for me.
Thank you guys SOOO much for having this forum and the "How to fix the black screen" tutorial! I would be lost without it!
So yesterday I rooted my Atrix and loaded CM7 on there. Everything was going fine. I then started seeing errors saying that my SD was unmounted or not found while in the OS. I tried looking it up and all I could find was that I should try formatting so I wiped everything off it, didn't work. So now I went into ClockworkMod recovery to reset to factory and now it's not booting up to the OS at all. It just sticks at the logo screen where it says "Unlocked". I am able to get back to recovery screen but that's it. I can't access the SD card at all because it's empty and it can't find it.
Anyone have any ideas as to how to fix this?
Reinstall CM7. you can enable USB mode from recovery, just copy the CM7 zip back on from your computer, and you should be good to go.
Znichols513 said:
So yesterday I rooted my Atrix and loaded CM7 on there. Everything was going fine. I then started seeing errors saying that my SD was unmounted or not found while in the OS. I tried looking it up and all I could find was that I should try formatting so I wiped everything off it, didn't work. So now I went into ClockworkMod recovery to reset to factory and now it's not booting up to the OS at all. It just sticks at the logo screen where it says "Unlocked". I am able to get back to recovery screen but that's it. I can't access the SD card at all because it's empty and it can't find it.
Anyone have any ideas as to how to fix this?
Click to expand...
Click to collapse
Did you wipe the internal or external?
If I were you I would do a complete fastboot wipe and flash another ROM. That way you eliminate a bunch of possible problems.
When I try to mount USB storage, it says "Unable to write to ums lunfile (No such file or directory)"
Also, I wiped the internal one. I don't have an external SD. And how do I do a fastboot wipe?
Do you think it might work if I got an external SD card and put the files on there? Then try to flash CM7 from it?
Ok I have a big problem here and need help fast... I rooted my Kindle quite awhile ago and installed a IcS rom.. It worked perfectly...i had back ups for the Stock and ICs rom on TRWP so I got a new rom Ics with kernel 3.0 or something... flashed it worked perfectly...... but i went to flash it again in Twrp i went to WIPE and did factory reset but SOME how i clicked Sd card it removed everything I was very very scared.......I go back to restore nothing is in there i go to install everything is gone Idk what to do how am i gona get a rom in here to flash please help me... i dont wanna lose my kindle fire
I bricked a kindle fire pretty bad but was still able to get a working rom on there after using firekit and the usb boot mode trick. Was able to install firefirefire and twrp using ubuntu on a usb stick and some motherboard shorting. I'm still waiting for my factory cable to arrive in the mail but found this trick while waiting.
Firekit:
http://forum.xda-developers.com/showthread.php?t=1430038
Usb boot mode trick:
http://forum.xda-developers.com/showthread.php?t=1405052
Was pretty scary because I accidentally touched a paperclip to a power source and caused a spark on the kindles motherboard but apparently nothing was damaged. Just make sure you stay away from the ribbon cable below the shorting point.
This is a last resort for when you can't even adb shell into your device.
tombombman said:
I bricked a kindle fire pretty bad but was still able to get a working rom on there after using firekit and the usb boot mode trick. Was able to install firefirefire and twrp using ubuntu on a usb stick and some motherboard shorting. I'm still waiting for my factory cable to arrive in the mail but found this trick while waiting.
Firekit:
http://forum.xda-developers.com/showthread.php?t=1430038
Usb boot mode trick:
http://forum.xda-developers.com/showthread.php?t=1405052
Was pretty scary because I accidentally touched a paperclip to a power source and caused a spark on the kindles motherboard but apparently nothing was damaged. Just make sure you stay away from the ribbon cable below the shorting point.
This is a last resort for when you can't even adb shell into your device.
Click to expand...
Click to collapse
Doesn't sound very smart to me, I wouldn't fudge with my motherboard
Sent from my Amazon Kindle Fire using XDA
7r3d said:
Ok I have a big problem here and need help fast... I rooted my Kindle quite awhile ago and installed a IcS rom.. It worked perfectly...i had back ups for the Stock and ICs rom on TRWP so I got a new rom Ics with kernel 3.0 or something... flashed it worked perfectly...... but i went to flash it again in Twrp i went to WIPE and did factory reset but SOME how i clicked Sd card it removed everything I was very very scared.......I go back to restore nothing is in there i go to install everything is gone Idk what to do how am i gona get a rom in here to flash please help me... i dont wanna lose my kindle fire
Click to expand...
Click to collapse
I'm sure you've figured out by now that you've deleted everything on your /sdcard partition. What you need to do now is "format" that area again. You can do this in one of two ways...
1) Use TWRP's Mount -> Mount USB Storage feature to get mount onto your computer's OS. It will ask you to format... you should be OK after that.
2) If that doesn't work out for some reason, you'll have to use parted to "make filesystem" which is just "format" in linux-speak...
http://forum.xda-developers.com/showthread.php?t=1424784
You can follow the directions in there to get it done, but it might ask a couple of times what partition and what filesystem type you want. It's always going to be 12 and fat32 for those questions. Don't mess with anything but partition 12. Type "quit" to get out of the "parted" program.
If you don't know how to use adb, read the posts in this guide...
http://forum.xda-developers.com/showthread.php?t=1552547
I suggest you read it from the beginning, but the information you need is mostly located in the 3rd post.
Hey, I said it was a last resort. I probably should have waited for the factory cable but i'm impatient. It all worked out though.
It should have just reformatted the sdcard partition. Try to mount usb from twrp and copy a Rom to flash.
Sent from my Amazon Kindle Fire using xda premium
brizey said:
It should have just reformatted the sdcard partition. Try to mount usb from twrp and copy a Rom to flash.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
The shortest recommendation (the one above), is the right one.
I don't know wth tombombman was talking about, that relates nothing to a formatted SD card
TRY to find the smallest possible OS install in megs. It'll increase the likelihood that a SD card data recovery program might be able to find your old backups, should it NOT be overwritten by any new data that's created on the SD card.
HI All,
i'm newbie on this site and I've run into a scenario that I am unsure of what to do now. I believe that I may have soft bricked my Acer Iconia A200. Here is what happened:
[*]- My tablet is US, 64gb and on ICS ROM
[*]- Tried One Click tools to root, unlock bootloader and install CWM (Successful)
[*]- I then ventured in installing a custom rom
[*]- I panicked when I did not do a NAND Backup/ Wipe before flashing and my tablet froze when installing the custom ROM
[*]- My tablet is now stuck on the ACER Screen
[*]- Tried superwipe- did not work stuck on /data
[*]- Tried flashing Stock ROM WW/PA, was able to go to ICONIA TAB Screen but stuck
[*]- Factory reset, thru tiny hole and the three button manipulation step did not work. error on erasing user data
[*]- Tried AROMA, Flashed Ultrabase and my tab now boots and was able to start!.............................. BUT
MY INTERNAL STORAGE IS ONLY 66MB and it's always full! Therefore I cant download/install anything. I can still browse via wifi so that's fine. Also rebooting the device acts as if it was always it's first run (asking for gmail account, setting up time and everything)
So, Here is what's working and my main issues:
- Recovery (Thor, TWRP, CWM) works
- Fastboot and ADB also works
- Can mount everything but /data. Working SD and USB (Flashdrive plugged in works)
- Internal Storage always full and only 66MB!
Here is what I've tried already:
- ADB, mke2fs (I read somewhere that if data cant be mounted/reset, we can do this) but it is stuck at 50-60/224 when writing inodes
- Hard Resets (via phone itself(since I got it running), via pin hole, via power + volume up + toggle lock) error on userdata
- Wipes on recovery mode (superwipe, format on thor, twrp and cwm does not work freezing on data or can't mount data at all)
- Fastboot erase (-w, userdata, data) did not work, invalid argument
I am really thinking the data partition (/dev/block/mmcblk0p8) needs to be fixed, it can't be mounted, but adb still sees it (i tried fdisk shows it 29 GB, /dev/block/mmcblk0 still shows 32GB. I just dont know how to use fdisk in ADB to partition or something)
Any thoughts guys? You help would be greatly appreciated!
Update
Still not working. AS a workaround I tried the swap internal memory to SD card hoping that it would work (completely ignore the corrupted? 32GB) but i cant install apps and still boots as if it was first boot. I can however, take pictures download stuff but not install it. So I reverted back.
BY the way, when connecting my Tab to PC, the internal memory's file system is Hiererchical, is that normal? Is there any way for me to repartition/reformat my internal storage?
Thanks
akokokoy said:
Still not working. AS a workaround I tried the swap internal memory to SD card hoping that it would work (completely ignore the corrupted? 32GB) but i cant install apps and still boots as if it was first boot. I can however, take pictures download stuff but not install it. So I reverted back.
BY the way, when connecting my Tab to PC, the internal memory's file system is Hiererchical, is that normal? Is there any way for me to repartition/reformat my internal storage?
Thanks
Click to expand...
Click to collapse
Hey man, I have the exact same problem did you make any move progress with your tablet??????????
Have you had any success at all? My Acer a200 has been bricked since the end of November, and I've been feverishly trying to find a solution (in my opinion, there should be a way to dual-boot to a real linux OS, but I can't even boot into android further than the "iconiatab" logo, so that's out of the question). I've looked at all the solutions concerning my softbricked a200, but nothing can really be applied if I can't get adb to work. Is there any help out there?
kerijan2003 said:
Have you had any success at all? My Acer a200 has been bricked since the end of November, and I've been feverishly trying to find a solution (in my opinion, there should be a way to dual-boot to a real linux OS, but I can't even boot into android further than the "iconiatab" logo, so that's out of the question). I've looked at all the solutions concerning my softbricked a200, but nothing can really be applied if I can't get adb to work. Is there any help out there?
Click to expand...
Click to collapse
Mine became softbricked around the same time. I've been looking around for solutions since then, and nothing has come up. I really feel like taking the tab and have someone video me smashing it on the ground. I am so frustrated that i can't get this thing fixed.
Yesterday my N7 'crashed' on me...
Device Info: N7 32gb non-3G, Android 4.2.1, Rooted via Toolkit, Stock, CWM v6.0.1.0 (non-touch), Bootloader 4.1.3 Unlocked (of course)
Recent changes: I had initially installed a 2nd account for my son to play games on without messing up my progress shortly after 4.1.2 launched... I immediately noticed that the N7 seemed more sluggish but put up with it so he would have his own account. Well he hasn't used my N7 for weeks and I hoped that maybe if I uninstalled that 2nd account that the sluggishness would go away... So a few days ago I went into settings and removed it... Not sure if it made a big difference. I only mention this because I am not sure if it had anything to do with what happened yesterday...
The Crash: Yesterday when I came home with my N7 I heard some notifications letting me know that it had logged into my home wifi and had connected with Gmail... About an hour later I went to use the tablet and when I hit the power button I briefly saw the wallpaper and unlock pattern. Almost immediately the wallpaper disappeared and was replaced by blackness. I could still see the unlock pattern and then the screen 'shifted' - got smaller, bigger and then bam... the tablet reset. This whole thing took just a few seconds.
After that it seemed to be stuck at the nexus logo/animation... I assume it was stuck in a boot loop. I let it go for a good 30 minutes and nothing changed... still had the animation. At that point I did the following:
So I rebooted into the bootloader and rebooted from there... same result.
So I rebooted into the bootloader and then recovery and rebooted from there... same result.
I gave up in frustration and powered it off from the bootloader and went to bed.
Today I went back into recovery and did a Nandroid backup. It gave me no options, it just did a full backup. Based on the amount of free space that was reported it seemed as if my SD card partition was intact. Up to that point I didn't know if the glitch maybe wiped everything out...
After that I formatted the /cache, /system and /data (not sure of the order). Then I tried rebooting and now it won't go past the Google screen with the unlock icon.
So I went back into recovery to see if I had a zip that I could flash. The only one there on my SD card that I can find is the CWM/Superuser one from the toolkit. That file is named CWM-SuperSU-v0.94-signed.zip and is in the root directory. I checked and the Nandroid backup seems to be where it should be...
So I figured that I need to flash the factory image but cannot seem to mount the N7 via USB. When I plug it in my Windows 7 machine, Win 7 lets me know that it has installed the "Nexus ADB" driver that my N4 installed and seems to be connected. But there is NO /USB in the Mount menu in Recovery and Windows 7 doesn't see the N7 from the My Computer/Windows Explorer.
My Questions:
Do I need to 'push' a stock image via ADB?
What ADB command do I type to see if the N7 is in-fact accessible from my Windows 7 machine?
I am assuming that when I formatted the three partitions mentioned above I wiped the boot ability of the N7. Is that why it won't go past the Google screen now?
Did I do anything wrong in what I've done so far?
Thanks in advance!
OldDogEyes said:
Yesterday my N7 'crashed' on me...
Device Info: N7 32gb non-3G, Android 4.2.1, Rooted via Toolkit, Stock, CWM v6.0.1.0 (non-touch), Bootloader 4.1.3 Unlocked (of course)
Recent changes: I had initially installed a 2nd account for my son to play games on without messing up my progress shortly after 4.1.2 launched... I immediately noticed that the N7 seemed more sluggish but put up with it so he would have his own account. Well he hasn't used my N7 for weeks and I hoped that maybe if I uninstalled that 2nd account that the sluggishness would go away... So a few days ago I went into settings and removed it... Not sure if it made a big difference. I only mention this because I am not sure if it had anything to do with what happened yesterday...
The Crash: Yesterday when I came home with my N7 I heard some notifications letting me know that it had logged into my home wifi and had connected with Gmail... About an hour later I went to use the tablet and when I hit the power button I briefly saw the wallpaper and unlock pattern. Almost immediately the wallpaper disappeared and was replaced by blackness. I could still see the unlock pattern and then the screen 'shifted' - got smaller, bigger and then bam... the tablet reset. This whole thing took just a few seconds.
After that it seemed to be stuck at the nexus logo/animation... I assume it was stuck in a boot loop. I let it go for a good 30 minutes and nothing changed... still had the animation. At that point I did the following:
So I rebooted into the bootloader and rebooted from there... same result.
So I rebooted into the bootloader and then recovery and rebooted from there... same result.
I gave up in frustration and powered it off from the bootloader and went to bed.
Today I went back into recovery and did a Nandroid backup. It gave me no options, it just did a full backup. Based on the amount of free space that was reported it seemed as if my SD card partition was intact. Up to that point I didn't know if the glitch maybe wiped everything out...
After that I formatted the /cache, /system and /data (not sure of the order). Then I tried rebooting and now it won't go past the Google screen with the unlock icon.
So I went back into recovery to see if I had a zip that I could flash. The only one there on my SD card that I can find is the CWM/Superuser one from the toolkit. That file is named CWM-SuperSU-v0.94-signed.zip and is in the root directory. I checked and the Nandroid backup seems to be where it should be...
So I figured that I need to flash the factory image but cannot seem to mount the N7 via USB. When I plug it in my Windows 7 machine, Win 7 lets me know that it has installed the "Nexus ADB" driver that my N4 installed and seems to be connected. But there is NO /USB in the Mount menu in Recovery and Windows 7 doesn't see the N7 from the My Computer/Windows Explorer.
My Questions:
Do I need to 'push' a stock image via ADB?
What ADB command do I type to see if the N7 is in-fact accessible from my Windows 7 machine?
I am assuming that when I formatted the three partitions mentioned above I wiped the boot ability of the N7. Is that why it won't go past the Google screen now?
Did I do anything wrong in what I've done so far?
Thanks in advance!
Click to expand...
Click to collapse
Use this tool to connect via adb and restore stock+unroot then after re-lock the bootloader, this will give you the same state as when the tablet left the factory then re-root and start over
http://www.wugfresh.com/nrt/
Oli1122 said:
Use this tool to connect via adb and restore stock+unroot then after re-lock the bootloader, this will give you the same state as when the tablet left the factory then re-root and start over
http://www.wugfresh.com/nrt/
Click to expand...
Click to collapse
Will I lose the SD partition?
My Nandroid backup isn't backed up anywhere else...
That was the first thing I was going to do after connecting the dead N7 to my Windows 7 machine...
Nervous about that aspect!
Thanks
OldDogEyes said:
Will I lose the SD partition?
My Nandroid backup isn't backed up anywhere else...
That was the first thing I was going to do after connecting the dead N7 to my Windows 7 machine...
Nervous about that aspect!
Thanks
Click to expand...
Click to collapse
Yes locking and unlocking your bootloader will wipe all data as far as Im aware. I dont know how viable your Nandrid backup would be regardless though. It was made after the boot looping errors occurred right? That would probably mean restoring a back up from that time frame would reapply all those errors. You could try to pull your nandroid back up using adb to see if theres anything salvageable from it and Id redo everything on your device. Heres a link to a bunch of useful ADB commands which may help ya out. ADB useful commands
cjsspape said:
I dont know how viable your Nandrid backup would be regardless though. It was made after the boot looping errors occurred right? That would probably mean restoring a back up from that time frame would reapply all those errors.
Click to expand...
Click to collapse
That is true. As you can tell I am semi-knowledgeable but not as proficient as many.
So I thought that the Nandroid backup was divided into different pieces... And that I could choose which pieces to restore and by doing that, just restore the portion of my tablet that represented the 'setup' (apps, layout, etc) but not the OS... Maybe I'm wrong about that...
As for ADB, yes, I thought about that as well and already did an ADB Pull to grab the Nandroid ... now I'm doing one to grab everything on the SD Card.
Thanks for that!
Yeh you should be fine so long as you backup your sd before hand. You can also use the same nexus tool to backup your apps and restore them using the developer tools backup