Related
I have been able to get into CWM Recovery v5.8.0.2 but there are no system files or any files on the phone, i can load new ROM's on the SD Card but every time i install it, it comes back with installation aborted, i have tried multiple different ROM's, any suggestion will be greatly appreciated. The phone does not boot any further
Are you sure youre not flashing a Nexus S 4G rom on a Nexus S. Or the opposite?
I am sure, i downloaded all the correct ROM's from CWM and am sure i have a Nexus S not 4G, it was rooted before and worked fine, i tried getting it back to stock and when it booted, it stopped on the boot ROM, from there i went through the procedure on loading CWM recovery and finally got back into recovery mode but from there i cannot flash anything and as mentioned, there are no file whatsoever on the phone, it is as if it was wiped clean.
Have you accidentally flashed a NS4G recovery by any chance? Try reflashing your recovery.
Also, any other errors listed?
I flashed using the CWM v5.8.0.2-touch on the Nexus S category, so am sure and triple checked and redid the flash a couple of times, its as if the new flash does not find any files to flash and i cannot see any files on the phone, there is only the update.zip file on there
Jpienaar2012 said:
I flashed using the CWM v5.8.0.2-touch on the Nexus S category, so am sure and triple checked and redid the flash a couple of times, its as if the new flash does not find any files to flash and i cannot see any files on the phone, there is only the update.zip file on there
Click to expand...
Click to collapse
try a different recovery, or the non touch cwm recovery.
I loaded v5.0.2.0 from CWM and still the same, it changes CWM but cannot load any new ROM's
Jpienaar2012 said:
I loaded v5.0.2.0 from CWM and still the same, it changes CWM but cannot load any new ROM's
Click to expand...
Click to collapse
dont load from there, flash a new recovery via fastboot.
I only downloaded the recovery file from CWM but loaded it through fastboot, but still the same result
Jpienaar2012 said:
I only downloaded the recovery file from CWM but loaded it through fastboot, but still the same result
Click to expand...
Click to collapse
download from somewhere else and try.
any suggestions on where else i could get it from?
Download stock fastboot.imgs for your specific device. Flash them all = stock and start over
i have also downloaded from nexushacks.com and same result
Sorry, but where can i get the stock files from?
Search Google. Go to official Google site with them. Can't recall the exact URL but it will come up. There is a thread on these forums as well with the links to factory images and instructions if you need them.
PSA. Stay away from nexusshacks. That guy is a tool.
Thanks, will have a look on what i can find
Ihave tried stock and various developers and still no luck, i tried fast boot update from terminal and get
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Any suggestions
Jpienaar2012 said:
Ihave tried stock and various developers and still no luck, i tried fast boot update from terminal and get
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Any suggestions
Click to expand...
Click to collapse
Did you grab your image from here and follow the instructions to start the script?
https://developers.google.com/android/nexus/images
Thanks, this worked and my phone is back to normal again. Don't trust what other people say on the web cause most of the time they give you crap.
I've searched up and down for this and have yet to find a solid answer, so here I am. I have an AT&T One X (Evita), unlocked, rooted and flashed. Currently running TWRP & GooManager for recovery and ROMs and I'm on Viper 3.2.6.
Initially, my choice was to flash CM10, this failed and went into boot loop. So I recovered and tried Viper. No problems....everything installed just fine. However, I'd like a more lightweight OS - Viper is a little too heavy for my tastes. I saw in GooManager yesterday a new ROM, Liquidsmooth (4.2.2) - decided to flash it and the same thing happened as with CM10 - everything went fine through install and then black.....second install attempt resulted in another bootloop.
I recovered back to Viper without issue, but I can't help but wonder why both CM10 and Liquidsmooth fail to install, but suspect I'm missing a certain boot img? Am I correct here?
(I'd post this to the specific ROM forum but don't have enough posts to submit to developer forums - apologies)
originalseven said:
I've searched up and down for this and have yet to find a solid answer, so here I am. I have an AT&T One X (Evita), unlocked, rooted and flashed. Currently running TWRP & GooManager for recovery and ROMs and I'm on Viper 3.2.6.
Initially, my choice was to flash CM10, this failed and went into boot loop. So I recovered and tried Viper. No problems....everything installed just fine. However, I'd like a more lightweight OS - Viper is a little too heavy for my tastes. I saw in GooManager yesterday a new ROM, Liquidsmooth (4.2.2) - decided to flash it and the same thing happened as with CM10 - everything went fine through install and then black.....second install attempt resulted in another bootloop.
I recovered back to Viper without issue, but I can't help but wonder why both CM10 and Liquidsmooth fail to install, but suspect I'm missing a certain boot img? Am I correct here?
(I'd post this to the specific ROM forum but don't have enough posts to submit to developer forums - apologies)
Click to expand...
Click to collapse
Yes there is a sense kernel and one for non-sense roms (aosp)
Usually the dev will have a kernel link posted on their page
If you are hboot 1.14 or higher, and S-on, to be perfectly safe you should extract the boot.img for the ROM zip you are trying to flash, and flash it manually.
Also, be careful installing ROMs with GooManager (or similar apps, like ROM Manager). Not sure if it properly differentiates between the dual and quad core versions of the One X/XL.
redpoint73 said:
If you are hboot 1.14 or higher, and S-on, to be perfectly safe you should extract the boot.img for the ROM zip you are trying to flash, and flash it manually.
Also, be careful installing ROMs with GooManager (or similar apps, like ROM Manager). Not sure if it properly differentiates between the dual and quad core versions of the One X/XL.
Click to expand...
Click to collapse
Is it better to just boot into recovery (TWRP) and go that route, instead of having Goo flash it?
I checked the page where the ROM exists but I'm not seeing a link to any specific kernel. However, I downloaded to ROM again to my desktop just now, unarchived it and now see a 'boot.img" file. So this file.....this gets placed on my sd card, I boot into TWRP and flash it?
If you can point me to a how-to on this, I'd appreciate it - I hate filling boards with asinine questions.
originalseven said:
I've searched up and down for this and have yet to find a solid answer, so here I am. I have an AT&T One X (Evita), unlocked, rooted and flashed. Currently running TWRP & GooManager for recovery and ROMs and I'm on Viper 3.2.6.
Initially, my choice was to flash CM10, this failed and went into boot loop. So I recovered and tried Viper. No problems....everything installed just fine. However, I'd like a more lightweight OS - Viper is a little too heavy for my tastes. I saw in GooManager yesterday a new ROM, Liquidsmooth (4.2.2) - decided to flash it and the same thing happened as with CM10 - everything went fine through install and then black.....second install attempt resulted in another bootloop.
I recovered back to Viper without issue, but I can't help but wonder why both CM10 and Liquidsmooth fail to install, but suspect I'm missing a certain boot img? Am I correct here?
(I'd post this to the specific ROM forum but don't have enough posts to submit to developer forums - apologies)
Click to expand...
Click to collapse
viper doesn't require you to flash the boot image, it does it for your.
For cm10 or liquidsmooth you need to, an easy way is using Flash GUI. its available on the market and xda. you don't need to hook up to a computer to flash boot image, makes things much easier and faster.
originalseven said:
Is it better to just boot into recovery (TWRP) and go that route, instead of having Goo flash it?
Click to expand...
Click to collapse
For flashing the actual ROM, I don't think it matters. I think Goo Manager is still using TWRP, just automating the process.
originalseven said:
I checked the page where the ROM exists but I'm not seeing a link to any specific kernel. However, I downloaded to ROM again to my desktop just now, unarchived it and now see a 'boot.img" file.
Click to expand...
Click to collapse
The boot.img has the kernel in it. They are usually not posted separately in ROM threads. ROMs always contain a kernel, which normally just flashes with the rest of the ROM zip. But hboot 1.14 and above (if you are S-on) prevents the kernel from being flashed in recovery (TWRP). So you need to extract it from the ROM zip manually.
originalseven said:
So this file.....this gets placed on my sd card, I boot into TWRP and flash it?
Click to expand...
Click to collapse
Again, you can't flash boot.img from TWRP, which is the whole point. Couple methods:
1) Leave the boot.img on your PC, and flash using fastboot. See here: http://forum.xda-developers.com/showthread.php?t=1952076
2) Alternately, you can use the app "Flash Image GUI" on the Play Market. With this app, you place boot.img in the top directory of your SD card, then use the app to flash it.
Or you can S-off, and not have to mess with flashing boot.img seperately every time you flash a ROM.
redpoint73 said:
For flashing the actual ROM, I don't think it matters. I think Goo Manager is still using TWRP, just automating the process.
The boot.img has the kernel in it. They are usually not posted separately in ROM threads. ROMs always contain a kernel, which normally just flashes with the rest of the ROM zip. But hboot 1.14 and above (if you are S-on) prevents the kernel from being flashed in recovery (TWRP). So you need to extract it from the ROM zip manually.
Again, you can't flash boot.img from TWRP, which is the whole point. Couple methods:
1) Leave the boot.img on your PC, and flash using fastboot. See here: http://forum.xda-developers.com/showthread.php?t=1952076
2) Alternately, you can use the app "Flash Image GUI" on the Play Market. With this app, you place boot.img in the top directory of your SD card, then use the app to flash it.
Or you can S-off, and not have to mess with flashing boot.img seperately every time you flash a ROM.
Click to expand...
Click to collapse
Awesome - thank you so much. Cleared that up completely.
redpoint73 said:
For flashing the actual ROM, I don't think it matters. I think Goo Manager is still using TWRP, just automating the process.
The boot.img has the kernel in it. They are usually not posted separately in ROM threads. ROMs always contain a kernel, which normally just flashes with the rest of the ROM zip. But hboot 1.14 and above (if you are S-on) prevents the kernel from being flashed in recovery (TWRP). So you need to extract it from the ROM zip manually.
Again, you can't flash boot.img from TWRP, which is the whole point. Couple methods:
1) Leave the boot.img on your PC, and flash using fastboot. See here: http://forum.xda-developers.com/showthread.php?t=1952076
2) Alternately, you can use the app "Flash Image GUI" on the Play Market. With this app, you place boot.img in the top directory of your SD card, then use the app to flash it.
Or you can S-off, and not have to mess with flashing boot.img seperately every time you flash a ROM.
Click to expand...
Click to collapse
Ok, so I looked at this Flash Image GUI on G-Play and the OneX isn't listed as a supported device - is it simply not listed, but is actually supported? For instance, I see this in the reviews...
"I own the AT&T model of the HTC One X (the Evita with a Snapdragon 4 processor) and unfortunately I got it on the 2.20 version. This means that I need to run the "fastboot flash boot boot.img" from my computer if I want to flash a Rom or kernel. It was a pain, I just wanted to be able to download a new Rom whenever and where ever I wanted (I have a very large data cap) and flash it on the go. I can actually do that now it's worked with both AOSP and Sense based Roms, so I'm happy. Great job to the dev "
Failing that, I'll run it from terminal (im on a mac) and assume those same commands apply (but with -mac after bootloader).
originalseven said:
Ok, so I looked at this Flash Image GUI on G-Play and the OneX isn't listed as a supported device - is it simply not listed, but is actually supported? For instance, I see this in the reviews...
"I own the AT&T model of the HTC One X (the Evita with a Snapdragon 4 processor) and unfortunately I got it on the 2.20 version. This means that I need to run the "fastboot flash boot boot.img" from my computer if I want to flash a Rom or kernel. It was a pain, I just wanted to be able to download a new Rom whenever and where ever I wanted (I have a very large data cap) and flash it on the go. I can actually do that now it's worked with both AOSP and Sense based Roms, so I'm happy. Great job to the dev "
Failing that, I'll run it from terminal (im on a mac) and assume those same commands apply (but with -mac after bootloader).
Click to expand...
Click to collapse
flashimagegui is perfectly supported. got support awhile back. [APP] Flash Image GUI - Flash Kernels and Recoveries from normal Android mode!
Hey,
Can I change custom recoveries as if I was flashing them for the first time? Do I need any special care with it? I've flashed CWM, but it isn't the touch version, and this is way nicer to use.
Diogomsb said:
Hey,
Can I change custom recoveries as if I was flashing them for the first time? Do I need any special care with it? I've flashed CWM, but it isn't the touch version, and this is way nicer to use.
Click to expand...
Click to collapse
Yup. Just fastboot or mfastboot flash (whichever one you used) the new recovery and it will overwrite the one you have now. Some recoveries even come in a flashable form so you can flash the zip from your current recovery just like you would any other zip (ie SuperSU).
I recently purchased a Verizon Pixel and successfully unlocked it, installed TWRP RC1, ROM and EX Kernel. I notice, however, that I cannot flash any other zips such as Viper4Android, WETA, etc. This makes no sense to me but after trying to flash these other zips (all of which say successful) nothing is ever installed after a reboot and files do not appear in the expected directory locations. Anyone have any idea what I am missing? I have never seen anything like this before.
Thanks!
bradld said:
I recently purchased a Verizon Pixel and successfully unlocked it, installed TWRP RC1, ROM and EX Kernel. I notice, however, that I cannot flash any other zips such as Viper4Android, WETA, etc. This makes no sense to me but after trying to flash these other zips (all of which say successful) nothing is ever installed after a reboot and files do not appear in the expected directory locations. Anyone have any idea what I am missing? I have never seen anything like this before.
Thanks!
Click to expand...
Click to collapse
After flashings the ROM; do you reboot to recovery before you flash the mods? You need to either reboot to recovery or boot to the system at least once before flashing any mods. When you flash a ROM, it gets flashed to the slot that is currently inactive. The mods will get flashed to slot the is currently the active slot. So, if you don't reboot before you flash the mods, they get flashed to the wrong slot. That's about the only thing I can think of that would cause this issue.
robocuff said:
After flashings the ROM; do you reboot to recovery before you flash the mods? You need to either reboot to recovery or boot to the system at least once before flashing any mods. When you flash a ROM, it gets flashed to the slot that is currently inactive. The mods will get flashed to slot the is currently the active slot. So, if you don't reboot before you flash the mods, they get flashed to the wrong slot. That's about the only thing I can think of that would cause this issue.
Click to expand...
Click to collapse
Yes, have rebooted to recovery numerous times. Zips appear to flash and on reboot to ROM, nothing! Zips with save log features return an error as if nothing is writing to memory.
I have returned to factory image and repeated everything, no change.
I have only booted to TWRP for installing zips, and I haven't installed TWRP on my phone. When booting TWRP RC1, I've had it fail to install zips multiple times. I think the times it failed I didn't get the initial opening information. Honestly I didn't look into it very much, because I just booted Alpha 2, and that installs zips just fine when RC1 doesn't work for me. If someone has rooted their phone, I think FlashFire can probably also install zips.
bradld said:
I recently purchased a Verizon Pixel and successfully unlocked it, installed TWRP RC1, ROM and EX Kernel. I notice, however, that I cannot flash any other zips such as Viper4Android, WETA, etc. This makes no sense to me but after trying to flash these other zips (all of which say successful) nothing is ever installed after a reboot and files do not appear in the expected directory locations. Anyone have any idea what I am missing? I have never seen anything like this before.
Thanks!
Click to expand...
Click to collapse
If you flash a mod from a flash made specially for Pixel, it should work. Other zips will not because the system files for the Pixel are in system/system, not just system.
Every time i tried to flash twrp recovery via Odin it failed or stucked.i tried many times but failed.i reset my phone and try again but again it failed.also changed the data cable but same result.
Note that i tried Izzy12 sir's final and stable recovery.img by making it a .tar format by PeaZip.Help someone to successfully flash the twrp.I want to flash a custom rom.Please help!:crying::crying:
You'll want to check that you have the latest version of Odin. It was necessary with Oreo.
Also, I had a problem making a tar file with the newer TWRPS initially and while it finally worked taking off by making my changing the filename from .tar.mdb to just .tar but before getting this right, I flashed just the recovery part of the following TWRP and not the bootloader part. Notice that its a little buggy but you can go straight from flashing it to flashing the recovery image of the recent version that you want from the image file on the sdcard and reboot to the newer recovery https://forum.xda-developers.com/ga...-j701f-core-nxt-exynos-7870/recovery-t3693009
PantsDownJedi said:
You'll want to check that you have the latest version of Odin. It was necessary with Oreo.
Also, I had a problem making a tar file with the newer TWRPS initially and while it finally worked taking off by making my changing the filename from .tar.mdb to just .tar but before getting this right, I flashed just the recovery part of the following TWRP and not the bootloader part. Notice that its a little buggy but you can go straight from flashing it to flashing the recovery image of the recent version that you want from the image file on the sdcard and reboot to the newer recovery https://forum.xda-developers.com/ga...-j701f-core-nxt-exynos-7870/recovery-t3693009
Click to expand...
Click to collapse
Thank you for replying.But the lates twrp didn't work.so i tried a little bit older and it worked!:laugh:
Thank you again!:victory: