So, using NVFlash and the image files for the Wi-Fi only model, I can not restore my Streak 7.
I've gotten it to work before, using older custom ROMS, but when I try going back from the newer versions of Honeystreak, it won't work.
After flashing over, I can't get past the Dell logo. I've tried everything that worked for me before. When I try to restore it, though, it says "Error mounting /data", so it seems not every part of the system can be accessed.
If I try flashing back over to Honeycomb, it works. So, I can run Honeycomb, but NOT Froyo.
I've gotten it to work before, and don't know why it isn't working now. Any ideas?
you know i had s similar problem well long story short i didn't have all the proper file even though i did download them all i eventually figured out they didn't finish even though it said they did so i would check all your file sizes if you are using the p. files and make sure also don't forget you gotta go into recovery and reset with option 3
Related
I finally got around to flashing a friends zio to 2.2.1 and got a fresh nandroid backup directly after the tethered update. Not rooted, no mods, themes, all bloatware incl.
Download Stock 2.2.1 Nandroid Backup
Use our Clockworkmod Recovery image to flash.
Enjoy.
:'(
Xda should support Android Smileys on the Xda app.
Sent from my Zio using XDA Premium App
link is back up.
If you encounter a md5 sum mismatch, you may need to md5sum the .img files yourself.
MD5 Summer in windows
or
"md5sum <file.img>" command in linux
Once you have your md5 sums, just replace the old ones in "nandroid.md5" with your newly generated ones.
Ok, so I got a new phone and I need to put the stock rom back on my Zio m6000 so that I can sell it because it is no longer use to me. I downloaded your stock nandroid back up, now I need to know how to excatly put it to use. I got all the way up to the prompt screen, but now I'm like now what?! Do I need to put anything on the sdcard or what I have no idea. So please if someone can give me a little more details on the operation on how to restore to stock firmware using your nandroid backup would be great. Thanks in advance
Ricardo
If you just want to restore the M6000 to stock you can always use the updater for Microsoft. You'll need to have the drivers installed and connect via USB, then start the updater. It will reboot the phone into Modem Download Mode and will flash the stock 2.2.1 images.
Sent from my Zio using XDA Premium App
Any other way to go back to stock 2.2 on a Cricket Zio?
This doesnt work for me, Ive tried flashing it in Recovery, it started to flash then rebooted. The old rom was still on the device, but the boot-up screen changed back to Cricket. (That was the only thing that changed.)
When I tried to restore this file using Rom Manager (which I hate), it kept giving me an error: "File Name can't contain spaces" or something to that effect.
Tried renaming the file several times, even just naming it "1.zip" made no difference.
All the roms on this forum are just way to slow compared to the stock rom. The only exception being the 2.1.x Rom here (which runs fast.)
Microsoft Activesunc/Windows Mobile Device Center isnt available to me as Im running Windows 7 64-Bit, the Windows 7 "Sync" program in accessories doesnt even recognize the device.
Fastboot into CWM works tho.
I know this phone pretty much sucks, but my daughter loves to play games and youtube on it, thats all we use it for. Some games arent compatible with Android 2.1..
Thanks!
jasew503 said:
Any other way to go back to stock 2.2 on a Cricket Zio?
This doesnt work for me, Ive tried flashing it in Recovery, it started to flash then rebooted. The old rom was still on the device, but the boot-up screen changed back to Cricket. (That was the only thing that changed.)
When I tried to restore this file using Rom Manager (which I hate), it kept giving me an error: "File Name can't contain spaces" or something to that effect.
Tried renaming the file several times, even just naming it "1.zip" made no difference.
All the roms on this forum are just way to slow compared to the stock rom. The only exception being the 2.1.x Rom here (which runs fast.)
Microsoft Activesunc/Windows Mobile Device Center isnt available to me as Im running Windows 7 64-Bit, the Windows 7 "Sync" program in accessories doesnt even recognize the device.
Fastboot into CWM works tho.
I know this phone pretty much sucks, but my daughter loves to play games and youtube on it, thats all we use it for. Some games arent compatible with Android 2.1..
Thanks!
Click to expand...
Click to collapse
Although I havent booted this phone up for years, I still disagree. OpenZio ROM far surpasses the stock ROM in performance, benchmarks and snappiness.
But if you are insistent on returning to stock, try formatting /system in CWM's advanced settings, then flash the backup.
Alternately, you can always run the 2.2.1 update to restore to a completely stock, unrooted system.
http://forum.xda-developers.com/showthread.php?t=966047
Spz0 said:
Although I havent booted this phone up for years, I still disagree. OpenZio ROM far surpasses the stock ROM in performance, benchmarks and snappiness.
But if you are insistent on returning to stock, try formatting /system in CWM's advanced settings, then flash the backup.
Alternately, you can always run the 2.2.1 update to restore to a completely stock, unrooted system.
http://forum.xda-developers.com/showthread.php?t=966047
Click to expand...
Click to collapse
The "2.1.x" rom I was quoting in my previous post was the OpenZio rom, and yes it performs extremely well. Just no App to SD ability, among other limitations. Phone runs great with it however. Every other rom ive tried 2.2.x (except stock) seems to be generally very slow, and slow at recognizing screen input (almost a whole second from touching the screen until it actually recognizing there is a touch, which is hard very work with), and the screen's touch input seems to be uncalibrated somewhat. Ill try "formatting /system" then flashing the backup, but I guess the question I should have originally asked was: Do I flash this zip as I would any other custom rom from the SD? (Install Zip from SD>Select this ZIP). Im not familiar with the ZIO as I use T-Mobile, but I assume since its CW Recovery and it would be the same, right?
How do I perform the mentioned: "run the 2.2.1 update to restore to a completely stock, unrooted system."?
If I go to Settings/About/Update it says I need to be on Wifi, which it is (The phone's not activated). Ive tried doing that with every available rom in the forum.
UPDATE:
Just tried this, however when I choose to install this ZIP from SD, it starts to install, and within a half second goes back to the Recovery main screen.
Nothing changes (Except that I formatted everything)
so i am having trouble getting cwm to flash an update.zip on my GFs new streak 7. anywho my only reason for wishing to do so is i want to load the wpa_supplicant fix as we both run tethering apps on our phones (barnacle) for all our portable connectivity. I have a gtab and tinker with my OS all the time. not to say i am a guru...just smart enough to really screw myself on occasion but i have yet to fully brick anything. Give time i say!!! lol
So while i got CWM working after a romp though online android forums i could not seem to get as far as my update.zip actually working. when i try to run one i get an error from CWM saying i need to edify my code for compatiblity. So i found used amend2edify....while i did not get the edify error with my new update.zip it supposed converted for me...i still got errors and the install still aborted just for differant reason.
I prefer not tinker with my wpa files directly though i am aware that is another solution to my problem using root, busy box and adb/or file manger. Tried that once (or a billion times) with my gtab and i only ended up back at NVflash every time.
So does anyone know a way to recompile my update.zip's that has had the same issue with cwm 3.0.1.9 ??? i'll take any ad-hoc fix for wifi but it would be nice to know i can do update.zips for my GF's tablet like my gtab.
So Ive rooted many times switching back and forth and updating various roms. I always use "unleash the Beast" for rooting. This morning I decided to try out the Serendipity 7 so I cleared everything with Odin and when I placed the "Unleash" file on my phone (as update.zip) it will not install? There used to be a re-install packages file on my phone and Id just hit that and id be rooted, that wasnt there and just selecting the actual file from re-boot mode doesnt work either. When I Odin'd this time did I somehow get a newer version of a stock Rom or something? I'll Odin again and see if I did something different, just posting this in the mean time.
dont mind me. Looks like I used a different version of Odin than normal and it gave me a 2.3 Droid which didnt have the re-install packages included.
Phone: HTC Hero, CDMA
Carrier: Sprint
While others have reported of this problem, the solutions that worked for them dont work for me. Im really stuck.
I know, its an old and slow phone, but I was hoping to go to CM7 to get better performance out of it. Well, I must have done something wrong in the process. My current android version is 2.1-update1. I used z4root to root it and used the clockworkmod ROM manager to install a recent nightly after backing-up my current ROM. Installing the nightly failed, something to do with the zip, but my phone had already been wiped and rebooted in default factory mode. I tried doing the install again with the same nightly and a more recent one, but it kept failing due to a problem with the zips. After one of the reboots, the OS just wouldnt load; seems to be looping on the 'HTC quietly brilliant' screen. I am able to boot in recovery mode, but cant figure out how to get past this looping issue.
Ive tried booting using the back-up I created with no luck. Ive even tried going through the RUU process (cant post a link cause Im a new member here), which results in an error message stating that theres an incorrect bootloader.
I did figure out that I was trying to install CM7 using the wrong zip; had the GSM version. Ive tried installing CM7 with the correct zip, but, after reboot, it loops at the animation with the android on the skateboard and the blue arrow around it. Not sure what it means that the two different OSs loop at, what looks like, the same points.
I probably did something wrong, but Im hoping somebody with a better understanding of all thats involved can let me know if there is any way for me to fix this. Thanks in advance for the help.
grins1 said:
Phone: HTC Hero, CDMA
Carrier: Sprint
While others have reported of this problem, the solutions that worked for them dont work for me. Im really stuck.
I know, its an old and slow phone, but I was hoping to go to CM7 to get better performance out of it. Well, I must have done something wrong in the process. My current android version is 2.1-update1. I used z4root to root it and used the clockworkmod ROM manager to install a recent nightly after backing-up my current ROM. Installing the nightly failed, something to do with the zip, but my phone had already been wiped and rebooted in default factory mode. I tried doing the install again with the same nightly and a more recent one, but it kept failing due to a problem with the zips. After one of the reboots, the OS just wouldnt load; seems to be looping on the 'HTC quietly brilliant' screen. I am able to boot in recovery mode, but cant figure out how to get past this looping issue.
Ive tried booting using the back-up I created with no luck. Ive even tried going through the RUU process (cant post a link cause Im a new member here), which results in an error message stating that theres an incorrect bootloader.
I did figure out that I was trying to install CM7 using the wrong zip; had the GSM version. Ive tried installing CM7 with the correct zip, but, after reboot, it loops at the animation with the android on the skateboard and the blue arrow around it. Not sure what it means that the two different OSs loop at, what looks like, the same points.
I probably did something wrong, but Im hoping somebody with a better understanding of all thats involved can let me know if there is any way for me to fix this. Thanks in advance for the help.
Click to expand...
Click to collapse
I *think* your error, in general, was using a bunch of "easy" one click methods and not properly learning (READING) about what the proper steps are. Here is my advice (assuming you are still rooted) -
1.boot into recovery (power off phone, hold home button, press power)
2.wipe data/factory reset
3.mounts/storage - wipe system and boot
4.restore nand backup OR flash ROM/gapps (from the same thread)
5.reboot, and be patient, bootup could take 5-10 minutes.
Good Luck.
You are the man (or woman)! I believe the formatting of system and boot is what did it. Really appreciate the help.
grins1 said:
You are the man (or woman)! I believe the formatting of system and boot is what did it. Really appreciate the help.
Click to expand...
Click to collapse
It is important, as Il Duce said, that you definitely do a good amount of reading when you want to get involved in rooting your phone. You are opening yourself up to some great innovation and fun, but you can also cause yourself a lot of headaches.
Recovery is your friend. If you can get into that, at least you know things are ok. I like to wipe (or format) system, data, cache, and boot 3x just to make sure that clockwork recovery cleaned everything and there are no dingleberries from the last rom I was using.
Flashing the correct type of rom is even more important. Don't flash a gsm rom to a cdma phone and NEVER flash a gsm radio to a cdma phone. Once you delve into the reading aspect of XDA, you will see that is the sure way to brick your phone.
Some roms take longer than others to boot up. Let it run its course. Sometimes it will reboot right after installing. At some point, you might want to make a nandroid of the new rom you are running and go back to your stock (2.1 update 1) and update your PRL, baseband, etc. (if you haven't done an update in a while).
Have fun, that is the most important part and we seem to have a lot of it here in HeroC XDA land.
You know, I put in a fair share of reading about how to update the ROM on my phone and I was under the impression that it would be fairly simple. I figured that since this has been done for quite a while and all these tools have been developed, I wouldnt need to know what happens on the back end during a root or ROM install.
But I did get myself into a bind that I wasnt able to figure out on my own. And with the help of this forum, I was able to get past my problem. Im glad to say I now have a phone that is functioning very smoothly with CM7 and the apps I need.
Next step for me is figuring out how to save my apps to the SD card so that I can install from there if/when I update my ROM in the future.
Thanks again for the help!
Get titanium backup FTW.
BANG! from my shooter...
ive had the phone since at&t had it on display. rooted it and had various roms for the last couple years and never had any serious issues. last night i flashed jellycream v2 and then did a factory reset inside the rom. the phone prompted that it would reboot twice and that it was normal. it rebooted into twrp and did nothing afterwards. i rebooted it from the recovery and all it did was reboot back into recovery. i decided to flash a different version of twrp and still the same. then flashed clockwork and still got the same result. i wiped the bootloader and basically went through the rooting process again. flashed the latest version of twrp and the phone is still only booting into recovery.
i am at a loss because this is as far as my knowledge goes. its like the phone is stuck still trying to wait for that factory reset from the jellycream rom or something and it wont do anything else but load TWRP.
If factory hard reset will not work (with phone off, press power and volume up together for some seconds. You might want to try also holding home on the touch screen.) flashing firmware will fix it unless you have hardware failure, which I doubt.
http://forum.xda-developers.com/showthread.php?p=39269819
Part 1 can be tricky, so take your time and get that right before proceeding.
drastic00 said:
If factory hard reset will not work (with phone off, press power and volume up together for some seconds. You might want to try also holding home on the touch screen.) flashing firmware will fix it unless you have hardware failure, which I doubt.
http://forum.xda-developers.com/showthread.php?p=39269819
Part 1 can be tricky, so take your time and get that right before proceeding.
Click to expand...
Click to collapse
so far i get the grey LG screen with 'booti mmc_read xxxx' at the upper left with the hard reset. it only takes 2 seconds to show up but the phone shuts off if i continue to hold the power and volume buttons. ill read up on that link here.
I missed that you wiped bootloader. You need that . So you could maybe just install the wkpark bootloader in recovery. You would do 1 and 3 here (1.25a file is down the page)
http://forum.xda-developers.com/showthread.php?p=39130435
I think Jellycream actually requires you have it, if I remember correctly.
Not sure why factory reset would cause that issue, but it will definitely not start without bootloader.
Flashing firmware will also write the (stock) bootloader if that does not do it. It will also reinstall the OS if system is corrupt or missing.
I can't find the thread for Jellycream2. Would you post a link? Are you sure it is for P920/P925 (same device, one is AT&T branded. I have the Thrill P925). If it is not for those device numbers, you may need xbsall's unbrick guide.
Also, if Jellycream2 is based on ICS and you were on a GB ROM, you would likely have needed to first upgrade to ICS and then install the ROM.
I'm just trying to understand why a factory reset could brick your phone...
drastic00 said:
I can't find the thread for Jellycream2. Would you post a link? Are you sure it is for P920/P925 (same device, one is AT&T branded. I have the Thrill P925). If it is not for those device numbers, you may need xbsall's unbrick guide.
Also, if Jellycream2 is based on ICS and you were on a GB ROM, you would likely have needed to first upgrade to ICS and then install the ROM.
I'm just trying to understand why a factory reset could brick your phone...
Click to expand...
Click to collapse
ok basic rundown of what i did in the last year;
when first played around with rooted it about a year ago i used all-in-one to do it. i had already upgraded to ics using the lg mobile support tool prior to rooting. rooting went off fine until i installed a Beats Audio app from the play store. when the phone rebooted after it would be stuck at the grey LG logo. i didnt know what to do so i used twrp and wiped the whole phone. then i used all-in-one and flashed the ICS bootloader and did the flash kernel 4 fix or something its one of the last options to do. then using twrp i flashed ICS_V20_P20, Stock_V20P_Rooted, and a Thrill Update, the phone rebooted fine in an ICS rom but it ran like complete ****, so i tried various roms and the one i settled with was called OptimusRS V1. i used that up until 2 days ago when i flashed the jellycream rom.
after i factory reset that i tried to flash the different wkpark bootloader and twrp that came with the megatron tool hoping that would fix the issue. but it did so i reflashed the original twrp and ics bootloader from all-in-one.
failed to mention this before but i tried 3 different recovery files in between each attempt and it would flash and reboot fine but the phone would still do the same thing and just load recovery.
ill find links when i get off work today. thats the basic history of the phone though.
Hmm. Stil not sure then . Maybe a corrupt zip or you wiped something important. Flashing with LG Flashtool should recover it. And always make a Nandroid backup before installing anything from recovery.
http://forum.xda-developers.com/showthread.php?t=2392309
thats the jellycream rom.
im downloading the files for your xbsa rom at the moment. i do remember yesterday when i used the megatron tool i saw an option to flash the stock bootloader and recovery. i tried it but all i got was the pink LG logo then a security error message below it and the phone shut off.
Oh, ok, OptimusRS's ROM.
Hmm, I thought v20 was GB or something... If it is not ICS then that would be the problem. Also it does say there you need wkpark bootloader for that ROM.
Also, xbsall's v28B includes recovery but it is in system partition. I don't know if that ROM requires you install it from recovery partition or not.
If you still want Jellycream you should be able to flash xbsall's ICS v28B (the normal partitions one, not large partitions), then install wkpark bootloader 1.25a in recovery, then the ROM.
drastic00 said:
Oh, ok, OptimusRS's ROM.
Hmm, I thought v20 was GB or something... If it is not ICS then that would be the problem. Also it does say there you need wkpark bootloader for that ROM.
Also, xbsall's v28B includes recovery but it is in system partition. I don't know if that ROM requires you install it from recovery partition or not.
If you still want Jellycream you should be able to flash xbsall's ICS v28B (the normal partitions one, not large partitions), then install wkpark bootloader 1.25a in recovery, then the ROM.
Click to expand...
Click to collapse
well that breaks down that a bit better. my progress at the moment is step f6. when i connect the phone nothing installs though. it just reconnects and disconnects every second or so. im guessing its because i already have those files. dunno though. i cant get my pc to install the adb drivers for the life of me when the phone is connected in recovery mode.it sees the new hardware just cant find the files.
actually i got it. for some reason the phone wouldnt install anything until i put the battery back in at that step. i continued successfully to step M. the phone is setting up my google account at the moment.
will flashing the baseband be necessary if my apn and sim work like the phone is now? my provider is h20(canadian i heard) but im the usa.
HUGE thanks regardless
Cool :thumbup::beer:
The no battery part is just for driver install, which is fiddly for this phone. Sometimes trial and error is a factor.
The baseband you have now would be the one you had previously. If it works, no problem. The one in the v28B pack is supposed to be optimized for the v28B .bin file, but hey, whatever works.
drastic00 said:
Cool :thumbup::beer:
The no battery part is just for driver install, which is fiddly for this phone. Sometimes trial and error is a factor.
The baseband you have now would be the one you had previously. If it works, no problem. The one in the v28B pack is supposed to be optimized for the v28B .bin file, but hey, whatever works.
Click to expand...
Click to collapse
im only getting E for data. i tried to flash a baseband meant for at&t but it says failed after about 90 seconds. still no 4g though. i did flash the xbsav8 before i set my apn up. i might just go with an optimusRS rom again though. i was happy with it. probably not jellycream this time.
Baseband fail after 80 or so sec is normal. It means it worked. Check your baseband in android settings/about phone.
You might try speed test app to compare actual speed. ATT 4G icon is a lie on this phone IMO.
Now that your pc is set up you can flash any P925/920 bin. Kdz files (combo of bin and fls, there is another tool for flashing those files) can be extracted into separate bin and fls, but I have not done it. The advantage is you can flash baseband separately.
Xbsalls vX3D (see his page) with the P925G fls file gives me 4G icon on Straight Talk in the US, but I like his vR3D better, and I can't tell a speed difference, honestly.
I have not actually measured the speed in either, however.
And for either of those ROMs, you must flash his large partition version of v28B first...very important.
oh its definitely like 2g speeds. its pretty slow. i tried using my providers app and website and its saying the phone i have isnt registered to them anymore so it might be just that. if thats the case ill just bring it in so they can do that for me. when i rooted it the first time i wasnt getting any data and they had to re-register the phone to get it to work right.
my baseband says OMAPP4430/XMM6260. for comparison and/or confirm differences. i have no idea lol.
side question though; my sdcard still has recovery files for the optimusRS v1 rom i had on it. i really liked the setup i had when i made the recovery for it. Im tempted to reinstall it but im really not too sure if itll work or worse harm my phone again.
Lots of variables, but you must remember that xbsall's P940 recovery app he he uses has recovery in system partition. The recovery you had before was probably in recovery partition. They write restores from two different places. Probably you would get an error, but not positive. Understanding that may take some Googling...
If you try it, back up before trying to restore the old backup. Then you could hopefully restore if the restore fails, know what I mean?
Probably the safest thing is to use the all in one tool to install recovery in recovery partition and use that one to restore backup.
I do know when I have restored backups, I have wiped Dalvik, Cache, and Factory Reset (in recovery) and then restore. Then it works. Some people wipe system too.
You can usually flash to recover from a problem, but then you have to set your phone up again
Well I recovered everything. All settings and personalized stuff. Just everything. Everything is running normal again. Just now my data is saying im using an h20 microcell instead of just H20 with a 4g connection. This 2g stuff is for the birds. I'm almost thinking the firmware we flashed has something to do with it. The phone is functional though. Just slow and no mms. I haven't been able to find much on the forums about it. I'll poke around more tomorrow.
Sent from my LG-P920 using xda app-developers app
I'd try another baseband.