so just rooted my HOX last night using the new 2.20 method
finally got the bootloader unlocked and installed twrp
figured out how to use twrp and tried to install paranoid rom...
from what i read on another thread i was to extract the boot.img from the rom zip and flash that boot.img from the pc
then restart in recovery/twrp and install the paranoid rom zip
restarted my phone and got to the loading screen for the paranoid rom but just hags
restarted in recovery/twrp and restored my backup
for some reason the restore didn't work and got the endless boot
went back into twrp and did a factor wipe which i think also removed my backup (which didn't work the 1st time anyways)
so now what lol? help.. basically all i can do now is get into twrp - is there a stock backup file i can use to restore from twrp?
you always need to "fastboot flash boot boot.img" from bootloader anytime you are flashing a new rom or backup you are restoring, but you should already know this if you could read.
also make sure you flash gapps if you are flashing a aosp rom.
also NEVER factory reset in bootloader which will corrupt your sdcard.
what you need to do now is what i said above, then rewipe everything in twrp, mount your sdcard in twrp and copy a rom from your pc to your sdcard, unmount sdcard from pc then unmount from twrp, then you can install rom and gapps if its a aosp rom. if you didnt already "fastboot flash boot boot.img" you can reboot into bootloader and run the command instead of reboot system.
DvineLord said:
you always need to "fastboot flash boot boot.img" from bootloader anytime you are flashing a new rom or backup you are restoring, but you should already know this if you could read.
also make sure you flash gapps if you are flashing a aosp rom.
also NEVER factory reset in bootloader which will corrupt your sdcard.
what you need to do now is what i said above, then rewipe everything in twrp, mount your sdcard in twrp and copy a rom from your pc to your sdcard, unmount sdcard from pc then unmount from twrp, then you can install rom and gapps if its a aosp rom. if you didnt already "fastboot flash boot boot.img" you can reboot into bootloader and run the command instead of reboot system.
Click to expand...
Click to collapse
yeah i did the fastboot flash boot boot.img for the paranoid rom - i think my problem was that i left the boot.img in the zip
rezipping now and trying to mount
goot tip on the factor reset from bootloader to bad i already did it lol
i have never modified the actual rom zip before and have never had a problem. it just takes a little longer to install. i am a md5 junkie and never modify offical releases.
DvineLord said:
you always need to "fastboot flash boot boot.img" from bootloader anytime you are flashing a new rom or backup you are restoring, but you should already know this if you could read.
also make sure you flash gapps if you are flashing a aosp rom.
also NEVER factory reset in bootloader which will corrupt your sdcard.
what you need to do now is what i said above, then rewipe everything in twrp, mount your sdcard in twrp and copy a rom from your pc to your sdcard, unmount sdcard from pc then unmount from twrp, then you can install rom and gapps if its a aosp rom. if you didnt already "fastboot flash boot boot.img" you can reboot into bootloader and run the command instead of reboot system.
Click to expand...
Click to collapse
k think the sdcard is corrupt since i did do the factor reset from bootloader..
getting unable to mount sdcard
failed to do a system wipe because of this as well
:crying:
Plug it in to.computer.and enter twrp. When comp recognizes it, it'll ask to format the disk drive (sdcard).. then use instructions above
sent from my venom injected, blazingly fast as f#&k OneXL via xda premium
InflatedTitan said:
Plug it in to.computer.and enter twrp. When comp recognizes it, it'll ask to format the disk drive (sdcard).. then use instructions above
sent from my venom injected, blazingly fast as f#&k OneXL via xda premium
Click to expand...
Click to collapse
worked..
setting up cm10 right now but i dont have a recovery backup to fall back on
how do i go about doing this or should i just make a backup of the cm10 rom in twrp
probably in backup =)
Good job bro. Just *dont* do anymore factory resets in bootloader. Enjoy the Roms. Be careful with cm10 though. I been hearing of a few glitches in it. If anything arises, ask first and don't freak out
sent from my venom injected, blazingly fast as f#&k OneXL via xda premium
InflatedTitan said:
Good job bro. Just do do anymore facto resets in bootloader. Enjoy the Roms. Be careful with cm10 though. I been hearing of a few glitches in it. If anything arises, ask first and don't freak out
sent from my venom injected, blazingly fast as f#&k OneXL via xda premium
Click to expand...
Click to collapse
*don't *factory
DvineLord said:
*don't *factory
Click to expand...
Click to collapse
Lol, edited
sent from my venom injected, blazingly fast as f#&k OneXL via xda premium
So far so good with latest cm10 nightly.. Only crashed once when loading camera.
Now how do i get the default software back on my phone as a backup? Download 2.20 ruu.. Flash.. Then backup in twrp.. Then re flash cm10 from backup?
Sent from my One X using xda app-developers app
silent1643 said:
So far so good with latest cm10 nightly.. Only crashed once when loading camera.
Now how do i get the default software back on my phone as a backup? Download 2.20 ruu.. Flash.. Then backup in twrp.. Then re flash cm10 from backup?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Well. That's a HUGE pain, and I'll tell you why
If you wanted a backup of stock, you would have to do this
1. Relock Bootloader
2. Run RUU
3. Unlock Bootloader
4. Flash TWRP
5. Backup your ROM
6. Wipe your System
7. Factory Reset
8. Flash CM10 boot.img
9. Flash CM10
10. Flash Google apps
and after that.. you have a stock backup, and you are back on CM10.. Now what if you wanted to revert to stock? Well... Sigh
1. Wipe System
2. Factory Reset
3. Flash boot.img from your backup
4. Flash your backup
and now you are back to your stock backup..
What's easier though.
1. Download a stock rooted ROM
2. Wipe system
3. Factory Reset
4. Flash the boot.img from stock
5. Flash stock
6. Make a backup
From here you can either keep stock, or go back to CM10. but, if switching between CM10 and your stock backup, you should wipe system and factory reset. you will need to flash the boot.img every time you switch
Stock rooted rom? Isnt that the ruu
Or are you talking about sense roms based off stock.
I basically want to be able to flash back to stock if i ever sell the phone
Sent from my One X using xda app-developers app
silent1643 said:
Stock rooted rom? Isnt that the ruu
Or are you talking about sense roms based off stock.
I basically want to be able to flash back to stock if i ever sell the phone
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
A stock rooted rom is.. a stock ROM with root installed.. some of them have removed AT&T apps (what we call bloatware)
You can't get root on a stock ROM unless you unlock your bootloader, flash twrp, then flash su.zip
If you want to sell the phone.. just relock the boot loader and run the RUU
Thanks!
Enlightened... If i may how do i handle nightly builds with cm10?.. The rom itself can check for updates but i also see them posted on the url link.. Whats the best way to keep flashing night lies without setting up my settings each time.. Should also mention already backing apps up with titanium pro with Dropbox
Sent from my One X using xda app-developers app
silent1643 said:
Thanks!
Enlightened... If i may how do i handle nightly builds with cm10?.. The rom itself can check for updates but i also see them posted on the url link.. Whats the best way to keep flashing night lies without setting up my settings each time.. Should also mention already backing apps up with titanium pro with Dropbox
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
You can try an 'upgrade' which means you just flash overtop of your installation. I don't know if this will keep your settings. What it may do is break some stuff, if that's the case, do not report errors unless you have a clean install.
Your best bet is to find your favorite/stable nightly build and stick with it for a while
Good advice will stick with current until something major is updated in cm10..
But essentially i could make a backup of my current cm10 install and try other roms.. Then restore from backup to revert to cm10 with all my settings intact
Sent from my One X using xda app-developers app
silent1643 said:
Good advice will stick with current until something major is updated in cm10..
But essentially i could make a backup of my current cm10 install and try other roms.. Then restore from backup to revert to cm10 with all my settings intact
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Yes. But don't forget to flash the boot.img for your CM10 backup before flashing the backup.
The boot.img that came with the cm10 zip or the boot.img from the twrp cm10 backup
Sent from my One X using xda app-developers app
Related
Alright, I rooted my Nexus S 4G this guide. My phone was running 2.3.5 but I figured that these steps in Terminal wouldn't really change. When I flashed the "recovery-clockwork-3.0.0.5-crespo.img" it didn't install properly (I assume because it was out of date/wrong version) Anyway, I flashed this instead with no problems.
In my euphoria over solving my clockwork problem, I forgot to flash the "su-2.3.6.1-ef-signed.zip" and flashed the current version of MIUI. I am now stuck in a bootloop and I cannot enter recovery by using power+volume. I cannot turn the phone off. I can load the bootloader screen using Terminal while I plug it into my computer, but I don't know what to flash to fix the phone, and start over/end up with a Nexus running MIUI.
i dont know much about macs but you can flash the img files through fastboot.
imgs files are here
thank buglesspete
chewbz said:
i dont know much about macs but you can flash the img files through fastboot.
imgs files are here
thank buglesspete
Click to expand...
Click to collapse
I can handle the mac part if you can show me which files to flash in which order to make my phone work again.
Okay this will take your phone back to stock. Download the grj22 image files. When you open it up it should have like 4 or 5 img files. After that open up cmd and type in the commands buglesspete has in his first post. It should be under "return to stock" or sometime like that.
Sent from my Nexus S 4G using XDA App
XikkeN said:
Alright, I rooted my Nexus S 4G this guide. My phone was running 2.3.5 but I figured that these steps in Terminal wouldn't really change. When I flashed the "recovery-clockwork-3.0.0.5-crespo.img" it didn't install properly (I assume because it was out of date/wrong version) Anyway, I flashed this instead with no problems.
In my euphoria over solving my clockwork problem, I forgot to flash the "su-2.3.6.1-ef-signed.zip" and flashed the current version of MIUI. I am now stuck in a bootloop and I cannot enter recovery by using power+volume. I cannot turn the phone off. I can load the bootloader screen using Terminal while I plug it into my computer, but I don't know what to flash to fix the phone, and start over/end up with a Nexus running MIUI.
Click to expand...
Click to collapse
Just a general hint... if oyu own a Nexus S 4G, Crespo isn't the right codename to look for.. it's crespo4g. Get the cwm recovery from here and flash the 4G version via "fastboot flash recovery <recoveryname>.img": http://forum.xda-developers.com/showthread.php?t=988686
rentaric said:
Just a general hint... if oyu own a Nexus S 4G, Crespo isn't the right codename to look for.. it's crespo4g. Get the cwm recovery from here and flash the 4G version via "fastboot flash recovery <recoveryname>.img": http://forum.xda-developers.com/showthread.php?t=988686
Click to expand...
Click to collapse
I know. I linked to that thread in my first post. What step am I skipping to run MIUI without a bootloop?
XikkeN said:
I know. I linked to that thread in my first post. What step am I skipping to run MIUI without a bootloop?
Click to expand...
Click to collapse
I have no experience with the 4G version of this phone but I can tell your that bootloops are usually caused by failing permissions (fix permissions in cwm rec) or missing wipes before isntalling the actual rom.
So I'd go back to start, flash the 4g recovery, wipe everything (including "mount and storage"'s /boot and then flash MIUI for 4g from here afterwards.
Basically, that MIUI (and most other custom roms) includes superuser.zip aka root. No need to root the devices before, all you need is an unlocked bootloader.
rentaric said:
I have no experience with the 4G version of this phone but I can tell your that bootloops are usually caused by failing permissions (fix permissions in cwm rec) or missing wipes before isntalling the actual rom.
So I'd go back to start, flash the 4g recovery, wipe everything (including "mount and storage"'s /boot and then flash MIUI for 4g from here afterwards.
Basically, that MIUI (and most other custom roms) includes superuser.zip aka root. No need to root the devices before, all you need is an unlocked bootloader.
Click to expand...
Click to collapse
What he said, I always wipe 3x everything just to make sure it is a clean install. And some people will also suggest to let the rom boot up normally before flashing a different kernel.
Sent from my Nexus S 4G using XDA App
chewbz said:
What he said, I always wipe 3x everything just to make sure it is a clean install. And some people will also suggest to let the rom boot up normally before flashing a different kernel.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
wiping 3 times is senseless! and the kernel should be flashed right after the rom install!
oh and wiping the dalvik cache and chache after a rom-update is also senseless! the updater-script do this automatic!
Sent from my Nexus S using XDA Premium App
Borky_16 said:
wiping 3 times is senseless! and the kernel should be flashed right after the rom install!
oh and wiping the dalvik cache and chache after a rom-update is also senseless! the updater-script do this automatic!
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
your assuming that the devs took the time to make sure to include that
Hi
I installed CWM 5 on my Nexus S. I can reboot one time and go back to CWM but after a second reboot, the recovery is back to default and I have to reflash it
Does any of you already experienced this problem ?
happens to me. i go to rom manager and re flash cwm then reboot to recovery.
Are you both using stock? The stock rom has a script that restores the default recovery when you reboot.
Delete / rename /etc/install-recovery.sh
This script writes the stock recovery on boot.
Sent from my Nexus S using xda premium
I've experienced this as well, and plan to re-name install-recovery.sh.
For those that are continually re-flashing the recovery image, do you think there is a possibility of writing to that area too many times?
I've heard of NAND flash dying in flash drives after very data intensive operations, and I've also heard of ROM storage areas having a limited number of writes.
Just wanted to test the waters.
rican408 said:
happens to me. i go to rom manager and re flash cwm then reboot to recovery.
Click to expand...
Click to collapse
Always flash through Fastboot, Better than flashing from Rom manager.
I renamed /etc/install-recovery.sh and it works
Thanks
Happens to me until I started flashing twice everytime I flash a Rom ... =] try it
Sent from my Nexus S using xda premium
So, I have S-On and the newer Hboot (1.14 I believe), and I had a quick question about TWRP restores and fastboot.
Normally, the process of flashing a new ROM means that I go into fastboot and flash the boot.img first, then go back into TWRP to flash the ROM.
However, what if this happens:
1. backup the ROM that I'm currently on (which is, say AOKP)
2. flash to a new ROM using fastboot boot.img and TWRP (this ROM is Sense-based)
Now, I decide I liked my old AOKP rom better. Can I just go into TWRP and click on restore? Or do I have to do something else first?
You need to also flash the boot.img for the ROM you are restoring to.
Sent from my HTC One X using xda app-developers app
Well if its on your sd card click install then go to file, if its nandriod then use restore and re flash img. I strongly suggest you do s off , process is easy if you read the thread and follow instructions
Sent from my HTC One X using xda premium
crazylilazn said:
So, I have S-On ....
Click to expand...
Click to collapse
The answer to any question that starts like this is "You need to s-off before going any further."
I have been reading for the last couple weeks, thinking I have an answer and end up further into the hole.
Rogers HTC One X / EVITA / HBOOT 2.14. / 2.4 TWRP initially, now 2.6 / Unlocked boot loader / s-on
1. Started trying to flash AOKP 4.2.2. Flashed boot.img, then followed with TWRP recovery. All I could get was the language screen and then it stalled. Tried numerous iterations of this with various wipes and flash first and flash after.
2. Next tried Viper 3.2.7. All good till it gets to startup screen then it stops (I understand Viper has its boot.img installed to start not needing it flashed).
3. While trying various wipes to see if it would install completely I mistakenly did a factory reset! Now no OS! No Nandroid! No ROM.zip!
4. To get a ROM on SDCard tried ADB sideload thru TWRP. after running script it says unable to mount SDCARD! Suggests I reboot system! Now a little leery of rebooting for fear it will not.
5. Also tried to MOUNT HTV via TWRP on to laptop. Did not recognize said ti initialize. Formatted FAT 32 (via MAC). Now will not mount SD Card. I did drop Viper.zip into mount (cache and system OK) but can not find it using FILE MANAGER via TWRP
6. Now am in BOOTLOADER screen of Android. Thought I could flash a ROM but from what I read it does not look possible.
Can any one point me in the right direction to get this thing up and running. At this point, as much as I am learning all the time, it does me no good having my phone down for two weeks (sure glad I kept my Nexus One).
Any answer at this stage is a good answer and I appreciate all input!
Thanks
D
Sounds like you did a factory reset in bootloader which corrupts the sd card after unlocking the bootloader. You used to be able to just mount it on pc and format it but after the jb update I don't think that's possible due to the drive no longer being a mass storage device but an mtp device instead. There was a method to fix it developed by team nocturnal but it looks like the site is inaccessible right now. I'll see if there's a way to fix it and get back to you. Bear with me.
[/COLOR]By any chance have you tried wiping sd card in twrp 2.6?
Also, have done SuperCID yet?
Sent from my One X using xda app-developers app
exad said:
Sounds like you did a factory reset in bootloader which corrupts the sd card after unlocking the bootloader. You used to be able to just mount it on pc and format it but after the jb update I don't think that's possible due to the drive no longer being a mass storage device but an mtp device instead. There was a method to fix it developed by team nocturnal but it looks like the site is inaccessible right now. I'll see if there's a way to fix it and get back to you. Bear with me.
[/COLOR]By any chance have you tried wiping sd card in twrp 2.6?
Also, have done SuperCID yet?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
SuperCID has not been done. It is S-ON presently.
I wiped SD Card as suggested. Saw it set up partitions. And now TWRP shows up when I mount . Can I just drop a ROM in and flash via TWRP? Any suggestions for a ROM. Could not get AOKP 4.2.2 to run or Viper 3.2.7.
Thanks for the quick assist at getting it to MOUNT.
Flash a stock sense rom and then fastboot flash boot boot.img extracted from the rom. Then use jet to downgrade hboot and SuperCID and then s-off. It'll save you lots of headaches.
Sent from my One X using xda app-developers app
exad said:
Flash a stock sense rom and then fastboot flash boot boot.img extracted from the rom. Then use jet to downgrade hboot and SuperCID and then s-off. It'll save you lots of headaches.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
It all sounds simple when you say it.
I will find a stock sense ROM to install then follow with boot.img.
Is it necessary to wipe anything more then Dalvik and Cache?
Thanks again.
David
In twrp 2.6 the factory reset wipes everything except sd card and system. You don't have to wipe system but I always do when I'm flashing a new rom.
Sent from my One X using xda app-developers app
exad said:
In twrp 2.6 the factory reset wipes everything except sd card and system. You don't have to wipe system but I always do when I'm flashing a new rom.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Will wipe the system then.
Thanks again.
D
Anytime pip
Sent from my One X using xda app-developers app
I have flashed many 4.3 Roms and can not get any of them to boot. I have followed all install instructions but can't get past gs3 screen. Any ideas?
Sent from my SCH-I535 using xda app-developers app
im having a similar problem to yours..i mean after i do a fresh install+gapps it works..but after i go back to recovery and install my other files it wont go past the gs3 logo no idea why.
Yep frustrating any other ROM is OK just 4.3 not working, sucks.
Sent from my SCH-I535 using xda app-developers app
I've flashed every 4.3 and all booted. Try just flashing ROM first. Let sit a few minutes then flash gapps. I also use the eclipse ROM gapps for all. No issues.
Sent from my SCH-I535 using xda app-developers app
I also have the same problem when I try to reboot on 4.3 Roms. First boot up is fine. But when I go into to recovery it won't boot back up unless I reflash the ROM from the start. If someone tries flashing ROM and gapps separately let us know if it fixes it.
Sent from my SCH-I535 using Tapatalk
Tried eclipse ROM and apps. No different. Initial boot works and ROM runs fine but reboot freezes up on gs3 screen. What is getting scrambled and is there a way to fix this.
Sent from my SCH-I535 using xda app-developers app
I've never had this issue. What I've done/used to flash all 4.3 roms was use the super wipe tool found in the general section(the one that wipes data, system and caches only) and then run it once and flash Rom+ gapps as instructed. I use twrp as well. Also, perhaps it's a stock 4.3 kernel and maybe flash a kernel straight after you flash the rom and gapps. Rom> gapps>kernel . Hope it helps
Sent from my SCH-I535 using Tapatalk
---------- Post added at 08:47 PM ---------- Previous post was at 08:41 PM ----------
http://forum.xda-developers.com/showthread.php?t=2097365
[Mod][Utility] Wiping Tools - Simple and Fast
Sent from my SCH-I535 using Tapatalk
I used ez recovery from the play store and used cwm touch recovery and I no longer have the reboot issues. Even if you're using cwm, I would just download ez recovery and try it.
Sent from my SCH-I535 using Tapatalk
Use ez recovery to flash the ROM or install cwm and then flash through that?
Sent from my SCH-I535 using xda app-developers app
I had a similar problem when I first tried 4.2 but I've found two ways that have always worked for me
Full wipe (I wipe everything 3 times, but I'm sure that's overkill)
Flash rom
Flash gapps
Reboot
If it gets stuck on any screen wipe the cache and dalvik cache
Reboot
The other method I've only used with Dirty Unicorns
Full wipe
Flash rom
Reboot
Once the rom reboots, reboot back into recovery
Flash gapps
Reboot
Wait 10 minutes
You can either reboot again or just use as is
But if nothing is working you can odin back to stock
Then use this tool to root, unlock the bootloader, and flash the custom recovery of your choice http://forum.xda-developers.com/showthread.php?t=2332825 (it even works on a mac)
(This is what I always use to root, unlock the bootloader, and flash recovery whenever I have to flash back to stock)
After I do that I always reboot and use Rom Manager to flash the latest recovery before flashing anything else.
These 2 roms have been 100% stable for me
http://forum.xda-developers.com/showthread.php?t=2484256 (4.3.1)
http://forum.xda-developers.com/showthread.php?t=2469789 (4.3 I've never tried the weeklies just the lastest stable build)
Hope it helps
It seems that most ROMs will boot up fine with the latest TWRP recovery. But there are a few that will only boot up with CWM. So download both recoveries and flash them using ez recovery when one of them isn't working.
So, I usually stick with TWRP 2.6 as my default. The great thing about ez is that it includes cwm in it. First off I'd make sure you're running the latest recovery available. Then if that doesn't work restore your backup, hopefully you made one, and flash cwm and try reflashing the ROM. Assuming you're wiping everything at least 3 times and flashing the correct ROM with the correct gapps, there's no reason why it shouldn't work. And another thing. It's never a good idea to restore data from any app, ever. Trust me, I know.
Sent from my SCH-I535 using Tapatalk
Juice3250 said:
It seems that most ROMs will boot up fine with the latest TWRP recovery. But there are a few that will only boot up with CWM. So download both recoveries and flash them using ez recovery when one of them isn't working.
So, I usually stick with TWRP 2.6 as my default. The great thing about ez is that it includes cwm in it. First off I'd make sure you're running the latest recovery available. Then if that doesn't work restore your backup, hopefully you made one, and flash cwm and try reflashing the ROM. Assuming you're wiping everything at least 3 times and flashing the correct ROM with the correct gapps, there's no reason why it shouldn't work. And another thing. It's never a good idea to restore data from any app, ever. Trust me, I know.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
You do realize that the recoveries built into ez recovery are over a year old. I wouldn't flash those under any circumstances. Only use ez recovery to flash from the custom slot.
Sent from my SCH-I535 using Tapatalk 2
Thanks for correcting me on that one. My bad.
Sent from my SCH-I535 using Tapatalk