Related
Ok, I want to leave a message on here for future noobs like me with a Galaxy S
i9000 but it might work for others too.
My issue when flashing custom roms is that I have not been able to access my galaxy from my computer via usb since literally day 1 (when it did work once).
I spent a week trying to connect to Kies on multiple computers (vista and Windows 7). Tried via Android SDK, even tried hiemdall. I almost tried in ubuntu also but I never did get that working as I really don't know linux well enough. I've now given up...
So then I saw that you can do flashing all on the phone with the clockwork mod. With clockwork, my first rom flashed, well, like clockwork! But then I had some issues with lag and hang ups and reception and I decided to switch to another rom (seearms jl2 based rom - good stuff so far).
However this rom install went sideways... It said that it had installed ok but on reboot it stalled on the Galaxy I9000 screen and froze. Luckily I could still use the 3 button recovery to boot to clockworks but the hitch was that I HAD NO OTHER ROM to flash back to.
I had done a backup through clockworks but when I tried to restore it said the systems.img file was missing so it skipped it and the end result was the same freeze.
Normally everone says to reflash at this point with odin but that was not an option for me. So this is where I got lucky. The SeeARMs rom included Steam recovery module (though I thought it was the stock 3 button recovery menu for a while - I was panicking a little). I highly recommend seeing if you can get steam because it allows access to the External SD card for flashing which can be a lifesaver. Ahh, finally I could get the old rom on that, reflash it and go one with my life. My theory being that at least the issues would be aligned with the this rom and it worked.
So the lessons I learned:
1) Always have your new rom and your old rom on the interanal SD card in case of issues.
2) check your nandroid backup - even try testing it? - they don't always work perfectly with every device.
3)I highly recommend finding out if Steam or similar will work if you cannot access the USB connection and load things on when things go wrong.
Some tips I saw that also worked for me
1) flash a new kernel before you flash a new whole rom.
2) if things go sideways, try redownloading or retransferring the file to make sure there were no errors.
I did both and then reflashed (with my old rom Voodoo Doctor, SeeArms Rom and Darky's 8.1 rom on the card just to have options) and all was good!
PS: the steam recovery knocked off the first letter of the file when executing for some reason so I had to make 2 copy's of each rom I wanted access to ie Darkysrom.zip and arkysrom.zip just look for that error when you are doing this.
Good post - hopefully it'll help someone out who's stuck.
Hopefully
I'd like to stick some of that in on the thread for your rom but I need put another 7 half relevent messages out there before I am worthy... I understand the rule but I'd rather only post where it is meaningful...
GF
Hi all,
Need help with my phone... :\
So I wanted to install ICS on my phone today (http://forum.xda-developers.com/showthread.php?t=1492957) and I looked at the instructions, obviously you have to have a stock ROM installed first before going for the ICS update. At this time I had CM7.1 installed. So I chucked the files on my SD Card to install (the ICS and Stock) and went ahead into clockwork recovery to try and install the stock ROM first. This didn't work, as at the time I didn't know you have to install it via the pink screen and extract the zip folder and put the dload folder in the root of the sd card. So when I tried to install it, it said starting installation, and then would say installation aborted, I had no idea why, so I tried another couple of times, still didn't work. I then updated my clockworkmod recovery to the latest version for the U8800 and it still didn't work (as I was obviously doing it wrong...). I also happened to have an update for CM7 on the SD card that I never got around to installing (7.1.0.1), and so I tried to install that and again it said installation aborted (not sure why that didn't work, should of...). So then I thought, that's odd, nothings working, betcha the ICS ROM won't install either, see if something else is wrong, so I pressed install... and it started installing... not exactly what I wanted or was expecting. So it seemed to install alright with no errors, so I did a reboot out of recovery. It then stuck on the white Huawei logo screen and just stayed there... some folders got created on my SD card (apps that I had installed on CM7), no idea why, it didn't seem to boot, left it for 5 minutes and still just the white logo screen.
So I then did some more reading and learnt that I needed to put the official ROM's dload folder to the root of the SD card and install it via the pink screen. I tried this, unpacks it fully and completes step 1, but it gets to step two, and 5 seconds later after it starts attempting to install the ROM it says, Installation Failed.
So I was looking around for people who had a similar problem as me, and found some, they found a way to fix it which was to put the dload folder in the root of the internal SD card, unfortunately I have no idea how to get to that when the phone doesn't boot up into the OS. I tried putting it in the internal storage via the pink screen, but that's only 200-250MB in size, and the file needs around 300MB, so there wasn't enough room. I tried repartitioning the storage hoping this would increase it, or return it to normal (as I had partitioned it before to the 1.42GB/1.12GB partition that others had posted up previously) and it didn't change a thing. So I have no idea how to get to internal storage D:
Not having fun so far... so I thought I might try and install CM7 again, and then go to stock, and then to ICS, or maybe just leave it on CM7 and give up for now. Unfortunately the version of CM7 I had isn't available anymore, and the newer version you have to have stock ROM installed first, so I decided to grab oxygen instead. Downloaded it and chucked the zip folder onto my SD card and tried to boot into recovery (Power+VolUp) and now it won't even go into that! It goes to the pink screen (Power+VolUp+VolDown) without any issue and I can connect to the computer and access the files on there.
So basically, I've bricked my phone and I would love it so much if you could help me get it back, I really don't want to have to go back to my old Nokia 2760 (http://www.gsmarena.com/nokia_2760-1975.php) where the speaker doesn't even work, so if I make/receive a call, I have to put it to loud speaker or headphones to actually hear their voice... would be much appreciated.
Thanks,
Gunny
I think you have some hope left if you can go in the pink screen mode. You should find some istructions from general section and Q&A section. If you can go to pink screen you should be able to install official Huawei rom.
Pressa00 said:
I think you have some hope left if you can go in the pink screen mode. You should find some istructions from general section and Q&A section. If you can go to pink screen you should be able to install official Huawei rom.
Click to expand...
Click to collapse
I finally got it all sorted, if it wasn't for that pink screen, I'd be stuffed!
I had to go back to a 2.2.1 ROM before it would finally accept it and install. Had a bit of cache and corruption, but android eventually cleared/cleaned itself and put itself back to normal. Now I've got the official version of Gingerbread on my phone, and I'm not sure if I should upgrade to the official version of ICS or whether I should upgrade to Aurora's (http://forum.xda-developers.com/showthread.php?p=22682229#post22682229) version of ICS. Thoughts? And don't worry, this time I won't screw it all up!
Thanks all!
Alright, just discovered my official ICS ROM is for the U8800 pro, not the standard one, so I guess I will be going for Aurora!
Gunny007 said:
This didn't work, as at the time I didn't know you have to install it via the pink screen and extract the zip folder and put the dload folder in the root of the sd card.
Click to expand...
Click to collapse
I have a Huawei U8860 and wants to go from custom rom MIUI to stock rom B925. Can I just follow your advice here and install it via the pink screen?
My N7 has been getting laggier recently - accepting the 5.1.x OTA updates was clearly a bad idea, and possibly the 5.0.x ones. So I have been thinking of giving it a new ROM after this past weekend.
Last night, it started bootlooping, getting to the initial 'swipe to use' main screen but not accepting any touches and then crashing to a restart after a few seconds regardless.
I long ago used the Nexus Root Tool Kit to root it and install TWRP. The most recent OTA 5.1.1 update involved an update to TWRP to version 2.8.6.0. So let's install a new ROM!
I can boot into TWRP and, while there, the NRTK will also talk to the Nexus 7 over USB.
In both of them, plus a console using fastboot commands, I can wipe and format partitions. By telling TWRP to use 'rm -rf' rather than formatting, I can also get its partition repair info to think, for a while, that the partition in question is empty. But looking again reveals that it's just as full as it used to be and indeed, whether or not the formatting, flashing and installing a .zip file appears to work - including fastboot commands reporting success - no files appear to actually change on the device. NRTK will believe it has successfully installed the latest 2.8.7.0 TWRP or any ROM, but rebooting finds the old ones still there. Even all my data is there, despite repeated wipes and reformats, including to different file systems.
What can I try next? At the moment, I am just grateful that this happened before I'd tried installing a new ROM because I'm not blaming myself for all this.
lovingboth said:
What can I try next? At the moment, I am just grateful that this happened before I'd tried installing a new ROM because I'm not blaming myself for all this.
Click to expand...
Click to collapse
It's now not powering up at all. Whatever it is, it looks terminal.
Poo.
Over the weekend my Nexus 4 decided not to start. Saturday night it was working, and I hooked it up to charge. By Sunday morning it had turned off. When I restarted it, it got as far as asking for my password (encryption key), and then the four circles just danced around for hours. After letting it sit for a few days, the phone started again. But the experience made me decide it was time to update the system from Kit Kat.
So, more or less, I followed the instructions on the Team Android site. (As a new member of this forum, I'm not allowed to include the link. But Google "Update Nexus 4 to Android 6.0.1 Pure Nexus Project Marshmallow Custom ROM.") The main differences were (1) I only copied the ROM file over and (2) I used TWRP instead of CWM for the recovery. I was having trouble copying the Gapps file, so I thought it would be easier to install Marshmallow first and do the apps later.
Everything was backed up and copied around 7 PM yesterday, when I then wiped the data, did a factory reset, wiped the cache, wiped the dalvik cache, and finally started the installation. It's now almost 1 AM, and the ROM is still being flashed.
What should I do next?
Well it seems like the ROM you downloaded is a corrupt zip file.
I would like you to go to Original Development and download one of the ROMS from there, and then google opengapps, choose, ARM>6.0.1>Pico package (or any other package of your choice). I recommend Pico for your first install which is barebones google play services and Google Play store.
TWRP is perfectly compatible with most recent roms.
And for 6.0.1 , Flash the ROM and then flash GAPPS right away. After flashing, wipe dalvik/cache and then reboot.
If you have any questions, do not hesitate to post them here. good luck
EDIT: If you want Vanilla android with zero modifications, get this one:
http://forum.xda-developers.com/nexus-4/development/rom-6-0-android-marshmallow-pure-aosp-t3220900
Also, if it helps, I got 4 hours of Screen On Time on this ROM, I never got it on any other ROM so it is very light and is exactly what you would be getting on a nexus device.
mohsinkhan35 said:
Well it seems like the ROM you downloaded is a corrupt zip file.
I would like you to go to Original Development and download one of the ROMS from there, and then google opengapps, choose, ARM>6.0.1>Pico package (or any other package of your choice). I recommend Pico for your first install which is barebones google play services and Google Play store.
TWRP is perfectly compatible with most recent roms.
And for 6.0.1 , Flash the ROM and then flash GAPPS right away. After flashing, wipe dalvik/cache and then reboot.
If you have any questions, do not hesitate to post them here. good luck
EDIT: If you want Vanilla android with zero modifications, get this one:
http://forum.xda-developers.com/nexus-4/development/rom-6-0-android-marshmallow-pure-aosp-t3220900
Also, if it helps, I got 4 hours of Screen On Time on this ROM, I never got it on any other ROM so it is very light and is exactly what you would be getting on a nexus device.
Click to expand...
Click to collapse
Thanks, Mohsinkhan35. I followed the link you included and downloaded the ROM and TWRP 3.0.0-0, as the site requires. (I currently have TWRP 2.7.1.0 installed.) I was unable to download the Pico Gapp from that site, since the link seems to be broken. No problem. It's available from lots of locations.
So, as I understand it, my first step should be updating TWRP. I found instructions on how to do this at PhoneArena.com. Although written for Windows users, basically one starts the phone in bootloader mode and then uses adp commands to flash the new recovery (TWRP file).
But now Android File Transfer is not connecting to the phone. I wouldn't expect it to connect if the phone wasn't booted, as the file system is encrypted. Nonetheless, I tried this way without success. Then I tried using bootloader mode, with similar results. I then booted up in RM and got into TWRP, but AFT still doesn't see the phone. This is not altogether unexpected. If the new OS has settings and drivers to connect to my computer (a Yosemite iMac), and I've wiped the old one to make way for the new install, then how can the phone communicate with the PC?
For each of these cases (normal start, bootloader, and RM), I also tried issuing "adb devices" from a command prompt, but it's also returning nothing.
So any suggestions for the next step?
Von Neumann said:
Thanks, Mohsinkhan35. I followed the link you included and downloaded the ROM and TWRP 3.0.0-0, as the site requires. (I currently have TWRP 2.7.1.0 installed.) I was unable to download the Pico Gapp from that site, since the link seems to be broken. No problem. It's available from lots of locations.
So, as I understand it, my first step should be updating TWRP. I found instructions on how to do this at PhoneArena.com. Although written for Windows users, basically one starts the phone in bootloader mode and then uses adp commands to flash the new recovery (TWRP file).
But now Android File Transfer is not connecting to the phone. I wouldn't expect it to connect if the phone wasn't booted, as the file system is encrypted. Nonetheless, I tried this way without success. Then I tried using bootloader mode, with similar results. I then booted up in RM and got into TWRP, but AFT still doesn't see the phone. This is not altogether unexpected. If the new OS has settings and drivers to connect to my computer (a Yosemite iMac), and I've wiped the old one to make way for the new install, then how can the phone communicate with the PC?
For each of these cases (normal start, bootloader, and RM), I also tried issuing "adb devices" from a command prompt, but it's also returning nothing.
So any suggestions for the next step?
Click to expand...
Click to collapse
NEVERMIND!!!!
Experimenting with several different USB cords and ports finally yielded a good connection! Even a native USB port on the back of the iMac didn't work, and neither did some of the ports on my USB 3.0 (2.0 compatible) hub. But finally one worked, and I ran with it. Currently reinstalling my apps on the shiny new Marshmallow system!
THANKS Mohsinkhan35!!!!!
Von Neumann said:
NEVERMIND!!!!
Experimenting with several different USB cords and ports finally yielded a good connection! Even a native USB port on the back of the iMac didn't work, and neither did some of the ports on my USB 3.0 (2.0 compatible) hub. But finally one worked, and I ran with it. Currently reinstalling my apps on the shiny new Marshmallow system!
THANKS Mohsinkhan35!!!!!
Click to expand...
Click to collapse
Sorry about the late reply Von I just saw your replies, I am glad that you got it to work!!
For Future purposes, The easiest way to update TWRP is to download the .img from TWRP, put it on your phone, go to TWRP recovery, and instead of flashing .zip file, choose .img from dropdown list, then select the image file, select recovery option from the list.
Enjoy your new system! Which MarshMallow ROM did you end up flashing?
I found that MM breathe a new life into my Nexus, can't imagine going back to Lollipop, I don't know how you managed to stay with KitKat haha
So I've finally mustered up some courage to flash something fancy into my X720, and this is what happened. Up until flashing the ROM itself ([ROM] [TREBLE] [8.1] [Official] AICP 13.1 (Pro3 aka zl1, zl0, X727,X720,X722) by mosimchah) it went relatively well, but then I got twrp error 7. After some tweaking error message changed to "failed to mount '/system' (invalid argument). Can it be because I've wiped "system" before flashing? I think instructions said to do so... Anyway now I'm stuck, because even though I made a twrp backup, I was smart enough to remove it from the phone and now I can't put it back, because one of the files is 4gb in size, and I get error message when trying to copy it to phone storage (file system indicates "generic" or something along those lines). I'm new with this kind of stuff, so I really could use some advice. Should I flash stock rom? If so, which version? I can't remember exactly which was mine. I wonder if there's something to be done with that 4gb recovery file? And how did twrp mess up like that? Shouldn't it be calculated more carefully?
TheOkMan said:
So I've finally mustered up some courage to flash something fancy into my X720, and this is what happened. Up until flashing the ROM itself ([ROM] [TREBLE] [8.1] [Official] AICP 13.1 (Pro3 aka zl1, zl0, X727,X720,X722) by mosimchah) it went relatively well, but then I got twrp error 7. After some tweaking error message changed to "failed to mount '/system' (invalid argument). Can it be because I've wiped "system" before flashing? I think instructions said to do so... Anyway now I'm stuck, because even though I made a twrp backup, I was smart enough to remove it from the phone and now I can't put it back, because one of the files is 4gb in size, and I get error message when trying to copy it to phone storage (file system indicates "generic" or something along those lines). I'm new with this kind of stuff, so I really could use some advice. Should I flash stock rom? If so, which version? I can't remember exactly which was mine. I wonder if there's something to be done with that 4gb recovery file? And how did twrp mess up like that? Shouldn't it be calculated more carefully?
Click to expand...
Click to collapse
You can use a SD card or a USB otg and a flash drive for your backup
Sent from my PH-1 using Tapatalk
clsA said:
You can use a SD card or a USB otg and a flash drive for your backup
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
Thanks for the tip, clsA. Gave me quite a push. However, here what happened next: with USB OTG I was able to move the missing 4gb file to the phone storage and recovered my phone to a fully working state (wasn't able to recover directly from USB - anyone knows why? Maybe because it's ntfs?). Thinking I've established a good pivoting point I proceeded flashing custom ROMs. First time I did everything the same. The result was same, obviously. Then recovery. Then I tried leaving *system* out of wiping process and switched my ROM from AICP to DotOS. Installation went through without errors, but the ROM wasn't working correctly. SIM card wasn't recognized, HOME and DETAILS capacitive buttons wasn't working, couldn't download apps from play store, some crashing here and there. I though I had enough, and decided to recover for the time being, but when I did that upon boot up I got *ENCRYPTION UNSUCCESSFUL* error. There's restore system option under it, but it doesn't help. Tried recovering again - same. Reflashed DotOS - got my SIM recognized, but all other bugs remained. I think I'm doing something wrong when flashing, but can't figure out what. There isn't that many steps, and I followed them through... Even tried removing first lines of that script file (in ROM zip file) to get rid of that error 7 at the beginning of AICP installation, which didn't do anything (there's also a chance I've deleted wrong lines, or not all of them..). Maybe someone had similar problems and could share some ideas? And that Encryption error is very strange. Nothing changed after first recovery, so why I'm getting it? All the directories are in ex4 format. Any thoughts about this one?
TheOkMan said:
Thanks for the tip, clsA. Gave me quite a push. However, here what happened next: with USB OTG I was able to move the missing 4gb file to the phone storage and recovered my phone to a fully working state (wasn't able to recover directly from USB - anyone knows why? Maybe because it's ntfs?). Thinking I've established a good pivoting point I proceeded flashing custom ROMs. First time I did everything the same. The result was same, obviously. Then recovery. Then I tried leaving *system* out of wiping process and switched my ROM from AICP to DotOS. Installation went through without errors, but the ROM wasn't working correctly. SIM card wasn't recognized, HOME and DETAILS capacitive buttons wasn't working, couldn't download apps from play store, some crashing here and there. I though I had enough, and decided to recover for the time being, but when I did that upon boot up I got *ENCRYPTION UNSUCCESSFUL* error. There's restore system option under it, but it doesn't help. Tried recovering again - same. Reflashed DotOS - got my SIM recognized, but all other bugs remained. I think I'm doing something wrong when flashing, but can't figure out what. There isn't that many steps, and I followed them through... Even tried removing first lines of that script file (in ROM zip file) to get rid of that error 7 at the beginning of AICP installation, which didn't do anything (there's also a chance I've deleted wrong lines, or not all of them..). Maybe someone had similar problems and could share some ideas? And that Encryption error is very strange. Nothing changed after first recovery, so why I'm getting it? All the directories are in ex4 format. Any thoughts about this one?
Click to expand...
Click to collapse
follow instructions posted here > https://forum.xda-developers.com/showpost.php?p=77813881&postcount=793
clsA said:
follow instructions posted here > https://forum.xda-developers.com/showpost.php?p=77813881&postcount=793
Click to expand...
Click to collapse
Thanks again, clsA. Looks like this could be it. Will try it soon. For now I have flashed [ROM][X72X][7.1.X][OFFICIAL] LineageOS 14.1 (which is now 8.1 somehow...) and it works without any issues so far.
Any insights on why I'm getting *Encryption unsuccessful* error after restoring my original system image via TWRP (first recovery was fluent, error appeared following my later attempts for recovery)?