So i figured Multisystem was the solution I was finally looking for: Alliance for a lollipop daily driver, and a kitkat rom ( any really ) so that I can use Viper4Android in the car for music control on long trips.
Got MS installed, sd card partitioned up right, copied an image of my stock install just fine, and booted to the virtual image just fine. Thats where the trouble began...
So i already had a copy of TMS (twiseted monkeys 5.0 rom) on my sd card so I decided to flash this as a test ( figuring if i can get a 5.0 rom to install to the virtual image correctly then I can move on and try to get a kitkat rom running) Loaded up MS and then switched into Flashfire, loaded up my Zip of TMS and flashed away ( with a wipe ahread of time ofcourse, turned out to be a big mistake)
So i read ahead of time that the updater-script makes a big difference on if your stock partition is gonna get touched or not, so I looked into thd zip on TMS and it looked to be setup right so that my stock image didnt get touched.
Flash went fine until i hit 'extracting system' and then froze up completely. ( i let it sit for about an hour justto make sure things werent just taking thier time. I ended up having to battery pull. So at this point of course I just get a hang when trying to boot into the primary virtual image, I expected that since obviously the install did not complete. No biggie, I'll just boot back into the stock image and try to flash again.
No such luck, when I booted into the stock image Fireflash had apparently wiped the data partition of the stock image as well as the virtual one on my sd card. Luckily im pretty good at backing up, But im not thrilled about continuously reinstalling backups endlessly so my main question is:
When I get to the point of flashing the ROM over the loop img, should I be wiping the system and data partitions in Fireflash, or unchecking that option and just wiping delvik and cache?
TL;DR - Flashfire freezes when I try to flash a rom - What am I doing wrong there, AND
When flashing a rom with Flashfire should I be wiping system and data partitions or not?
Related
Ok. One gracious member of this forum is already helping me on PM, but he hasn't signed on in a bit, and I kinda need a working phone, so I'm asking for any help that can be provided. Here's my situation
Went from CM 4.2.1 to 4.2.2 via the CMUpdater. All good. Then, like a moron, I flashed what I thought was the latest Hero theme by Ultra Spikey. I reboot, and it gets stuck on the Android boot screen (I waited about ten minutes, maybe should've waited more). I reboot into AmonRa's Recovery, wipe, and re-flash 4.2.1, which I still had on my SDcard. Goes into an infinite boot loop after loading to the main lock screen. Then, genius me, I wipe three times (data, partition, and davliK) reflash 4.2.1, and now I get Force Close on the setup screen. AndroidAppCritic tells me its cause Ive lost the proprietary Google bits. Needless to say, the phone continuously reboots again. He also tells me I probably just need a Linux swap partition, so I RE-FORMAT MY SDCARD with fat32 and ext2 and swap. Duh. Now I realized I have NO zip files to flash, my sdcard is basically wiped clean. I can't flash to anything because I have no files to flash to, and I can't get the phone to any functional status because it won't get past the setup wizard, so I can't add any zip files to flash.
How screwed am I?
As always I appreciate any assistance from anyone.
Go to the CM 4.2.2 thread, download the HTC update file and the CM 4.2.2 file and put them both on your sd card.
reboot into recovery and flash them both again.
Edit...you can put the files on your sd card by using the mount usb option from amon-ra's recovery.
I have been playing with HC, CM7 etc on my Nook color and decided to go back to running auto-nooker on top of stock, but I want to keep the SD CWR image I made, which has a lot of free space for me to play with future ROM. Has someone packed an CWR zip for auto-nooker?
Thanks.
mathfeel said:
I have been playing with HC, CM7 etc on my Nook color and decided to go back to running auto-nooker on top of stock, but I want to keep the SD CWR image I made, which has a lot of free space for me to play with future ROM. Has someone packed an CWR zip for auto-nooker?
Thanks.
Click to expand...
Click to collapse
BOOM Wining.
http://forum.xda-developers.com/showthread.php?t=932145
therealguppy said:
BOOM Wining.
Click to expand...
Click to collapse
LOL. Thanks.
My current ROM is phiremod nook V4.1. After flashing this and reboot. The Nook U picture flashes, then it's flashing "A N D R O I D _" prompt at the lower left and nothing...
There are three of us currently stuck on that damned android_ screen right now. As I posted in the other one if you get out of this please post your steps!
I reflashed phiremod nook V4.1. That boots pass ANDROID_.
Hmm maybe this is due to CM7 using EXT4 and stock using EXT3,
after flashing the Stock restore also try flash the Restore Boot Partition..
http://forum.xda-developers.com/showthread.php?t=914690
At the bottom of the first post on this one you can find the Restore Boot. which restores Stock B&N boot.
I already did that. Right now as I turn it on, it displays the "Touch the Future of Reading" line instead of the "Loading..." line from CWR. Or do you think this is not sufficient?
There is message when installing repartition-boot-with-stock.zip:
"This will install stock boot 1.0.1 Eclaire --- This won't boot with Froyo!"
Can this the issue too?
EDIT: During the 5 minutes delay b/t post, I installed repartition-boot-with-stock.zip and Nook Color-v1.1.0-r2.zip, now it boots and stucked at the Nook icon with the "Contain Reader Mobile by Adobe" line.
Okay, so I restore stock image, albeit 1.0.1 using images form this page:
http://forum.xda-developers.com/showthread.php?t=919353
Steps:
1. download/extract boot.img and system.img to bootable sdcard (with CWRv3.0.0.6)
2. boot using sdcard, mount /sdcards
3. use adb to dd the image as described in article.
4. repeat failed boot to force recovery.
I thought this would restore /system and /boot ext3 again, but it doesn't...still getting stuck at "ANDROID_" prompt after reflashing the Nook Color v1.1 above. I am going back to CM7...sigh...
EDIT: Actually, it DID work! My problem was when I reflashed Nook Color v1.1-r2.zip, I wiped system and data, which I shouldn't have.
therealguppy said:
Hmm maybe this is due to CM7 using EXT4 and stock using EXT3,
after flashing the Stock restore also try flash the Restore Boot Partition..
http://forum.xda-developers.com/showthread.php?t=914690
At the bottom of the first post on this one you can find the Restore Boot. which restores Stock B&N boot.
Click to expand...
Click to collapse
FYI I've been in the same boat as you a couple of times now with my Nook not wanting to boot. And it seems it gets to different points each time before locking up and not booting. I'm starting to think the same thing as your comments here. This whole ext4 stuff is what seems to be causing issues for a lot of folks specially when wanting to go back to a different ROM or stock. To further compound it is the fact the newest CWR is 3.0.1.0 and all bootable sdcard files are still 3.0.0.6 or 3.0.0.5. With that said I can tell you making a backup using the 3.0.1.0 CWR that is on the internal mem and then getting stuck booting is no good. Reason being from wha tI've found so far is if you take your 3.0.1.0 backup and put it on a bootable sdcard that has 3.0.0.6 so you can restore, it does not work right from what I've found. The only way I've found to fix it easily so far is to first flash the " Remove CWR * .zip from the link posted here. After that then flash the repartition-boot-with-stock.zip file. Once I've flash those 2 files I'm able to flash a new ROM and have it boot like it should.
Another way I've got around it was to power the device on into recovery with no sdcard in the device. Once it booted into recovery ( ie CWR 3.0.1.0 ) I put the sdcard in the device that had my 3.0.1.0 CWR backup. I restored that backup using the actual 3.0.1.0 recovery from internal mem. Once finished tried to boot and it got stuck. When it did I then powered it down and fire it back up but this time booting to the sdcard and then I flashed the repartition-boot-with-stock.zip and it would finally boot up like it should.
Bottom line IMO at least is it seems to be hit or miss on what is the best way to get it back up and running after the boot partition gets hosed. And that can make it a bit frustrating.
Sorry I don't have time to read all of this. Just keep in mind that > 3.0.0.6 formats to ext4 (ie CM). For stock and froyo, use 3.0.0.5 to format to ext2 and 3..
System, data and cache need formatting before flashing a new rom.
Repartitioning boot is only useful if your NC doesn't boot.
Sent from my HTC Desire using XDA App
thought 3.0.1.0 was supposed to work for everything.
My nook color recently got stuck on the boot screen for CM7 where the blue android text just chills out in the left corner. This happened right after my nook ran out of battery power.
I have gotten it to boot all the way into CM7 occasionally. However, it is not reliable at all, so I've tried to restore it to stock and reflash the whole thing.
I tried to do this by booting into recovery and then flashing the restore to 1.01 stock zip file, but when the nook rebooted it was still stuck on the android text. I have tried flashing everything related to restoring nooks, but to no avail.
I thought that maybe my CWR was broken, so I tried making a CWR sd card but even when I flashed the restore zip, my nook's boot still gets stuck on the android text.
What do you think I should try to do now?
You are able to boot into cwr though? If so have you tried downloading the stock image file again? Could be the file is corrupt.
I just downloaded it again and it still doesn't work.
I don't think that the problem is the zip files. I think that CWR is the problem since I've tried formatting /system and /data and tried repartitioning boot, but nothing happens...
I just tried to restore my nook to stock through ADB, but it still tried to boot into CM7. I guess that rules out CWR as the problem...
I also made an ext4 compatible CWR SD and tried the restore 1.01 zip again. This time I got past the android text and instead got to the grey android text from the rooted nook boot. However, it just sat there, stuck in a loop.
Odd, that even after wiping system and data that you'd have anything to boot into. You aren't leaving a bootable sd card in place are you?
I make sure to take out the SD card before rebooting.
Is it possible to check to see if CWR/ADB is actually writing to the correct partitions?
EDIT: I do not think that my nook is keeping any changes that I make to it...
I managed to boot into CM7 and I uninstalled a few apps and changed the max clock to 800mhz. Then I rebooted and eventually got back into CM7 and my apps magically came back and my max clock was reset to 1.1ghz.
okay that is very odd. Unfortunately I've never run into this or even read about it before. Hopefully someone here will be able to give you a tip that will help you fix this.
I've been having same issue for a week now. I tried everything I was able to find here but nothing is wokring. It seems like my nook became a read-only device. No matter what I do it goes back to previous stage.
I was running CM7 RC4 and system hung so I rebooted and that was it. It displays "Android_" on the bottm for about 10-15 sec and reboot.
I tried
CWR 3.0.0.5
- Repratition to stock nook.
- Getting error when I try to format system and data - I thought it was because CM7 was setting system to ext4.
- ADB and DD boot.img, System.img and copy Factory to mmcblk0p3
- Try to restore from back up I made
- Nothing works but goes back to boot loop
CWR 3.0.0.6 - One I got from CM7 install to emmc thread
- System format works
- Install latest nightly
- Restore from back up
- ADB can't find device - This is odd and couldn't find a way to fix it yet.
- Tried to install Stock zip but going back to CM7 boot loop
CWR 3.0.1.0
- Can't format data/system
- ADB to delete partitions and create them again but it doesn't help
- Tried all zip files to bring it back to stock - no go
- ADB to copy Factory.zip to emmc partition - umount and mount again then file I copied is gone.
- Deleted partitions and reboot but some how I got back to CM7 loop
I see people start to talking about CM7 boot loop issue. I saw this thread and man this is same issue I'm having! Let me know if you some how resolved this issue. I will do the same if I can find one.
Naw, I haven't resolved it yet...
I will post the solution if I do though!
Perhaps it's just a coincidence, but I am also stuck running RC4. Maybe there's some weird glitch in RC4 that makes the file system read only or something...?
I went from RC4 to stable with no problem. I did notice that CWR was not mounting the system and data partitions so I did have to do that when updating. Not sure why they aren't mounting automatically.
From the Dummies guide link....Here...
First visit this link:
http://forum.xda-developers.com/showthread.php?t=922870
Download either the Rootpack, or the Clockwork Recovery image (1gb).
Next visit this link and download the 1.0.0 or 1.0.1 restore to stock files:
http://forum.xda-developers.com/showthread.php?t=914690
From this link you should also download the very last zip on the page. It is titled-flashable boot repartition zip. or something of the like. If you followed all these steps and still nothing, I would recommend flashing this as it can fix a completely screwed boot partition.
I had to use that last file after my hard crash. Seems that te /boot gets corrupted and tis seemed to fix it for me. After this you will probably need to do a full wipe and reinstall.
My order was...
rebuild /boot
reflash to stock
reflash to CM7
not sure why this worked...just did.
edit: just noticed my H key isn't always working...makes me type like a alf drunk brit..
deadbot1 said:
From the Dummies guide link....Here...
First visit this link:
http://forum.xda-developers.com/showthread.php?t=922870
Download either the Rootpack, or the Clockwork Recovery image (1gb).
Next visit this link and download the 1.0.0 or 1.0.1 restore to stock files:
http://forum.xda-developers.com/showthread.php?t=914690
From this link you should also download the very last zip on the page. It is titled-flashable boot repartition zip. or something of the like. If you followed all these steps and still nothing, I would recommend flashing this as it can fix a completely screwed boot partition.
I had to use that last file after my hard crash. Seems that te /boot gets corrupted and tis seemed to fix it for me. After this you will probably need to do a full wipe and reinstall.
My order was...
rebuild /boot
reflash to stock
reflash to CM7
not sure why this worked...just did.
edit: just noticed my H key isn't always working...makes me type like a alf drunk brit..
Click to expand...
Click to collapse
I tried this too but mine didn't come back.
Hmm. dunno. Maybe you can get samuelhalff to chime in...he was helping another guy out with something similar. searc in the threads for his name and your problem...wasn't to long ago.
edit---http://forum.xda-developers.com/showthread.php?t=1022941 this was the thread I was talking about...doesn't appear they came up with a solution.
I tried all the things you suggested guys, but nothing worked...
Although I think I made some kind of progress... I tried to dd stock boot.img and system.img files onto my nook and now CM7 just bootloops instead of hangs!
Hopefully we can get this sorted out soon, or else I may try what one member suggested about microwaving it so that you can get a new one...
I tried a long various way, no success and now i can't use my loved nexus.
Everything was working very fine till i used my nexus' sd to flash a rom in a friend's nexus ( his was not working): here started the problem.
After re-putting on my sd on my n1, i lost all data, settings, no apps, no market, no adw..
-Tried to reflash the rom(kang 1.3 which was working perfectly till before): still no market, no adw, stock look, no apps (included in the rom)
-Tried to wipe all data/factory reset, reflash the rom: still no market, no adw, stock look, no apps (included in the rom)
Then i reached to install the 2.3.6 stock rom, which was working: i rooted it with superoneclick, installed rom manager
First i tried to backup with clockwork recovery but it stopped on backing up sd/ext: i had to remove battery and reboot, install ra recovery to have a success in backing up ( in recovery's opinion).
At this point i tried to reflash the rom, but i got stuck on the starting animation which is in loop..
I tried to nandroid restore from ra recovery but it said "Oooops something went wrong"
don't know how to solve, can you please help me? i can't use the phone! (recovery seems to work, have drivers correctly installed)
Ok my guess it's your SD card that has a problem so try making a full wipe (erase on) of your SD card and see what happens.
Dude Random21 said:
Ok my guess it's your SD card that has a problem so try making a full wipe (erase on) of your SD card and see what happens.
Click to expand...
Click to collapse
I'm re-flashing the passimg of stock 2.3.6 which yesterday was working.
again i noticed some problems on boot animation, but it moved on and it seems to works..
should i partition again my sd? Because it works on my pc ( in this way i put into the sd the passimg.zip, so it shouldn't be broken) and i guess maybe it's because of that..
A re partition would be a good idea.
When my sd-ext got corrupt the fat32 portion was fine but ext portion was busted
repartioned sd, still get the problem wtf..
http://pastebin.com/igvgPHSN here is the boot log, hope this'll help you..
thanks!!
I would format card outside phone with sdformatter--I use v2.0? Full Erase and Size Adj ON. Then repartition and swap is 0.
i first tried this:
http://imageshack.us/photo/my-images/38/problems2.png/
and then this:
http://imageshack.us/photo/my-images/23/problems3a.png/
but it didn't solve the problem.
Then i did a full wipe and it worked, i reached to install the rom, BUT missing some pre-installed apps (like adw, facebook, android stock keyboard etc., but with market, gapps et.)
i put this apps on my own and now it's working, but still miss something like the link to "power off", "reboot" , "recovery" etc.
what is going on?
This is related to http://forum.xda-developers.com/showpost.php?p=44237167&postcount=39259
Problem:
Stuck at bootscreen after installing Roboto 4.3 via Rom Toolbox Pro. I'm on ARHD 12.0.
Fastboot erase cache, full wipe, dalvik wipe etc. pp didn't help.
ADB-Sideload also didn't work due to a mysteriously & out of the blue non-mountable internal SD. Something was borked when I installed the new typo, dunno how and why.
So, re-flashing ARHD from my laptop wouldn't work, furthermore I deleted ARHD.zip from my internal SD; but anyway, the SD was to no avail -> no chance to grab a Nandroid.
Solution:
I firstly changed the recovery on my black lady by flashing TWRP in order to substitute CMW. TWRP allowed me to access and mount an USB-OTG, which hasn't shown up on CMW (v6.0.3.4) at all.
So, finally I placed the ARHD.zip on the external drive, mounted the drive and flashed the ROM 2 times, as the first flash freezed on 20%. But then it went throu, the ROM settled down and the bootscreen stuck was gone.