Ive searched everywhere, but I couldnt find anything. Right now I can boot into recovery and the bootloader but cant start up the phone completely. The phone is just stuck at the splash screen. In recovery, Ive tried wiping data and cache using clockworkmod 3.0.0.6 recovery but it just says "error mounting /system! Im about to try to unroot my phone.
Any help will be appreciated, Thanks.
Edit: Just tried installing the PD15IMG.zip through the bootloader but all it says is "-Fail-PU" next to everything.
You're not gonna like this. I've heard of this happening only 2 other times. Both times I dont think they found a fix.
try to fastboot wipe everything and see if that will let you install the PDimg. Also,try and download it from a different source.
If you have the ENG bootloader, you can try to fastboot flash parts of old nandroids as well.
option94 said:
You're not gonna like this. I've heard of this happening only 2 other times. Both times I dont think they found a fix.
try to fastboot wipe everything and see if that will let you install the PDimg. Also,try and download it from a different source.
If you have the ENG bootloader, you can try to fastboot flash parts of old nandroids as well.
Click to expand...
Click to collapse
Ok, Im going to try this right now, thanks hopefully it all goes good.
When I try to wipe everything via fastboot, all i get is a FAILED:remote not allowed message.
Do you have the eng Hboot?
option94 said:
Do you have the eng Hboot?
Click to expand...
Click to collapse
What is that? I dont think I do.
Edit: I just found it here. I tried doing it through recovery but all i get is an error,
"~ # dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18
dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18
dd: can't open '/data/local/hboot-eng.img': Not a directory"
xl DIGITAL lx said:
What is that? I dont think I do.
Edit: I just found it here. I tried doing it through recovery but all i get is an error,
"~ # dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18
dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18
dd: can't open '/data/local/hboot-eng.img': Not a directory"
Click to expand...
Click to collapse
You cant do it in recovery. You can do it while its booting, if it gets past the splash screen. You could try and do it from the splash screen as well.
Being that you cant get anything to work, i wont tll you not to try this. Just know that this is the most dangerous thing that you could do to your phone.
option94 said:
You cant do it in recovery. You can do it while its booting, if it gets past the splash screen. You could try and do it from the splash screen as well.
Being that you cant get anything to work, i wont tll you not to try this. Just know that this is the most dangerous thing that you could do to your phone.
Click to expand...
Click to collapse
Just tried it through the splash screen and Im trying to get to adb shell, all I get is
exec 'system/bin/sh' failed: no such file or directory (2)
yeah. /system is hosed.
Im at a loss for what to tell you. :/
option94 said:
yeah. /system is hosed.
Im at a loss for what to tell you. :/
Click to expand...
Click to collapse
What if I just ask for a warranty exchange and just turn it in to tmobile like it is?
I've done it, but YMMV.
Related
Is there anyone around with a Rogers HTC Dream?
if so, could you please do a nandroid backup of your phone and sent me the files?
I can't boot my phone after messing up reflashing it with incompatable firmware
Thanks in advance!
they are here
Yep they are there and I plan to leave them on that server permanently.
would i install these using fastboot... or what would I use?
the nandroid gives me errors
it refuses to back up my data and will not restore anything
if i use nandroid-mobile.sh backup in the console it says
error reading recovery no space left on device
PurpleFries said:
would i install these using fastboot... or what would I use?
the nandroid gives me errors
it refuses to back up my data and will not restore anything
if i use nandroid-mobile.sh backup in the console it says
error reading recovery no space left on device
Click to expand...
Click to collapse
yup fastboot.
k heres what i used
fastboot flash boot boot.img
fastboot flash system system.img
restarted and
still stuck on rogers screen
no change whatsoever
When I semi-bricked my phone these are the instructions I used.
Since you can get into fastboot you should be able to reload to factory settings no problem.
should be...
hmmmm, looks like you did the correct thing.
Just to let you know, after you reload the fresh copy of boot.img and system.img it will take much longer for your phone to turn on the first time, typically 5-10 minutes. It has to re-install the OS on the phone.
thats essentially what i did
however the link you gave me did not include a data.img
DISREGARD TEMPORARILY, waiting those 5-10 minutes
it doesnt work if i just flash the boot and system
also, would i need to reflash the recovery with the stock rom? because then i need the stock recovery rom as well
PurpleFries said:
thats essentially what i did
however the link you gave me did not include a data.img
Click to expand...
Click to collapse
The data.img would be personal. It's not needed, but if you don't have when you flash your Dream it'll be like you're starting over for the first time.
it doesnt work if i just flash the boot and system
also, would i need to reflash the recovery with the stock rom? because then i need the stock recovery rom as well
Click to expand...
Click to collapse
AFAIK, the stock from is the system.img file. How lond did you leave it on the Rogers screen before you manually restarted your phone?
as of now, it's been approx 10 minutes.
after ur post edit i wiped and re-fastboot-ed the stuff
gonna let it run for about 20 minutes before i conclude its still not workin
EDIT
18 minutes so far...
not looking favorable T.T
EDIT2
yea its been 20 minutes, no change...
any other ideas?
EDIT3
30 minutes...
def not working
PurpleFries said:
as of now, it's been approx 10 minutes.
after ur post edit i wiped and re-fastboot-ed the stuff
gonna let it run for about 20 minutes before i conclude its still not workin
Click to expand...
Click to collapse
yeah after 20 minutes it's certainly too long. I think mine only took about 5 minutes, but good luck. eeep
edit: worse comes to worse, take it back to the store and tell them your phone wont turn on.
Also you might be able to get more help tomorrow on the subject. I'm a fairly big newbie here so I don't know that much. There is a way for your computer to see at what point your phone may be frozen at but I can't remember how.
edit 2:
17. It's taking forever to boot!
The first boot will take longer than normal because dexopt needs to run. If you are nervous, connect USB and run "adb logcat" to watch the progress.
Click to expand...
Click to collapse
That is from cyanogen, but it should give you some insight as to what your phone may be doing.
doesnt help
it doesnt see my device as attached.
adb devices doesnt list a device
and adb logcat tells me its waiting for devices
I'm sure ill need some sort of explanation as to why it doesnt turn on... what could I say?
also, not sure if i thanked you before, but thanks for all of the assistance
EDIT
it sees the device if it is attached in recovery mode
I still cant logcat tho
it says: /sbin/sh: exec: line 1: logcat: not found
PurpleFries said:
doesnt help
it doesnt see my device as attached.
adb devices doesnt list a device
and adb logcat tells me its waiting for devices
I'm sure ill need some sort of explanation as to why it doesnt turn on... what could I say?
also, not sure if i thanked you before, but thanks for all of the assistance
EDIT
it sees the device if it is attached in recovery mode
I still cant logcat tho
it says: /sbin/sh: exec: line 1: logcat: not found
Click to expand...
Click to collapse
I would just tell them I turned it on this morning and this happened. Ask them if they can fix it and see what happens. Mention nothing about trying to root it.
Just to make sure you're doing the steps correctly.
You're downloading the files I provided for you and placing them in your android/sdk..../tools folder right?
Then you boot the phone into fastboot?
Then I think you press the talk button to usb connect
from there you type in the commands.
Is that what you're doing?
exactly word for word.
during entering the commands:
i flash the boot and system.img
and press the back button to reboot
then i do the adb logcat and it cannot detect the device
PurpleFries said:
exactly word for word.
during entering the commands:
i flash the boot and system.img
and press the back button to reboot
then i do the adb logcat and it cannot detect the device
Click to expand...
Click to collapse
have you applied the update.zip file? Perhaps try applying that again first and then try the recover again.
which update.zip?
you never told me to install an update.zip previously
it's done through the recovery menu correct?
PurpleFries said:
which update.zip?
you never told me to install an update.zip previously
it's done through the recovery menu correct?
Click to expand...
Click to collapse
Well from that earlier psot I showed you that linked to HOFO step #1 had this.
Assuming you installed the update.zip before or after rooting (you can do it at any point really), now you can begin the recovery. First, enter the following into the command prompt
Click to expand...
Click to collapse
So it looks like the phone has to be rooted before you can apply the backup and to root the phone correctly you need the update.zip file.
The instructions to install the update.zip file and the file itself can be found here
Perhaps try to follow all of those steps, well skip the nandroid backup and see if your phone boots after that. If it does not but you can install the update.zip file then try the recovery method you have been trying.
tried updating with the files given (update.zip, boot.img, recovery.img)
could not go into recovery mode, would not boot
tried updating with update.zip and other files from before(update.zip, boot.img, system.img)
still no booting
my phone was, however already root-ed before it stopped working
PurpleFries said:
tried updating with the files given (update.zip, boot.img, recovery.img)
could not go into recovery mode, would not boot
tried updating with update.zip and other files from before(update.zip, boot.img, system.img)
still no booting
my phone was, however already root-ed before it stopped working
Click to expand...
Click to collapse
Sorry then. I'm out of ways to help. I don't really know all that much about the process. Perhaps your phone is slightly different than the rest of our Rogers phones so my backup files wont work on yours.
how long ago did you get it?
this thursday
credits to K'tag
http://forum.xda-developers.com/showpost.php?p=11205300&postcount=284
i tried to flash it and wow it worked but its a wrong dimension it has a black bar on both sides.. so i tried the other one you post.
but a little blury... so i did some adjustments and now its kinda more like the default splash... thanks bro....
newei
heres the file
http://www.mediafire.com/?urkjhzcugs0wex8
thank you so much bro
ardeldotcom said:
credits to K'tag
http://forum.xda-developers.com/showpost.php?p=11205300&postcount=284
i tried to flash it and wow it worked but its a wrong dimension it has a black bar on both sides.. so i tried the other one you post.
but a little blury... so i did some adjustments and now its kinda more like the default splash... thanks bro....
newei
heres the file
http://www.mediafire.com/?urkjhzcugs0wex8
thank you so much bro
Click to expand...
Click to collapse
how do i get this on my phone?
Nice work aldeldotcom!
Of course, before I saw this, I cleaned up the resized image a bit, so I may as well link to it.
http://www.mediafire.com/?ts7q2t2q7bovao1
I actually haven't gotten it onto my phone yet. I lost root with the OTA and haven't managed to get it back yet, (I haven't tried too hard either... yet) but it should look pretty good.
Of course, the REAL file would still be better...
"Fender" splash screen AND stock recovery
So I made it work.... I have this splash screen, root, AND stock recovery. (Ya know, in case I want more OTAs...)
Here's my story. And I'm stickin' to it.
You will need root. SuperOneClick worked for me. I did have to follow his instructions about toggling USB debugging on and off when it went into a loop. I also had a snag in that SuperUser.apk didn't actually load onto the phone, even though it was rooted. Apparently it's a lack of memory problem. There's a simple fix though; after rooting, copy the superuser.apk file from the SuperOneClick folder onto you SD card. Open it with ASTRO and install it like any other non-market app. You're good to go.
After getting root, here's what I did.
I flashed the 2010 SPL from the thread below by putting the zip on my sdcard and flashing it from Amon's recovery. There were some nervous moments, but it worked fine for me.
BE CAREFUL!!!! THIS IS WHERE YOU CAN BRICK YOUR PHONE. BE CAREFUL! (did I say to be careful?)
http://forum.xda-developers.com/showthread.php?t=794447
This is the link to the actual SPL I used: http://rapidshare.com/files/267475618/update.Engineering-SPL-HBOOT-1.33.2010-signed.zip
Next, I renamed the splash screen splash.rgb565 and put it in the same folder as my fastboot tool and followed the unlockrs instructions here:
http://theunlockr.com/2010/04/15/ho...for-all-320-x-480-resolution-android-devices/
Read their directions throughly, but here are the commands you need from fastboot:
fastboot flash splash1 splash.rgb565
fastboot reboot
Click to expand...
Click to collapse
And finally I reflashed the stock SPL through fastboot as instructed here:
http://forum.cyanogenmod.com/index.php?/topic/644-mytouch-12-tutorial/
This link: http://www.megaupload.com/?d=9Z7K1PAL
has the stock radio and SPL. I just put the SPL in the folder with fastboot and followed their instructions
AGAIN, BE CAREFUL!!! FLASHING SPLs CAN BE DANGEROUS.
PLEASE, read the instructions carefully and multiple times, but, here are the commands you'll need:
fastboot flash hboot hboot.nb0 (that's a zero at the end)
fastboot reboot-bootloader
Click to expand...
Click to collapse
Then I finally reflashed the stock recovery from a terminal emulator on the phone using DonJaun's instructions from here:
http://forum.xda-developers.com/showpost.php?p=11136815&postcount=266
The recovery file is here: http://forum.xda-developers.com/attachment.php?attachmentid=509115&d=1296862264
Here's his quote:
DonJuan692006 said:
Download the attached "Flash_image.zip", unzip the file, and put in on the root of your SD card. Then open up terminal on the phone and type the following hitting enter at the end of each line:
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 755 /system/bin/flash_image
mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
flash_image recovery /sdcard/*name of recovery*.img
reboot recovery
Click to expand...
Click to collapse
So that's where I'm at. As close to stock as I'm probably going to get, but still with root!
KT
BTW: I had the OTA on my phone before I did all this, but if I were still on 1.6, I would go in the same order and not try and apply the OTA first, if for no other reason than getting root on 1.6 is easy. Use UniversalAndRoot. Done. Then:
flash engineering SPL from recovery,
flash splash screen and original SPL from fastboot (in that order), and finally
flash stock recovery from terminal.
Then I would probably UNROOT before applying the OTA. I was unrooted when I got it, and I think I might be the only person not having trouble with it. Just my 2 cents..
I updated my post to include the actual flash_image command argument needed for my little guide.
As for applying the update. I would do it manually. You can download the update file from here, rename it to update.zip, put it on your SD card, and flash it from recovery. Before flashing it, make sure you do a "Wipe data/factory reset". For my myTouch 1.2 the update ran like crap, until I went it and did a wipe. It seems the update doesn't do a very good job of cleaning up the system cache before updating, which leads to ridiculous lag. A full wipe will help it run a million times better.
on the last part when you re-flash the stock hboot and recovery..
i flashed the hboot first according the guide then when i tried to flash the recovery it failed.. so i reflash the eng spl again then flash the stock recovery after that i re-reflashed the stock spl.. and it works... iam now left with "close to stock" fender??
about the stock recovery, is it the one when it onl shows you triangle with exclamation mark?
yes thats stock recovery. anywei
if you like you can do manual update if you want to update to froyo thats what i did.. after doing what i stated above.. now im on my stock froyo fender running smooth..
Sent from my T-Mobile myTouch 3G my fender using Tapatalk
ardeldotcom said:
yes thats stock recovery. anywei
if you like you can do manual update if you want to update to froyo thats what i did.. after doing what i stated above.. now im on my stock froyo fender running smooth..
Sent from my T-Mobile myTouch 3G my fender using Tapatalk
Click to expand...
Click to collapse
yes but i after that i put the update.zip in the MMC but it did not read it.
Just putting the word out...
There are people who have the original image who have visited the forum and are willing to donate their original Splash image if there is someone who can post direction on how to get it off the phone.
did you check if its update.zip ( no wrong spelling) and if your pc showing file extension because if not maybe you have it spelled as update.zip.zip...
Sent from my T-Mobile myTouch 3G using Tapatalk
i hope someone can post it on how to. but for now maybe you could try the splash imges we posted.. its almost close to the origial..
Sent from my T-Mobile myTouch 3G using Tapatalk
I'm fine, thanks.
I don't really need to change my splash screen. People are certainly welcome to use the one that's been synthesized. I'm just hoping for about as complete a restore for the Fender as we can get and that image would really seal the deal. Getting it off just seems to be the challenge.
Also working on a clean and usable 2.2.1 image in the event one should want to go there if they happen to release this rumoured fix or try it with an overclocked kernel. Hopefully we will see some targeted at the 1.2/Fender owners with some encouragement. Work so far impressed a T-Mobile rep who was a fan of the phone when I went in to pay for a data plan. It's getting pretty clean and snappy as is.
In the efforts of bringing this to a successful close I have created the following thread. http://forum.xda-developers.com/showthread.php?p=11341358
Seems the splash image and the entire original ROM can be fetched and reconstructed.
update stuck
so i did the whole process and i ended up with "stock" Fender Edition, i did a system update, it downloaded the update so i installed it but after it's done reseting it's just stuck at the splash screen, and now i cant boot to the system anymore...
help please?
Questions...
Can you boot your phone into Recovery, Fastboot/HBoot? Have you tried asking for help in the OTA thread? http://forum.xda-developers.com/showthread.php?t=906006 More super smart android people seem to be watching that one and may be able to help.
WoefulDerelict said:
Can you boot your phone into Recovery, Fastboot/HBoot? Have you tried asking for help in the OTA thread? http://forum.xda-developers.com/showthread.php?t=906006 More super smart android people seem to be watching that one and may be able to help.
Click to expand...
Click to collapse
i can boot into fast/h-boot and i am able to boot to the recovery screen(the one with the ! mark, and also the 2e)
but i cannot do anything, fastboot gets remote not allow, tried to flash the eng SPL is also failed
danxtian said:
i can boot into fast/h-boot and i am able to boot to the recovery screen(the one with the ! mark, and also the 2e)
but i cannot do anything, fastboot gets remote not allow, tried to flash the eng SPL is also failed
Click to expand...
Click to collapse
Going to have to goldcard root. There's a guide in my sig.
Sent from my LG-P500 using Tapatalk
DonJuan692006 said:
Going to have to goldcard root. There's a guide in my sig.
Sent from my LG-P500 using Tapatalk
Click to expand...
Click to collapse
but i can't access my phone to turn the USB debugging on, is there anyway to make the goldcard?
danxtian said:
but i can't access my phone to turn the USB debugging on, is there anyway to make the goldcard?
Click to expand...
Click to collapse
Use a friends phone that has Android on it.
Sent from my LG-P500 using Tapatalk
DonJuan692006 said:
Use a friends phone that has Android on it.
Sent from my LG-P500 using Tapatalk
Click to expand...
Click to collapse
hmm... will it work if i use HD2 running android on it?
Followed these instuctions:
http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s/
My phone is now stuck at the google logo and will not go past. After rooting and clockwork i was not able to load anything else but i would not boot.
Please help.. Thank You
seriously? there is like 4 threads on how to root it, and you go with one that you shouldnt.. lol
it had pictures.. lol
all the threads on here talk about specific phone models and i wasnt sure so i just went with it... Bad choice on my part..
hopefully someone can help
load up fastboot and try to get to recovery if you can then awesome.. try wiping everything and see if that fixes anything
Pull the battery, hold volume up and power and follow this post to get into recovery. Then like shabby penguin said, when you get into recovery wipe everything and you should be good to go. Again, the post I linked you to is the proper way to root the 4g...
http://forum.xda-developers.com/showpost.php?p=13570498&postcount=5
i can get into recovery and i wiped the phone, but still doesnt help.
opie2l said:
i can get into recovery and i wiped the phone, but still doesnt help.
Click to expand...
Click to collapse
Oh, guess I didnt catch that.
ok your best bet it to go into fastboot and flash the clockworkmod 3.0.2.4
did you do the oem unlock command?
yeah i did the oem unlock.
ok well assuming you followed the directions from this guy, then you have a diff bootimg on there i can toss a few files that may fix it, but no garuntees...
seriously tho
(You should see that “LOCK STATE” says “UNLOCKED”, meaning your Nexus S is rooted.)
Click to expand...
Click to collapse
is posted on his site.. that would be a good indicator to me to stop listening to anything he said.. he then later in the comments was trying to help someone and told them if usb wasnt working then use a microsd adapter to put the files on..
yeah i am kicking my self in the a$$. Is there anyway do just get it back to stock?
well have you tried flashing a kernel? if it gets to bootani then its usually rom erros, freezing at spalsh screens is generally kernel images
is it possible to load a kernel when i cant see the phones memory from the computer???
someone has to have some idea of to fix this...
just got me to stock unrooted phone.. please
yes, download this
boot into fastboot and type in fastboot flash boot /path/to/natarchy.img
replace /path/to with where its located.. this should get you rollin again
thank you... thank you... thank you!!!!!!!!
i have learned my lesson and i wont stray from the xda forum next time.
Again thank you
I have a similiar issue as OP...I tried to flash netarchy kernel with kernal manager and then phone rebooted and got stuck at google logo.
I have installed SDK...google drivers, but when I try to flash the kernel I get waiting for device in command prompt. Same error when I type "fastboot oem unlock"
Any ideas?
Skillz1318 said:
I have a similiar issue as OP...I tried to flash netarchy kernel with kernal manager and then phone rebooted and got stuck at google logo.
I have installed SDK...google drivers, but when I try to flash the kernel I get waiting for device in command prompt. Same error when I type "fastboot oem unlock"
Any ideas?
Click to expand...
Click to collapse
Waiting for device means Windows does not recognize phone. Reinstall drivers.
ok sounds like a driver issue, i used pdanet to install the drivers i needed. try fastboot devices, if it doesnt show anything then your phone isnt connected
Ok used my mac and was able to get cwm recovery on device. I could mount it. Now how can I flash back to stock. I9020A att 3G version. Booting now I see google and a lock.
Thanks everyone!
Im looking to re-root my N7 after upgrading to 4.1.2 and losing root. Ive managed to unlock my device but cant seem to do anything else as it gets stuck on "<waiting for device>" and ive tried restart bootloader etc but to no avail. Im using Ubuntu 12.10 and will be using the Terminal to try and re-root it. New to using the terminal so no sure as to what to do completely.
I'm also looking to downgrade the bootloader to the previous version so i can add CWM as a Recovery. Any help would be greatly appreciated.
Why are you using the terminal when there are good tools/one click solutions ??
is debuging on?
Let me just bring the two of you together: http://forum.xda-developers.com/showthread.php?t=1936767
I find it amusing that your posts were six minutes apart. I hope that you find this helpful.
360porcento said:
Why are you using the terminal when there are good tools/one click solutions ??
is debuging on?
Click to expand...
Click to collapse
Id rather be able to root and unlock without using tools/one click solutions as they are not always the best on Linux and its more in the sport of android doing it yourself.
Tonttunator said:
Let me just bring the two of you together: http://forum.xda-developers.com/showthread.php?t=1936767
I find it amusing that your posts were six minutes apart. I hope that you find this helpful.
Click to expand...
Click to collapse
Im trying to flash to boot image but it get stuck waiting for the device:-
[email protected]:~/Downloads$ ./fastboot-linux boot bootloader-grouper-3.34.img
creating boot image...
creating boot image - 2125824 bytes
< waiting for device >
Not sure if i have done anything wrong here if i have let me know.
mackay508 said:
[email protected]:~/Downloads$ ./fastboot-linux boot bootloader-grouper-3.34.img
creating boot image...
creating boot image - 2125824 bytes
< waiting for device >
Not sure if i have done anything wrong here if i have let me know.
Click to expand...
Click to collapse
Maybe your version of fastboot is not exactly compatible with the bootloader, that's also why rooting is so hard. If able, try the windows version that comes with one of the Toolkits. Please, even if you don't want to, give it a try. Might make your life easier.
Edit: Try flashing the bootloader permanently, that's what I did, I just noticed you're trying to temporarily boot it.
I cant seem to get out of TWRP. I use adb and i used "adb boot recovery" and i cant seem to get out. The issue i think i have is that the adb keeps pushing the command to the phone. Now before you say "Just unplug the phone and reboot it"... I did that. Now it seems that the code is stuck with the phone . Iv tried to put it into TWRP my self without adw and tryed to reboot it but that didnt work. No other tread helped me. If you could tell me how to how to fix this or link me to a thread somewhere else. Its a Verizon phone.
Thanks -
Subby
if it helps: I was trying to root :good:
Shubbyshak said:
I cant seem to get out of TWRP. I use adb and i used "adb boot recovery" and i cant seem to get out. The issue i think i have is that the adb keeps pushing the command to the phone. Now before you say "Just unplug the phone and reboot it"... I did that. Now it seems that the code is stuck with the phone . Iv tried to put it into TWRP my self without adw and tryed to reboot it but that didnt work. No other tread helped me. If you could tell me how to how to fix this or link me to a thread somewhere else. Its a Verizon phone.
Thanks -
Subby
if it helps: I was trying to root :good:
Click to expand...
Click to collapse
I got the phone to RAM dump boot i have no idea how i got it there. But its something else. THE PHONE IS NOT BRICKED.
So you're stuck in recovery??? If so, just flash one of the Verizon based roms that should get you going.
indoz said:
So you're stuck in recovery??? If so, just flash one of the Verizon based roms that should get you going.
Click to expand...
Click to collapse
Thanks but i got out of it. I think it was because i tried to root is so the microsd got corrupted because the rooting process screwed up
Thanks -
Shubb
Shubbyshak said:
I cant seem to get out of TWRP. I use adb and i used "adb boot recovery" and i cant seem to get out. The issue i think i have is that the adb keeps pushing the command to the phone. Now before you say "Just unplug the phone and reboot it"... I did that. Now it seems that the code is stuck with the phone . Iv tried to put it into TWRP my self without adw and tryed to reboot it but that didnt work. No other tread helped me. If you could tell me how to how to fix this or link me to a thread somewhere else. Its a Verizon phone.
Thanks -
Subby
if it helps: I was trying to root :good:
Click to expand...
Click to collapse
This happened to me. I just had to use the hardware buttons to boot into recovery then reboot from there and that got me out of the loop. Not sure why that happens.