So I started by rooting with Shabby's AIO root. Worked fine.
Today I unlocked, following QBKing's instructional video. No errors.
Then I flashed TWRP using fastboot. No errors.
I'm able to boot, everything seems to work (except 4g of course), but when I boot into recovery, all I get is an android with a yellow triangle. What gives? Can anyone help?
try reflashing the recovery happened to me once when i flashed cwm.
it keeps happening to me no matter how many times i try to flash either one. I'm definitely rooted and unlocked but recovery just wont stick at all, all i ever get is the yellow triangle. Ive given up on it....
I have in my notes to delete "install-recovery.sh" in system/etc and reflash. Couldn't hurt.
jrebo said:
I have in my notes to delete "install-recovery.sh" in system/etc and reflash. Couldn't hurt.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=19650030&postcount=1
I think that the above post is correct, and also remember reading somewhere about it.
And I can do that from Root Explorer? I must admit I'm a little nervous - I'd better make a backup. You guys have done it too?
CharFalco said:
And I can do that from Root Explorer? I must admit I'm a little nervous - I'd better make a backup. You guys have done it too?
Click to expand...
Click to collapse
I would always do a backup in CWM or bootstrap before trying anything. I've never done this, but you could always try.
I don't currently have the ability to boot into CWM. I suppose I'll try to get into Bootstrap and make a nandroid, if that's possible - I haven't done any of this stuff since around this time last year on my Evo.
Use root explorer. another reason could be your not unlocked. Does your screen say unlocked when you boot?
Mine does say I'm unlocked, I've also deleted that .sh file after backing it up and still nothing. I don't want to go through the whole process of relocking my mopho to get it to work,, but I know that may help. I've done everything I could and read through every thread on it and still no go. I've definitely learned a lot though, lol. I've also figured out how to switch the internal memory sdcard with sdcard-ext to have your actual sdcard be internal. Good stuff, I love xda.
The current procedure seems to be:
moto-fastboot delete recovery
flash recovery
reboot
That gives it time to re-flash stock recovery during the reboot. What if you flashed the new recovery, yanked battery, went to recovery, then flashed CM7 (which apparently doesn't try to replace the stock recovery)?
I've got Bootstrap working. I'll be doing a Nandroid, then trying to rename install-recovery.sh later today. If that doesn't work - all I can do is go back to total stock, unroot, and restart the process. Life goes on.
Mine definitely says "Unlocked" at the top of the screen on boot - and I'm rooted (I can use Titanium Backup and Wifi Tether)
If it's an issue with the order of rooting and unlocking (I saw no error messages at any stage), can we get a warning placed in the pudding / MoPho FAQ thread please, spare someone else the trouble we're going through?
Seeing as I'm already unlocked and rooted via Penguin's AIO root- and backed up through Bootstrap, is there any harm in flashing the system.img used in QBKing77's video? Would that solve my problem and let a normal recovery stick?
Any idea if this would bork my phone? I don't have a backup - but I -do- want to be able to use CM and Miui (hate MotoBlur). If I'm already AIO rooted and QBking Unlocked, is there any harm to flashing system.img, then flashing recovery?
I am having the same issue on my photon. when i boot in to clockworks i see the android recovery, and when i try to select it the triangle pops up with the
android guy then i have to pull battery to restart phone still works thoe. Tom
Ebert
This worked on my Xoom. Suspect same/similar will work on Photon. Issue is that recent OTA's add files that overwrite custom recovery with stock recovery if you let the device boot (don't let it boot - or if you do, delete those files, then reflash).
unlock
flash recovery
boot into recovery
root
then while still in CWM, no reboot, but instead:
adb remount
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
reboot with CWM
Only had to flash CWM once.
topeka_tom said:
I am having the same issue on my photon. when i boot in to clockworks i see the android recovery, and when i try to select it the triangle pops up with the
android guy then i have to pull battery to restart phone still works thoe. Tom
Ebert
Click to expand...
Click to collapse
I had the same issue then someone told me to root via Torpedo method. Did that and everything was smooth sailing from there.
Flash over Bootstrap?
With having bootsrap installed, could I use one of romracers CWM installers and flash over bootstrap? Has anyone tried this?
this is what i used. work great
http://forum.xda-developers.com/showthread.php?t=1250697
moonzbabysh, would you direct me to the thread that shows how to switch the internal and external memory around. I've got a 16gb card but can't put apps on it. Thanks.
Related
Tuesday night I loaded CM7, and then the Market wouldn't update my apps so I decided I would restore BAMF 1.5. After doing so, the Market just gave me "Fails" trying to update, and I could not access recovery, as I was going to do a complete wipe and reflash. Most of Wednesday, an extremely helpful & knowledgable member, Mattgyver83, tried diligently to help me rectify the situation, but to no avail. We tried to Fastboot, tried flash_image, tried fix permissions...shoot, I practically wore out adb..anyway, I ended up reverting back to stock and unrooted. I used jcase's method to revert back to stock, and that was painless, and successful. I decided last night to try rooting again, thinking a fresh root would solve my issue of not being able to access recovery. Root was successful, but I still cannot access recovery, through rom manager, or through bootloader. When I attempt it my Tbolt goes to white HTC screen, and stays there. All functions of my phone now work, and all aspects of root work, except I cannot flash anything. Rom manager shows I have clockwork recovery, but I just can't get to it.
Sorry for the long ramble. If anyone has had this issue, or if anyone knows a fix, I would appreciate it. Otherwise, I wait for Gingerbread.
Thanks
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
travishamockery said:
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
Click to expand...
Click to collapse
Tried that, but thanks. Still just goes to white HTC screen, and stays there until I do battery pull.
jr4000watts said:
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
Click to expand...
Click to collapse
I can get to bootloader, just not able to get into recovery.
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
monolithic said:
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
Click to expand...
Click to collapse
Thanks, but that didn't work. I think something in my os got lost when I restored BAMF from CM7.
Yea I spent a good few hours yesterday trying to help Orio out and we attempted a ton of things to try and fix the recovery issue, this post should offer a bit more insight to the methods used, this is running off memory;
adb reboot recovery failed
Reinstall latest Rom Manager apk and Flash CWM
flash latest rom manager via fastboot (CWM only)
(fastboot flash recovery /sdcard/recovery-clockwork-3.0.2.5.img)
**did not do fastboot erase recovery first**
"return to stock safely and properly" XDAthread by jcase
return to stock image [RUU], reroot, try again
try to boot into recovery via hboot
manually installed fix_permissions.sh script and busybox on rooted stock, ran.. didnt fix
tried to see if flash_image method would work, didn't
All of the above have failed and we basically tried almost all combinations. Not once would this phone get back into recovery, even after flashing the appropriate RUUs which include either stock android or CWM recovery. The only thing we have not currently attempted which might be the last thing left is to do is manually install the nandroid.sh script and do an advanced restore of the recovery image only from a nandroid backup on SD. I would rather not go down this method as it could have an undesired result, I have done it to restore a G1 back in the day but not 100% if its gonna work on a tbolt. Thankfully his phone boots, and we can get into hboot, but yea.. pretend recovery just doesnt exist at all...
Curious if anyone has any knowledge above what we have already tried.
monolithic said:
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Click to expand...
Click to collapse
I recall the same thing and its a good thought however that was mostly a generic error due to a CWM update and CM6 (I think) but either way flashing an RUU should override this shortcoming and im pretty sure that issue was worked out in CWM as well.
Not to be rude, but I don't think this question belongs in the development section.
Orio56 said:
I can get to bootloader, just not able to get into recovery.
Click to expand...
Click to collapse
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
hogowner said:
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
Click to expand...
Click to collapse
Thanks, but no, I deleted that after loading it. I actually reverted back to stock/unrooted last night and rerooted and the problem still remains. It's quite strange.
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
shelooga said:
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
Click to expand...
Click to collapse
That is what I was going to suggest. In ROM Manager at the very bottom try and flash an older version.
Sent from my ADR6400L using XDA Premium App
SUCCESS !!!
I fixed it !
Apparently, when I loaded up cm7, files showed up about the same time on my sdcard in clockworkmod download file. I deleted those files, and reflashed clockworkmod in rom manager, (which this time took like 3 - 4 minutes), and rebooted into recovery and it worked...did it again, just in case it was a fluke and it worked.
All is well now...the planets are realigned !!!
Thanks everyone for your ideas and especially thanks to mattgyver83 who helped me for something like 4 hours yesterday. Exceptional kindness !!
mods...you can close this thread.
GREAT NEWS!!!! CONGRATULATIONS!!
THANKS FOR REPORTING BACK!
This may help out other members with the same problem!!
now go ahead and start playing with your T-BOLT again!
That's a very odd solution. My first two things to try would have been:
1) fastboot:
fastboot erase recovery
fastboot flash recovery C:\some\local\path\recovery.img
You can't, well, probably shouldn't, flash a recovery from the /sdcard. When in fastboot mode I don't think the sdcard is even mounted. Either way, I think fastboot needs the img file on the local file system.
2) Create a PG05IMG.zip file with the recovery.img file in it, and flash that through HBOOT. Although this should have been done in some form or fashion when you downgraded or re-rooted, so YMMV.
Hi, stupid question here from a relative noob....
I have a Cincinnati Bell Vibrant, that I recently flashed CM7 on (after using Rom Manager to backup up my stock rom). Liked it, but found it too battery-intensive, so I booted into clockworkmod recovery and attempted to restore the backup of my stock rom. It failed on flashing the boot image, and now my phone is stuck on the Vibrant screen, and won't boot. None of the hardware combinations to get into recovery mode are working, but I can get it into download mode. Before I screw things up further, what is the best way to go from here to get the backup restored, or is it even possible at this point?
Thanks
tabbott01 said:
Hi, stupid question here from a relative noob....
I have a Cincinnati Bell Vibrant, that I recently flashed CM7 on (after using Rom Manager to backup up my stock rom). Liked it, but found it too battery-intensive, so I booted into clockworkmod recovery and attempted to restore the backup of my stock rom. It failed on flashing the boot image, and now my phone is stuck on the Vibrant screen, and won't boot. None of the hardware combinations to get into recovery mode are working, but I can get it into download mode. Before I screw things up further, what is the best way to go from here to get the backup restored, or is it even possible at this point?
Thanks
Click to expand...
Click to collapse
This doesn't sound too bad. Basically you want to Odin back to stock. Then reflash the rom you were on, then you can reboot back into recovery and restore your backup. If voodoo was enabled on your backup make sure voodoo is enabled again before restoring(it might work either way, but I'm not sure). When I've done this, I restore a prerooted 2.2 stock Rom without changing the bootloaders, but almost any official stock rom will also work. I'm on the go, so I don't have a link handy, but post back if needed and I will point you to the odin package I use. Good luck.
I also am having some issues with Clockworld recovery. The problem i am having is that when doing a nandriod backup this is the error i am recieving
"E:cant mount /dev/block/mmcblk1p1 (or @)
Cant mount /mnt/sdcard
any suggestions on whats going on?
phone_noobie said:
I also am having some issues with Clockworld recovery. The problem i am having is that when doing a nandriod backup this is the error i am recieving
"E:cant mount /dev/block/mmcblk1p1 (or @)
Cant mount /mnt/sdcard
any suggestions on whats going on?
Click to expand...
Click to collapse
Are you sure the sdcard is good? If so then I would follow the same steps listed above, that way you know your CWR is good.
mattb3 said:
Are you sure the sdcard is good? If so then I would follow the same steps listed above, that way you know your CWR is good.
Click to expand...
Click to collapse
yes it is good because i can see all the videos, pics i have saved in it. Also i put the new ROM on my internal sd card and its there so sd card is def good. What could be causing the problem?
To the op, I would use Odin, no real worries there.
To the other guy with sdcard issue, try moving all files to your PC, format your sdcard, reboot, move files back, flash cwr in ROM mgr, backup work? Move critical files back from PC.
mattb3 said:
This doesn't sound too bad. Basically you want to Odin back to stock. Then reflash the rom you were on, then you can reboot back into recovery and restore your backup. If voodoo was enabled on your backup make sure voodoo is enabled again before restoring(it might work either way, but I'm not sure). When I've done this, I restore a prerooted 2.2 stock Rom without changing the bootloaders, but almost any official stock rom will also work. I'm on the go, so I don't have a link handy, but post back if needed and I will point you to the odin package I use. Good luck.
Click to expand...
Click to collapse
Thanks...that's exactly what I did, except the backup would never quite "take." It completely loaded and cycled through the boot process, but I ended up on a boot-restore loop. So now I've Odin-ed back to stock with the closest build I could find to my stock (which I don't think is out there yet - FROYO.UVJL6.ULTIMOBILE - do you know anywhere to find it?), rooted, and am searching for a good, stable, battery-friendly mod once again.
s15274n said:
try moving all files to your PC, format your sdcard, reboot, move files back, flash cwr in ROM mgr, backup work? Move critical files back from PC.
Click to expand...
Click to collapse
i did try formatting, then moving all the stuff back and am still getting that same error message
^ what rom are you on, if one?
You could always ODIN, and use my option b cwr in the noob guide. I just tested making a backup using trigger 8/22 and know there are no issues. Not really sure whats up on your end. I will say though, I've emailed koush several times that there is an issue with cwr on the vibrant from rom manager, for some it won't even flash.
phone_noobie said:
i did try formatting, then moving all the stuff back and am still getting that same error message
Click to expand...
Click to collapse
try different sd card..or reinstall CWM...
Hello,
I'm a happy user of cyanogenmod and have loved it since the day I got it. But as I updated to CM 7.1.0 Stable mod, I've had problems with my wireless. Whenever I try to turn it on, it responds with "Error" and doesn't turn on. I can't see any wireless networks either.
I tried something from cyanogenmods forum, but with no luck, it said I had to "Format system". As I tried to "Format system", it restarted and it's stuck at the "HTC" White screen. It shows the white screen everytime I try to start it. I'm able to get into HBOOT and recovery, but I'm unsure what to do. Have I really broken my phone?
Anything I can do to get it working again? I'd love if anybody could help me here, thank you.
I'm not very good at this, so I would be nice if somebody could guide me through this.
Ok, In your possition I bet you panic a little bit? Don't worry and stay calm
First of all, i don't know what other requirements you need other than to get the rom back into your phone ie swap partition, ext partition etc, so this help is to ONLY get a rom back into your formatted phone.
You said you can boot in recovery, this is a sure sign phone is not broken, do you have clockwork mod recovery?
If you have clockwork mod still in root folder of your sdcard, your halfway to fixing your issue, if no clockwork mod, search on XDA and get the clockwork mod recovery, it'll probably be called fake-flash and it will be a zip file, might be best to get version 5.0.2.0.
Next you will need a rom, download any one you like, be it cyanogen, Blayo's froyo, ogo's gingerbread etc.
If you've already got clockwork mod on your sdcard then best to take the sdcard out, put it in a card reader attached to the computer, copy the rom zip file to the sdcard, put it back in to the phone, load up clockwork mod via recovery on your phone then flash the rom from sdcard...
if no clockwork mod, then copy both clockwork and the rom to the sdcard clockwork must be named update.zip and in the root of the sdcard, put sdcard back in your phone then follow the same flashing procedure as before. You may need to wipe data and davlik cache before flashing.
I'm pretty new to android rooting & flashing and i've had a few scares myself, the one most important thing i've discovered is to have clockwork mod recovery in the root of the sdcard, and so long as you can boot into that, you pretty much can't go wrong, unless your S-OFF, then an inexperianced user can do damage.
The other thing of importance is to either have backups (done via clockwork mod) or a fresh rom to flash on the sdcard, backups are better though because that keep all your apps and stuff intact
Good Luck
OH F*** YEAH! It started now! ranger4740, I love you!
Thanks a lot for the help!
GuyFromDenmark said:
OH F*** YEAH! It started now! ranger4740, I love you!
Thanks a lot for the help!
Click to expand...
Click to collapse
I am very glad I could help you get your phone back up and running.
Have a look in this post my newbee tip for using Clockworkmod recovery's, it may help you for future reference. http://forum.xda-developers.com/showthread.php?t=1298680
Alright, after bricking my phone yesterday and spending hours finally unbricking it, I've decided that I'm just not quite ready to play around with ROMs on the Transformer Prime. At least, not until they get a little more stable.
However, I'm finding myself unable to get my Prime back to stock ICS...
What I'm currently running is a Cyanogenmod 9 nightly build from 3/4/12. Through Rom Manager I was able to install the latest CWM (5.8.2.0) BEFORE the whole bricking incident. Now I can't even get my WiFi turned on...so I suppose any further changes via Rom Manager are halted.
Anyway, I used Vipermod's tool and was able to unroot successfully. I then went into settings and attempted to perform a factory reset. However, my tablet booted up with the same, Cyanogenmod boot screen and brought me back without any changes.
So then I tried using ADB....plugging my Prime in and typing "adb reboot recovery". But I get the message "adb server is out of date. killing..." then on the next line * daemon started successfully *. My device resets...but same thing...cyanogenmod...no CWM...no changes.
I thought maybe ADB wasn't working because I had unrooted. So I re-rooted, again using Vipermod. I see superuser again now...but ADB reboot recovery is still not working.
So now I'm stuck... I seemingly can't perform a factory reset with my build of cyanogenmod, and I can't find any way of getting back to recovery (I've tried selecting recovery reboot after pushing the power button, tried selecting recovery from within Rom Manager and tried with ADB...all failed). Again, all I want to do is factory reset, and get my stock ICS back. Can anyone please help me out?
You won't get back a total stock ICS easily
You can't use Factory reset after unlocking the Prime and installing CWM
adb reboot recovery does not work
The only way to reboot to recovery is via holding down Vol_Down on boot and then pressing Vol_Up
non working wifi is because you have a wrong kernel
you can't boot to recovery because it's most likely wiped
Try installing CWM from Rom Manager again, if that does not work follow the guide in the dev section to flash another CWM version manually.
Then reboot to recovery and flash another ROM.
Make sure the ROM contains a new kernel, so your Wifi is working again.
Diamondback said:
You won't get back a total stock ICS easily
You can't use Factory reset after unlocking the Prime and installing CWM
adb reboot recovery does not work
The only way to reboot to recovery is via holding down Vol_Down on boot and then pressing Vol_Up
non working wifi is because you have a wrong kernel
you can't boot to recovery because it's most likely wiped
Try installing CWM from Rom Manager again, if that does not work follow the guide in the dev section to flash another CWM version manually.
Then reboot to recovery and flash another ROM.
Make sure the ROM contains a new kernel, so your Wifi is working again.
Click to expand...
Click to collapse
Thanks again Diamondback!
To clarify, I don't really need stock ICS. What I need is a working ROM with Android Market (Google Play, WTF?), WiFi, a web browser...all that. I've heard that Virtuous is good, so I'll probably go that direction.
But more importantly, I need a way to install it, and the only way I know how to do that is a) using Rom Manager (which apparently doesn't work with the Prime at the moment), or b) doing it through CWM (which isn't working for me at the moment either).
As far as your suggestions go, I can't use Rom Manager to install CWM again, because my WiFi isn't working. However, I have found instructions online for flashing CWM manually, but it involves installing fastboot, and doing something with a "blob". I don't know what a blob is, but in your unbricking post, you specifically state:
Do not, I repeat, do not try to flash a stock ASUS ROM/blob file.
Doing this you will most likely hard brick your Prime.
I'm not sure if that applies in this case, but the last thing I want to do is brick my device again.
This is the post I'm referring to:
http://www.theandroidsoul.com/install-cwm-5-8-2-0-on-transformer-prime/
Can you advise whether this method is safe, or point me in the direction of a safer method for flashing CWM manually?
Thanks!
scaryslocuda said:
Thanks again Diamondback!
To clarify, I don't really need stock ICS. What I need is a working ROM with Android Market (Google Play, WTF?), WiFi, a web browser...all that. I've heard that Virtuous is good, so I'll probably go that direction.
But more importantly, I need a way to install it, and the only way I know how to do that is a) using Rom Manager (which apparently doesn't work with the Prime at the moment), or b) doing it through CWM (which isn't working for me at the moment either).
As far as your suggestions go, I can't use Rom Manager to install CWM again, because my WiFi isn't working. However, I have found instructions online for flashing CWM manually, but it involves installing fastboot, and doing something with a "blob". I don't know what a blob is, but in your unbricking post, you specifically state:
Do not, I repeat, do not try to flash a stock ASUS ROM/blob file.
Doing this you will most likely hard brick your Prime.
I'm not sure if that applies in this case, but the last thing I want to do is brick my device again.
This is the post I'm referring to:
http://www.theandroidsoul.com/install-cwm-5-8-2-0-on-transformer-prime/
Can you advise whether this method is safe, or point me in the direction of a safer method for flashing CWM manually?
Thanks!
Click to expand...
Click to collapse
My warning only applies to STOCK blobs (like the ones in the official asus updates from their website).
The guide you posted seems to be fine.
Great! I'll give it a shot tonight.
One last thing... If I find that Virtuous isn't the best fit for me, would you advise AGAINST installing the stock firmware posted over at Android Soul? Is this what you would consider a "stock blob" or is this something different? Here is the link:
http://www.theandroidsoul.com/trans...h-cwm-recovery-on-unlocked-bootloader-primes/
That's a zip, not a blob, you can flash that
Diamondback said:
That's a zip, not a blob, you can flash that
Click to expand...
Click to collapse
Worked perfectly! Thanks so much for your help Diamondback...again!
Alright, so I wiped my phone in TWRP in preparation to flash something and I neglected to make a backup (I know, rookie mistake). The ROM I tried flashing will not go through and now I am stuck. I can boot into recovery fine but I really need a ROM to flash so I have something to boot into. I can't use an RUU (I have tried), probably because I used the bootloader unlock/root work-around. I'd gladly take any advice but I think what I need is just a flashable .zip of the stock ROM or maybe a backup I can restore in TWRP. If some kind soul could help me out, I'd be forever grateful.
are you referring the the stock rom offered by mycomputerdoctor? If so, the flashing does fail, but your phone will still work. From what I understand the only problem is the error in TWRP and you wont have root anymore.
My phone does indeed still work, but I wiped /system before trying to flash so I don't have a ROM installed currently and therefore cannot boot past the splash screen.
http://forum.xda-developers.com/showthread.php?t=1999962
docnok63 said:
http://forum.xda-developers.com/showthread.php?t=1999962
Click to expand...
Click to collapse
Unfortunately, that is an RUU, which does not work for me. Thanks, though.
install the rom, even if it says fails, it should still boot. you could also just adb push the updated rom on to your sd card.
Thrillhouse847 said:
Alright, so I wiped my phone in TWRP in preparation to flash something and I neglected to make a backup (I know, rookie mistake). The ROM I tried flashing will not go through and now I am stuck. I can boot into recovery fine but I really need a ROM to flash so I have something to boot into. I can't use an RUU (I have tried), probably because I used the bootloader unlock/root work-around. I'd gladly take any advice but I think what I need is just a flashable .zip of the stock ROM or maybe a backup I can restore in TWRP. If some kind soul could help me out, I'd be forever grateful.
Click to expand...
Click to collapse
Im in the same boat :/ stuck in recovery and have no rom to flash. going to try to adb the latest version and see how that goes.
I was afraid of something like this. We shouldn't be messing with our phones without a back to factory state.
I'm actually all set now. I flashed the updated stock, debloated ROM and made a back up so I'm good to go.
Sent from my HTC6435LVW using Tapatalk 2