Related
I, an ignorant vibrant user eager to break into the world of ROMS, finally and successfully rooted my phone with the one click root.
One Click Lagfix from the marketplace immediately thereafter. Phone was blazing fast.
I decided to push my stupid limits. I tried to download and install Eugene's Vibrant Hybrid final ROM that would give me glorious, stock android. I followed the instructions I found for "installing a ROM":
Copy the zip to the root.
Boot into recovery.
Go into clockwork recovery.
factory reset.
install zip from sd card.
after that's done, reboot.
I got a little chimy, should-be-startup noise, (not the standard vibrant start-up noise, but what I expect would be the new ROM start-up noise I downloaded) and then nothing. Just the Vibrant screen.
I can boot into recovery mode, but I don't know what to do next. I tried to find the backup I made on Clockwork, but it was NOT THERE. I am now panicking and trying not to do anything stupid to my phone.
read on Eugene's site that it could be that I don't have the correct kernel flashed to support the ROM...? At this point, I kind of just want my phone back while having to lose the least amount of data. Please Help.
and before I tried installing the ROM, I used the one-click lag fix from the market on my already rooted phone.
Thanks!
james
Did you disable the lag fix before flashing?
Sent from my SGH-T959 using XDA App
no, didn't realize that it would be an issue until after flashing the ROM. I think I'm stuck in a boot loop... and I have access to a mac only at the moment. Tomorrow I'll have access to a PC if ODIN could help at all...
Search for "froyo that doesnt brick your phone" flash if with odin and after that flash back to stock.
Sent from my SGH-T959 using XDA App
Will this restore my data and settings...?? What will I lose?
In a weird. Everything. Unless you made an external backup. Eugene's will wipe the phone.
Sorry bud
Gl.
Sent from my SGH-T959 using XDA App
jamespwolpert said:
I, an ignorant vibrant user eager to break into the world of ROMS, finally and successfully rooted my phone with the one click root.
One Click Lagfix from the marketplace immediately thereafter. Phone was blazing fast.
I decided to push my stupid limits. I tried to download and install Eugene's Vibrant Hybrid final ROM that would give me glorious, stock android. I followed the instructions I found for "installing a ROM":
Copy the zip to the root.
Boot into recovery.
Go into clockwork recovery.
factory reset.
install zip from sd card.
after that's done, reboot.
I got a little chimy, should-be-startup noise, (not the standard vibrant start-up noise, but what I expect would be the new ROM start-up noise I downloaded) and then nothing. Just the Vibrant screen.
I can boot into recovery mode, but I don't know what to do next. I tried to find the backup I made on Clockwork, but it was NOT THERE. I am now panicking and trying not to do anything stupid to my phone.
read on Eugene's site that it could be that I don't have the correct kernel flashed to support the ROM...? At this point, I kind of just want my phone back while having to lose the least amount of data. Please Help.
and before I tried installing the ROM, I used the one-click lag fix from the market on my already rooted phone.
Thanks!
james
Click to expand...
Click to collapse
its just a simple user error. Honestly imo opinion, if you are using the lagfix option found on the market, flashing to other roms reformats /data and /system and such undoing it. So thats not where your issue came from the flashing. Before the flash, if you were on stock jdf, the flashing the hybrid final rom didnt update your baseband/modem.bin and i am pretty sure that would put you in your situation. Possible situation number 2. You had the ota update on your phone already. Meaning you were running ji6 then the rom update.zip may have been corrupted or incomplete.
to fix either one of these situations is simple. As long as the answer to my next question is a hell no. Did you flash jacs xmod voodoo kernel after you flash the hybrid rom?? The faster you reply to this the faster i can get to to a solution. You will also need a computer that has adb installed and properly recognizing your phone.
IF YOU DID FLASH THE VOODOO LAGFIX YOU WILL NEED ACCESS TO A COMPUTER WITH ODIN AND ANDROID SDK!! WETHER IT BE A MAC WITH PARRELLS OR A VM OR LINIX OR WINDOWS.
a4 moda said:
In a weird. Everything. Unless you made an external backup. Eugene's will wipe the phone.
Sorry bud
Gl.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
That is not true. Anything on his internal memory will be perfectly intact. And if he can still get into cwm recovery, he adb push a few files to the root of his sd card and boot right up depending the cause
jumaaneface said:
its just a simple user error. Honestly imo opinion, if you are using the lagfix option found on the market, flashing to other roms reformats /data and /system and such undoing it. So thats not where your issue came from the flashing. Before the flash, if you were on stock jdf, the flashing the hybrid final rom didnt update your baseband/modem.bin and i am pretty sure that would put you in your situation. Possible situation number 2. You had the ota update on your phone already. Meaning you were running ji6 then the rom update.zip may have been corrupted or incomplete.
to fix either one of these situations is simple. As long as the answer to my next question is a hell no. Did you flash jacs xmod voodoo kernel after you flash the hybrid rom?? The faster you reply to this the faster i can get to to a solution. You will also need a computer that has adb installed and properly recognizing your phone.
IF YOU DID FLASH THE VOODOO LAGFIX YOU WILL NEED ACCESS TO A COMPUTER WITH ODIN AND ANDROID SDK!! WETHER IT BE A MAC WITH PARRELLS OR A VM OR LINIX OR WINDOWS.
Click to expand...
Click to collapse
I didn't flash **** after that. Just the Hybrid mod, then I was stuck. The steps I mentioned in my process were the only things that ever ever happened.
also, yes, I (was) running JI6 as well. Until this fiasco.
Eugene's thread for the hybrid mod also has files posted for, quote, "reboots and freezes" with the file name JFDkernanmodemji2.zip. All things that have been mentioned positively at one point or another in this thread. Since I am pretty sure I don't have the appropriate kernel to run the ROM, do I simply push the JFDkernanmodemji2.zip file to my root, flash it, then flash the ROM again and life will be good?
jamespwolpert said:
Eugene's thread for the hybrid mod also has files posted for, quote, "reboots and freezes" with the file name JFDkernanmodemji2.zip. All things that have been mentioned positively at one point or another in this thread. Since I am pretty sure I don't have the appropriate kernel to run the ROM, do I simply push the JFDkernanmodemji2.zip file to my root, flash it, then flash the ROM again and life will be good?
Click to expand...
Click to collapse
Indeed. If it doesn't work. U had a messed up download. At that point redownload and push to sd root
jumaaneface said:
Indeed. If it doesn't work. U had a messed up download. At that point redownload and push to sd root
Click to expand...
Click to collapse
how do I push files to my vibrant? Where do I start?
jamespwolpert said:
how do I push files to my vibrant? Where do I start?
Click to expand...
Click to collapse
Do you have android sdk on your pc?
jumaaneface said:
Do you have android sdk on your pc?
Click to expand...
Click to collapse
I think. When I open it, it the app is called Java and the titlebar says Android SDK and AVD Manager
jamespwolpert said:
how do I push files to my vibrant? Where do I start?
Click to expand...
Click to collapse
jamespwolpert said:
I think. When I open it, it the app is called Java and the titlebar says Android SDK and AVD Manager
Click to expand...
Click to collapse
boot your phone into clockwork recovery and plug in to computer. Then open a command prompt window. you can type in cmd into search bar in windows to open it up. Then type adb devices into the little black window. tell me what happens when you do this. Do you have gtalk or aim? This will go by faster If you have one
jumaaneface said:
boot your phone into clockwork recovery and plug in to computer. Then open a command prompt window. you can type in cmd into search bar in windows to open it up. Then type adb devices into the little black window. tell me what happens when you do this. Do you have gtalk or aim? This will go by faster If you have one
Click to expand...
Click to collapse
yeah, I've got gtalk.
gmail is [email protected]
Personal assist, wow that's awesome.
So what came if this? What's the outcome?
I'm curious, please update.
Sent from my SGH-T959 using XDA App
Push pppuuuuush..baby deliveried yet?? An update on steps by steps?
I am ready to break something!!!
OK, after spending over a day reading and trying different things to no avail, my brain is a jumbled mess
i have a 16gb NT it was updated to the 1.4.3 when i started. I rooted it using indirect/brianf21 sd card method. everything worked fine for the little bit that i messed with it in this state. i then moved on to Veronica's CM7beta_ribbon_ICS rom for the most part everything was working. I installed a few apps from the market and on a reboot i got stuck in a bootloop. powered off, bootloop again. so i booted into CWM and tried reflashing the ROM only to be met with the 'please restart you device' screen. its all downhill from there. i can currently boot into CWM internally and have tried many different methods. so right now i dont get the 'restart' screen as it just goes into CWM. I have never worked with ABD but have been fighting drivers trying to get my nook to show up and having no luck so that i might try something there. i am new to rooting on the NT but have rooted and flashed different roms to my phone so i feel i have a basic concept. i dont know if im having so much of an issue cuz of the 1.4.3 or what **sigh**
I am now defeated and am in need of some help!!! haha! if anyone has anything to offer i would be so very thankful!
neonblur said:
I am ready to break something!!!
OK, after spending over a day reading and trying different things to no avail, my brain is a jumbled mess
i have a 16gb NT it was updated to the 1.4.3 when i started. I rooted it using indirect/brianf21 sd card method. everything worked fine for the little bit that i messed with it in this state. i then moved on to Veronica's CM7beta_ribbon_ICS rom for the most part everything was working. I installed a few apps from the market and on a reboot i got stuck in a bootloop. powered off, bootloop again. so i booted into CWM and tried reflashing the ROM only to be met with the 'please restart you device' screen. its all downhill from there. i can currently boot into CWM internally and have tried many different methods. so right now i dont get the 'restart' screen as it just goes into CWM. I have never worked with ABD but have been fighting drivers trying to get my nook to show up and having no luck so that i might try something there. i am new to rooting on the NT but have rooted and flashed different roms to my phone so i feel i have a basic concept. i dont know if im having so much of an issue cuz of the 1.4.3 or what **sigh**
I am now defeated and am in need of some help!!! haha! if anyone has anything to offer i would be so very thankful!
Click to expand...
Click to collapse
in order to get drivers working while in recocery mode you need to find the product id of the nook while its in cwm. in windows you need to go to device manager and check to see if your nook shows up in "other devices". then right click and go to properties and go to the tab that relates to hardware and find the neccessary info.
after that you should see two lines. ypu need to copy those two to the android_win.inf and modify the lines in there with notepad or something.
then try installing drivers and it shouls pick it up
Sent from my Nook Tablet CM7 BETA using xda premium app
ShinnAsuka said:
in order to get drivers working while in recocery mode you need to find the product id of the nook while its in cwm. in windows you need to go to device manager and check to see if your nook shows up in "other devices". then right click and go to properties and go to the tab that relates to hardware and find the neccessary info.
after that you should see two lines. ypu need to copy those two to the android_win.inf and modify the lines in there with notepad or something.
then try installing drivers and it shouls pick it up
Sent from my Nook Tablet CM7 BETA using xda premium app
Click to expand...
Click to collapse
thanks for the reply. ok my nook is showing up as a mass storage device under other devices but is also showing up under android phone as 'android composite ADB interface' and also under portable devices as 2 drives G: and H: both unclickable. when i right click the android phone i get a hardware tab but all i see there is device functions and device functions summery so im not sure of the info that you are referring to that i need. i have been at this all day and apologize if i am missing something because im tired haha. the other file i found was called android_winusb.inf, is this the right one? thanks again for your help!
neonblur said:
thanks for the reply. ok my nook is showing up as a mass storage device under other devices but is also showing up under android phone as 'android composite ADB interface' and also under portable devices as 2 drives G: and H: both unclickable. when i right click the android phone i get a hardware tab but all i see there is device functions and device functions summery so im not sure of the info that you are referring to that i need. i have been at this all day and apologize if i am missing something because im tired haha. the other file i found was called android_winusb.inf, is this the right one? thanks again for your help!
Click to expand...
Click to collapse
yea that inf file is the one you need to modify. but you already have adb composite interface... so that means drivers are installed.
what happens when you do adb devices after you get into cwm. what's the output?
Sent from my Nook Tablet CM7 BETA using xda premium app
this is where i am a complete noob. i have never used ADB and have been reading threads about people using it but the light bulb has just not gone off yet. i know how to get to the command prompt, heh, so that is one thing. what program do i need to install, is it the android SDK? thanks for your quick reply, i am generally a quick learner when it comes to this stuff just need to get over the ADB hurdle
neonblur said:
this is where i am a complete noob. i have never used ADB and have been reading threads about people using it but the light bulb has just not gone off yet. i know how to get to the command prompt, heh, so that is one thing. what program do i need to install, is it the android SDK? thanks for your quick reply, i am generally a quick learner when it comes to this stuff just need to get over the ADB hurdle
Click to expand...
Click to collapse
did you download the drivers and adb zip from one of the threads? that archive should have all you need for adb. after extractng you need to navigate to the extracted folder and do adb devices.
try looking in thr general section for these drivers I was talking about.
there should be a thread by lavero burgos in there.
Sent from my Nook Tablet CM7 BETA using xda premium app
ShinnAsuka said:
did you download the drivers and adb zip from one of the threads? that archive should have all you need for adb. after extractng you need to navigate to the extracted folder and do adb devices.
try looking in thr general section for these drivers I was talking about.
there should be a thread by lavero burgos in there.
Sent from my Nook Tablet CM7 BETA using xda premium app
Click to expand...
Click to collapse
Ha! got it going...ok so when i entered ADB devices it gives me:
2015170003944006 recovery
im feeling better about maybe getting this unbricked
neonblur said:
Ha! got it going...ok so when i entered ADB devices it gives me:
2015170003944006 recovery
im feeling better about maybe getting this unbricked
Click to expand...
Click to collapse
ok well now you have adb working. now the problem is how to fix your problem lol... I'll see if I can think of something.
in the meantime can you go into detail as to how you got tto your current situation?
EDIT: do you get any errors when booting into cwm? like not being able to mount a certain drive or something?
Sent from my Nook Tablet CM7 BETA using xda premium app
no errors booting into cwm internal and never had a problem when booting into it from an sd card. i flashed it internally hoping it would be a little easier seeing as how i only have one sd card but i am going to go get another today just to work through this.
nook started on 1.4.3 i rooted it using brianf23 and indirects sd card method. market and everything worked great. so i flashed Veronica's CM7beta_ribbon_ICS rom. everything for the most part was working, tho i did notice that some menu items would not open for me but they were noting i really needed to mess with at the time. so i installed a few apps and was done for the day. turned it on the next day and got stuck in a bootloop, so powered off and rebooted but got the same bootloop. booted into recovery did the standard dalvik cache ect and reflashed the rom, hoping this might fix the loop. upon rebooting is when i got stuck at the 'please reboot your device' screen. i have tried several methods of just flashing to stock ect, formatted my sd correctly and made sure it was active to try and flash back to stock that way but my nook will not boot from sd. so 12+ hours later i hung my head and asked for help lol! thanks to you i am able to start ADB no clue what to do but hey....step in the right direction!
Happy Dance
i got it working back to stock!! thank you so much for getting me going with ADB, without your help i would have stayed lost. i used kring789's ADB instructions and *poof* it rebooted to stock :good::good: thanks again for your help!
neonblur said:
i got it working back to stock!! thank you so much for getting me going with ADB, without your help i would have stayed lost. i used kring789's ADB instructions and *poof* it rebooted to stock :good::good: thanks again for your help!
Click to expand...
Click to collapse
good job on the fix. glad to help
Sent from my Nook Tablet CM7 BETA using xda premium app
Here's what happened:
-Had Eryigit GB-Installed PA w/ mevordel's kernel 4.0Rebooted recoveryStarted weird bootloop=would go back into recovery and act like its installing something, then reboot, ad infinitum
I tried reflashing Eryigits rom from odin,
then repartitioning. Somehow it was able to boot into Eryigit's ROM once, but the capacitative buttons didnt work and I couldnt reboot into anything except for download mode or a normal samsung logo bootloop.
I tried a few more things in Odin (not blindly, mind you) and still no go.. I can get it into recovery only if I flash a bootloader in Odin and auto-reboot it, otherwise it just goes back to the bootloop.
I believe I have the same problem as in this thread
I'm trying to adb into my device, but am having trouble detecting it. It'll connect in Odin fine, but not in adb, whether in download mode or just hanging at the samsung logo.
What can I do to fix this without adb working? I'm hoping for an odin fix for it, but through the mountains of threads I've been reading I don't believe there to be.
According to the thread above ^ it needs to be repartitioned manually... I read all the threads linked to and tried adb & heimdall but no luck after like 3+ weeks ):
Can anybody give me a better explanation of whats going on or throw me some troubleshooting advice?
<3 <3 <3
bmxer4130 said:
Here's what happened:
-Had Eryigit GB-Installed PA w/ mevordel's kernel 4.0Rebooted recoveryStarted weird bootloop=would go back into recovery and act like its installing something, then reboot, ad infinitum
I tried reflashing Eryigits rom from odin,
then repartitioning. Somehow it was able to boot into Eryigit's ROM once, but the capacitative buttons didnt work and I couldnt reboot into anything except for download mode or a normal samsung logo bootloop.
I tried a few more things in Odin (not blindly, mind you) and still no go.. I can get it into recovery only if I flash a bootloader in Odin and auto-reboot it, otherwise it just goes back to the bootloop.
I believe I have the same problem as in this thread
I'm trying to adb into my device, but am having trouble detecting it. It'll connect in Odin fine, but not in adb, whether in download mode or just hanging at the samsung logo.
What can I do to fix this without adb working? I'm hoping for an odin fix for it, but through the mountains of threads I've been reading I don't believe there to be.
According to the thread above ^ it needs to be repartitioned manually... I read all the threads linked to and tried adb & heimdall but no luck after like 3+ weeks ):
Can anybody give me a better explanation of whats going on or throw me some troubleshooting advice?
<3 <3 <3
Click to expand...
Click to collapse
If you are sure of what you state, solution is from post 39 at the following adress
http://forum.xda-developers.com/showthread.php?t=1676606&page=4
But check if you have a true "memory partitioning issue" best is said when wiping cache you get many advices about what is wrong (normaly in red letters!)
good luck and welcome to our club!
lolo9393 said:
If you are sure of what you state, solution is from post 39 at the following adress
http://forum.xda-developers.com/showthread.php?t=1676606&page=4
But check if you have a true "memory partitioning issue" best is said when wiping cache you get many advices about what is wrong (normaly in red letters!)
good luck and welcome to our club!
Click to expand...
Click to collapse
Hey thanks. I already read through all that stuff ^ and am not having much luck. Is there some way I can IM you or something? PM me if so. You seem very knowledgeable about this matter
bmxer4130 said:
Hey thanks. I already read through all that stuff ^ and am not having much luck. Is there some way I can IM you or something? PM me if so. You seem very knowledgeable about this matter
Click to expand...
Click to collapse
Normally we can solve this within a thread that can help any other getting the same issue.
i am still very involved because end 2011 I got in trouble (I was expecting to have much better performance by flashing a Gnote kernel !!!!) and stayed for months reading at XDA for a save. (also good english training then)
your Pb:
did you check by wiping if you are in this situation? You should get advice that (partition from n 14 and upper can't be read) if so follow the tracks from the relevant post and tell me what goes wrong with you.
I fixed it! you will do it the same!
PS:To enter Adb you should flash FIRST a kernel (with ODIN) rj14 for int'll version or entropy for US model
lolo9393 said:
Normally we can solve this within a thread that can help any other getting the same issue.
i am still very involved because end 2011 I got in trouble (I was expecting to have much better performance by flashing a Gnote kernel !!!!) and stayed for months reading at XDA for a save. (also good english training then)
your Pb:
did you check by wiping if you are in this situation? You should get advice that (partition from n 14 and upper can't be read) if so follow the tracks from the relevant post and tell me what goes wrong with you.
I fixed it! you will do it the same!
PS:To enter Adb you should flash FIRST a kernel (with ODIN) rj14 for int'll version or entropy for US model
Click to expand...
Click to collapse
Ok so I got into recovery with entropy's kernel and wiped everything,
When I try to mount usb storage it says:
E: Unable to write to ums lunfile (No such file or directory)
Click to expand...
Click to collapse
So yeah, its the internal memory.. now if i could just get adb shell to work right
okay now I'm just trying to adb shell into it from win7 x64 and fedora 18 linux with no luck. in win7 it shows up in adb devices, but i cant connect to it, right now im thinking its because of the java sdk and problems with the fact that its a 64 bit comp. in fedora adb devices says ???????????? offline usb:2-2...
bmxer4130 said:
okay now I'm just trying to adb shell into it from win7 x64 and fedora 18 linux with no luck. in win7 it shows up in adb devices, but i cant connect to it, right now im thinking its because of the java sdk and problems with the fact that its a 64 bit comp. in fedora adb devices says ???????????? offline usb:2-2...
Click to expand...
Click to collapse
So, you were able to flash entropy's kernel (said you have a US device?) Now you can go to recovery mode and enter adb call for;" adb devices" and your will and must show up. No need to mount anything. I 've never, under win7, tryied this. so no comment.
Would you mind to give me what is said after you do a single wipe because we have to be sure your problem is really a memory partition wreck.
lolo9393 said:
So, you were able to flash entropy's kernel (said you have a US device?) Now you can go to recovery mode and enter adb call for;" adb devices" and your will and must show up. No need to mount anything. I 've never, under win7, tryied this. so no comment.
Would you mind to give me what is said after you do a single wipe because we have to be sure your problem is really a memory partition wreck.
Click to expand...
Click to collapse
Ok, I was able to adb shell and rebuild the partition table, and it was indeed messed up, and I can mount usb storage, but I still can't get it to boot into any rom, and it refuses to boot into cwm recovery unless its just rebooted from odin. in recovery in the log it has an error about libc.so, idk if that has anything to do with it though. I'm beginning to think the problem may have to do with my usb cable. I accidentally switched the stock one with a Galaxy SII one, which should be fine, but maybe not.
bmxer4130 said:
Ok so I got into recovery with entropy's kernel and wiped everything,
When I try to mount usb storage it says:
So yeah, its the internal memory.. now if i could just get adb shell to work right
Click to expand...
Click to collapse
The "mount USB storage" option is for mounting the SD card on your computer. That error is because you don't have an external SD card inserted.
Mevordel said:
The "mount USB storage" option is for mounting the SD card on your computer. That error is because you don't have an external SD card inserted.
Click to expand...
Click to collapse
hehehe, I kinda realized that after posting. Derp.
But I think it may have to do with /data & maybe other folders/files being R/O (read only..) instead of R/W, as per this thread so I am now convinced I need the bootchain for the galaxy player, but this is just a sneaking suspicion, I need to do some more digging before making a fool of myself again
bmxer4130 said:
hehehe, I kinda realized that after posting. Derp.
But I think it may have to do with /data & maybe other folders/files being R/O (read only..) instead of R/W, as per this thread so I am now convinced I need the bootchain for the galaxy player, but this is just a sneaking suspicion, I need to do some more digging before making a fool of myself again
Click to expand...
Click to collapse
Ok you have all the needed stuff and now you are trained and skilled enough. You will succeed.
Why not you to try flashing Mevordel's GB Chip 1.5 rom that is in my view the best for your device, it is light simple and fast and no need for more for what we expect from this excellent but outdated product.
lolo9393 said:
Ok you have all the needed stuff and now you are trained and skilled enough. You will succeed.
Why not you to try flashing Mevordel's GB Chip 1.5 rom that is in my view the best for your device, it is light simple and fast and no need for more for what we expect from this excellent but outdated product.
Click to expand...
Click to collapse
Yes, I tried flashing it in cwm, along with eryigit (both with entropys kernel flashed over them) and PA venturi, but it refuses to boot properly. If it is the bootchain, how can I get a dump of a working one?
And I was able to dump a lot of stuff from [adb pull */*] and can access logs and dmesg, but havent inspected them fully. Is there an easy way to read the boot log and/or setup a custom log to run preboot? I figure that wouldnt be necessary since the linux kernel does a fine job of logging itself.
And yes I think I am skilled enough now, just was confused how to get to the adb shell, but I'm fairly well versed in linux, so the shell is relatively comfortable for me.
But if I'm able to figure it out I'm going to make a How To thread including what I've found and what you've found and posted to make it easier for nooblets in the future, maybe even make a simple shell script to repartition the US 8gb model.
I fixed it
how?
Jistropy said:
how?
Click to expand...
Click to collapse
Mainly luck hehe. But actually from the mentioned threads ^^^^^ and this nifty trick, but use caution as I have no clue how well this works for other devices, if it all. And a large part of the problem was that my battery was dead because it wasn't charging correctly when plugged into my computer; and it kept dying in Odin.
Do you have a similar problem?? I can probably help..
So I should not be doing this on so little sleep, obviously. I have a Verizon HTC Droid DNA, Moonshine S-off, TWRP, and I had CarbonROM on it, but I was having issues so after some fumbling around and trying different things, I was at a loss. So I wiped all data and formatted. Well, before this, for some damn reason, I think I turned USB Debug off. Now I can't get into Fastboot USB. Am I totally screwed? My PC won't communicate with the phone.
HELP!
Actually its difficult to be "totally screwed" you can always hold the power + volume down until the phone boots into HBoot. Once your in HBoot again fastboot should work if it doesn't then that generally a driver issue. Once your back in HBoot you can select fastboot and that will give you the option to boot back into recovery. Once you get into recovery again I would select sideload and flash the ROM using "adb sideload <rom name>" making sure your in the adb directory and so is the ROM. Hope this helps.
Yeah, I can still get into fastboot (just not fastboot usb) and recovery, but my PC and phone aren't talking when they were before I started screwing around.
Sent from my Nexus 7 - Carbon Rom
Kevin5377 said:
Yeah, I can still get into fastboot (just not fastboot usb) and recovery, but my PC and phone aren't talking when they were before I started screwing around.
Sent from my Nexus 7 - Carbon Rom
Click to expand...
Click to collapse
PC driver issue, go into device manager and load new driver
I'll take a look
Sent from my Nexus 7 - Carbon Rom
Yeah, I'm not even getting the Windows sound like I connected anything. Usually it'll tell you no drivers or unsuccessful installation or something!
Holy crap... well you were right... it was a driver issue. I reinstalled the HTC drivers and I got FASTBOOT USB now... thank goodness!
I feel like my brain isn't working. How do I now get my .zip on my device using fastboot so I can then get into recovery and flash it?
Nevermind... booted to recovery, used adb to push my .zip to device
Glad you got it figured out.
It's always fun to watch people talk to themselves. :laugh:
I think I did the exact as you. Tried to get fancy with things too early in the morning and ended up formatting data. I was wondering how you pushed the zip for the ROM onto your device using adb? I can get adb to discover my device as long as its in recovery but I'm not sure of the commands it takes to push a file like that onto your sdcard in order to reflash it in recovery.
Any help greatly appreciated.
trickster2369 said:
Glad you got it figured out.
It's always fun to watch people talk to themselves. :laugh:
Click to expand...
Click to collapse
Even more fun when they answer themselves
hawkstwelve said:
I think I did the exact as you. Tried to get fancy with things too early in the morning and ended up formatting data. I was wondering how you pushed the zip for the ROM onto your device using adb? I can get adb to discover my device as long as its in recovery but I'm not sure of the commands it takes to push a file like that onto your sdcard in order to reflash it in recovery.
Any help greatly appreciated.
Click to expand...
Click to collapse
First, make sure your .zip is in the same folder as your adb. Then in your cmd window, (assuming you're in the correct directory) type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends.
And yes, I know first hand how amusing it is, and somewhat gratifying watching someone figure it out on their own. I could not, however, have done it without you guys. I assumed since my phone was communicating not 10 minutes earlier with my PC, it wasn't a driver issue. But in the end, that's exactly what it was.
Kevin5377 said:
First, make sure your .zip is in the same folder as your adb. Then in your cmd window, (assuming you're in the correct directory) type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends.
And yes, I know first hand how amusing it is, and somewhat gratifying watching someone figure it out on their own. I could not, however, have done it without you guys. I assumed since my phone was communicating not 10 minutes earlier with my PC, it wasn't a driver issue. But in the end, that's exactly what it was.
Click to expand...
Click to collapse
Enjoy
Kevin5377 said:
First, make sure your .zip is in the same folder as your adb. Then in your cmd window, (assuming you're in the correct directory) type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends.
And yes, I know first hand how amusing it is, and somewhat gratifying watching someone figure it out on their own. I could not, however, have done it without you guys. I assumed since my phone was communicating not 10 minutes earlier with my PC, it wasn't a driver issue. But in the end, that's exactly what it was.
Click to expand...
Click to collapse
Thanks that worked! Back to loving viper.
I Have a similar problem
Kevin5377 said:
First, make sure your .zip is in the same folder as your adb. Then in your cmd window, (assuming you're in the correct directory) type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends.
And yes, I know first hand how amusing it is, and somewhat gratifying watching someone figure it out on their own. I could not, however, have done it without you guys. I assumed since my phone was communicating not 10 minutes earlier with my PC, it wasn't a driver issue. But in the end, that's exactly what it was.
Click to expand...
Click to collapse
Hey i'm new to this and i also formated my phone when installing a new rom i can still get into twrp and when i plug in the phone to the computer fastboot usb shows up and it makes the sound on the computer however when i type adb devices in the cmd its blank could someone please walk me through the adb stuff sorry for being a noob
I also have a OTG cable but i tried to plug in a 16GB FAT32 flash drive but twrp didnt recognize it. it says unable to mount
Thanks a bunch
Adb commands are done with the phone booted into recovery. Fastboot commands are done with the phone booted to, well, Fastboot.
Sent from my ViperDNA
Kevin5377 said:
Adb commands are done with the phone booted into recovery. Fastboot commands are done with the phone booted to, well, Fastboot.
Sent from my ViperDNA
Click to expand...
Click to collapse
Thanks a bunch but i plugged in a bunch of flash drives until one was recognized and then was able to restore my old ROM... WHEW
Hello everyone,
I have been searching in vain for a while now to find a solution to my problem and I fear that I may have done something daft to my phone.
I am using a HTC One X+ that was unlocked, s-off and rooted for about a year, i had TWRP and stock android 4.1.1. For ages I have been getting an update alert saying a software update is ready and i think it was some Vodafone update (1.17.161.7). Whenever i accepted and tried to install this it would obviously reboot into TWRP and then the update would fail. This was fine until last night when I decided to install it through TWRP, it said it failed again and i rebooted to find that WiFi wouldnt turn on, my phone was no longer rooted or s-off and that I get no signal. I tried to re-root it but command prompt on the computer or HTC Sync wouldnt recognise my device however it was appearing as HTC One X+ in My Computer and i could access the internal storage.
I restarted into recovery and managed to flash a new root using twrp and the root file using the unlockr.com - how to root the htc one x
Then thinking it was a ROM issue i downloaded and installed InsertCoin Evolution ONE X+ 5.0-6 Sense 5 Android 4.2.2.
This all went through ok however when i reboot from this install it just sticks at the HTC Quietly Brilliant screen. I wiped everything using twrp beforehand.
When i restart into bootloader, it says unlocked, S-On and HBOOT -1.30.0000
Not sure what else to do as now i have no ROM, i read that you have to partition the SD card for InsertCoin to work but the option to partition SD card isnt there in my TWRP (ver. 2.3.3.0)
Any help to even reset my phone back to basic stock everything would be amazing, i have a Titanium Backup of most of my stuff saved btw.
Thanks to anyone who can help.
Did you flash the insert coin boot.img?
Sent from my HTC One X+ using Tapatalk
AndroHero said:
Did you flash the insert coin boot.img?
Sent from my HTC One X+ using Tapatalk
Click to expand...
Click to collapse
No I just copied the whole zip file to the SD card section and installed it from there - ive encountered a new problem now in the fact that my computer no longer can recognise the phone via USB - it still appears in device manager but cant access the sd card and the sd card got wiped by twrp so now i dont have any way of getting things onto the phone that i know of. It just says - failed to open usb master mode in the bootloader. How could i get the computer to recognise the phone again so i can transfer it back onto it and try installing insertcoin again? Really hoping i havent managed to make my phone useless as ive had to dig out the old Nokia 6230 from the drawer haha!
Thanks.
EDIT - Now seen the instruction to flash the boot.img - what a fool i am. Now i need to get it recognised by USB again so i can transfer the zip file to it and go again.
maxwell689 said:
No I just copied the whole zip file to the SD card section and installed it from there - ive encountered a new problem now in the fact that my computer no longer can recognise the phone via USB - it still appears in device manager but cant access the sd card and the sd card got wiped by twrp so now i dont have any way of getting things onto the phone that i know of. It just says - failed to open usb master mode in the bootloader. How could i get the computer to recognise the phone again so i can transfer it back onto it and try installing insertcoin again? Really hoping i havent managed to make my phone useless as ive had to dig out the old Nokia 6230 from the drawer haha!
Thanks.
Click to expand...
Click to collapse
Now seen the instruction to flash the boot.img - what a fool i am. All I need now is to get it recognised by USB again so i can transfer the zip file back and go again.
maxwell689 said:
Now seen the instruction to flash the boot.img - what a fool i am. All I need now is to get it recognised by USB again so i can transfer the zip file back and go again.
Click to expand...
Click to collapse
Without a rom installed you're not able to acces the internal memory of your phone directly. You have to use "adb sideload" command to transfer a rom onto your phone. Look in the General and/or Q&A forum of this device, there are enough guides or topics on how to solve this "problem".
maxwell689 said:
Now seen the instruction to flash the boot.img - what a fool i am. All I need now is to get it recognised by USB again so i can transfer the zip file back and go again.
Click to expand...
Click to collapse
Hi use this link..may be useful (http://forum.xda-developers.com/showthread.php?t=2066390) by the way reaper90 is right you need to sideload the rom..
In TWRP:
1-wipe everything
2-goto advance in twrp
3-select sideload
4-navigate to the folder where you have adb.exe, adbwinapi.dll, adbwinusbapi.dll and fastboot.exe. and make sure to keep the rom and its image; bootimg there.
5-then in command prompt write (adb sideload *name of the rom*.zip) make sure the name is a letter.
6- also make sure to keep the screen alive and not let it goto sleep while adb sideload is working.
7- rom will start setup once sideload is 100%.
Hope this helps. Goodluck.
Optimus said:
Hi use this link..may be useful (http://forum.xda-developers.com/showthread.php?t=2066390) by the way reaper90 is right you need to sideload the rom..
In TWRP:
1-wipe everything
2-goto advance in twrp
3-select sideload
4-navigate to the folder where you have adb.exe, adbwinapi.dll, adbwinusbapi.dll and fastboot.exe. and make sure to keep the rom and its image; bootimg there.
5-then in command prompt write (adb sideload *name of the rom*.zip) make sure the name is a letter.
6- also make sure to keep the screen alive and not let it goto sleep while adb sideload is working.
7- rom will start setup once sideload is 100%.
Hope this helps. Goodluck.
Click to expand...
Click to collapse
Hi, thanks very much for the responses - its much appreciated.
Nothing happens when i type that command, a load of text appears in cmd prompt showing all the adb commands and thats it, i have searched for this problem and found this on twrp website as a possible solution "You will need version 1.0.29 or higher. You can find your current version by typing "adb version" at the command line" My version says 1.0.26 I have tried to update this but cant seem to find a way to do it, would that be an issue?
I think once ive managed to sideload the zip i should be good to go its just getting to that point that seems to be stumping me at the moment.
maxwell689 said:
Hi, thanks very much for the responses - its much appreciated.
Nothing happens when i type that command, a load of text appears in cmd prompt showing all the adb commands and thats it, i have searched for this problem and found this on twrp website as a possible solution "You will need version 1.0.29 or higher. You can find your current version by typing "adb version" at the command line" My version says 1.0.26 I have tried to update this but cant seem to find a way to do it, would that be an issue?
I think once ive managed to sideload the zip i should be good to go its just getting to that point that seems to be stumping me at the moment.
Click to expand...
Click to collapse
Dont sweat it. They understood you wrong.
Guys what he wants to do is copy the file FROM the SDCARD TO the PC.
First you will need to know where the location of your rom then type in the following commands:
Code:
adb devices
If you device is not detected then try to run the CMD as an administrator and try again
then:
Code:
adb pull {location without the curly brackets}
For example if its on the SDCard then:
Code:
adb pull /sdcard/rom.zip
It will paste the file to the folder where the adb is found
Then just open the zip file and get out the boot.img and flash it using fastboot
Hope this helps you out.
Ghand0ur said:
Dont sweat it. They understood you wrong.
Guys what he wants to do is copy the file FROM the SDCARD TO the PC.
First you will need to know where the location of your rom then type in the following commands:
Code:
adb devices
If you device is not detected then try to run the CMD as an administrator and try again
then:
Code:
adb pull {location without the curly brackets}
For example if its on the SDCard then:
Code:
adb pull /sdcard/rom.zip
It will paste the file to the folder where the adb is found
Then just open the zip file and get out the boot.img and flash it using fastboot
Hope this helps you out.
Click to expand...
Click to collapse
Hey, thanks.
No they got me correctly, there is absolutely nothing on my phone at all and I need to get my new ROM zip file from the PC to the phone so that I can install it. I am currently downloading SDK manager to try and update my adb to 1.0.29 or higher and will see if that works.
maxwell689 said:
Hey, thanks.
No they got me correctly, there is absolutely nothing on my phone at all and I need to get my new ROM zip file from the PC to the phone so that I can install it. I am currently downloading SDK manager to try and update my adb to 1.0.29 or higher and will see if that works.
Click to expand...
Click to collapse
Ok, i downloaded the hasoon toolkit and select ADB Sideload a ROM and it says "error device not found" in the command prompt. I am in ADB Sideload mode in TWRP with it plugged in via USB so dont know what to try next.
maxwell689 said:
Ok, i downloaded the hasoon toolkit and select ADB Sideload a ROM and it says "error device not found" in the command prompt. I am in ADB Sideload mode in TWRP with it plugged in via USB so dont know what to try next.
Click to expand...
Click to collapse
Lol.. Well, as i said try to run the Toolkit/cmd as administrator and try different usb ports.. It took me 5 minutes on windows 8 for the adb to properly read the device , had to try different usb ports, unplug , replug, and so on..
maxwell689 said:
Ok, i downloaded the hasoon toolkit and select ADB Sideload a ROM and it says "error device not found" in the command prompt. I am in ADB Sideload mode in TWRP with it plugged in via USB so dont know what to try next.
Click to expand...
Click to collapse
Hi goto htcdev n download the latest sdk
Sent from my HTC One X+ using xda app-developers app
---------- Post added at 09:08 PM ---------- Previous post was at 09:07 PM ----------
I will try to send I over the files for command prompt tomorrow.
Sent from my HTC One X+ using xda app-developers app
Optimus said:
Hi goto htcdev n download the latest sdk
Sent from my HTC One X+ using xda app-developers app
---------- Post added at 09:08 PM ---------- Previous post was at 09:07 PM ----------
I will try to send I over the files for command prompt tomorrow.
Sent from my HTC One X+ using xda app-developers app
Click to expand...
Click to collapse
Right ive manged to download the latest sdk and then after much unplugging and plugging and right clicking things in device manager its recognised my phone enough to sideload and install the ROM. I have also managed to fastboot the boot.img file as well after 3 attempts but it finally worked so i have a phone back again!! Thanks everyone here!!! Now to upload my titanium backup of apps, sadly i think ive lost all my photos thou
But thanks again to all. Sorry if ive been a bit noob but its been a good learning curve for me as i never had these issues with my HTC desire
maxwell689 said:
Right ive manged to download the latest sdk and then after much unplugging and plugging and right clicking things in device manager its recognised my phone enough to sideload and install the ROM. I have also managed to fastboot the boot.img file as well after 3 attempts but it finally worked so i have a phone back again!! Thanks everyone here!!! Now to upload my titanium backup of apps, sadly i think ive lost all my photos thou
But thanks again to all. Sorry if ive been a bit noob but its been a good learning curve for me as i never had these issues with my HTC desire
Click to expand...
Click to collapse
Thats great news that all is well now..feel free to post.. and dont forget to press the Thanks button