MyTouch 4g, perm-rooted, S-OFF. I pushed a custom kernel (for overclocking). The device is fine. T-mobile tried to push an update (which kept nagging me), so I eventually applied it. When I did it failed to reboot. Good job, T-mobile.
That would have been fine except that I also had to return the computer I did this all on to work. I've created a new system and ADB only appears to detect the device when it's in recovery mode. I'm running gentoo, so I had to hack the udev rules myself. The identifiers match lsusb, but recovery is the only time I don't get a blank console under "List of devices attached".
/etc/udev/rules.d/50-android.rules
SUBSYSTEMS=="usb, ATTRS{idVendor}=="0bb4", ATTRS{idProduct}=="0c94", OWNER=="poseidon1157" #Normal
SUBSYSTEMS=="usb, ATTRS{idVendor}=="0bb4", ATTRS{idProduct}=="0c96", OWNER=="poseidon1157" #Recovery
SUBSYSTEMS=="usb, ATTRS{idVendor}=="0bb4", ATTRS{idProduct}=="0fff", OWNER=="poseidon1157" #Fastboot
lsusb:
Bus 001 Device 018: ID 0bb4:0fff High Tech Computer Corp.
OR
Bus 001 Device 018: ID 0bb4:0c94 High Tech Computer Corp.
OR
Bus 001 Device 018: ID 0bb4:0c96 High Tech Computer Corp.
In recovery mode:
List of devices attached
HT0... recovery
else
List of devices attached
So wtf?
Ultimately I want to push cyanogenmod to the phone, but I can't do that very well if it's not detecting the phone.
Please help. I really need that thing. Both for work and for my personal life.
I forgot that you use a separate fastboot binary. Looking for that now. Did they remove that from the default sdk?
poseidon1157 said:
MyTouch 4g, perm-rooted, S-OFF. I pushed a custom kernel (for overclocking). The device is fine. T-mobile tried to push an update (which kept nagging me), so I eventually applied it. When I did it failed to reboot. Good job, T-mobile.
Click to expand...
Click to collapse
Um, you blame T-Mobile for hacking your phone and then f***ing it up by applying a stock update to a non-stock phone? What was the update, 2.2.1? What kernel did you have on it? Anything other than a custom kernel?
Try applying this in Recovery.
This is T-Mobile's fault how? You failed, not them. Thumbs down to you.
Part Four said:
This is T-Mobile's fault how? You failed, not them. Thumbs down to you.
Click to expand...
Click to collapse
+ Juan to this post.
if you can get into recovery just do a nandroid restore.
if you can still get into Bootloader store the PD15IMG and start over fresh.
Wow most ppl complain about tmo not sending out updates! This is a first!
Sent from my HTC Glacier
lisap006 said:
Wow most ppl complain about tmo not sending out updates! This is a first!
Sent from my HTC Glacier
Click to expand...
Click to collapse
Lmfao so so tru
CM7 wtf else....
lisap006 said:
Wow most ppl complain about tmo not sending out updates! This is a first!
Sent from my HTC Glacier
Click to expand...
Click to collapse
Good point! another reason to rename this thread "Damnit, my own hands..."
Figures. I post a technical problem and everyone chimes in on something I said while frustrated. Not the problem. Thank you very much setzer for the recommended fix.
Personally, I would greatly appreciate it if none of the rest of you replied to my posts. Ever. Again.
And for the record you're right, I shouldn't have applied the update. Repeated attempts to find the update file failed, the notification stayed there, and my clockworkmod backup apparently disappeared with my photos and media and so I was stuck with a system I couldn't recover.
So did it work? I am not sure why you applied it in first place as most do warn and why would people accept stock OTA on custom setup is beyond me. Hopefully it works by restoring the PD15IMG or you have to social TMo to get replacement.
Sent from my HTC Glacier
Hey guys, is there a way to turn off system updates so this doesn't happen to me when my girlfriend had my phone lol.
Sent from my HTC Glacier using XDA App
Essenar said:
Hey guys, is there a way to turn off system updates so this doesn't happen to me when my girlfriend had my phone lol.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
honestly wait till after the update has been pushed to mess with the phone.
just call T-Mobile, tell them you haven't seen the update and they can push the update to you.
the other option you have is do a nandroid back up of the OS in the rooted stated, then unroot and turn s=on Do the update, re-root then flash the nandroid back up. and you are good to go.
I called T-Mobile and they cannot prevent the system from pushing the update notification to your phone.
poseidon1157 said:
Figures. I post a technical problem and everyone chimes in on something I said while frustrated. Not the problem. Thank you very much setzer for the recommended fix.
Personally, I would greatly appreciate it if none of the rest of you replied to my posts. Ever. Again.
And for the record you're right, I shouldn't have applied the update. Repeated attempts to find the update file failed, the notification stayed there, and my clockworkmod backup apparently disappeared with my photos and media and so I was stuck with a system I couldn't recover.
Click to expand...
Click to collapse
hold on there slick, i did provide insight full information. It's a simple mistake to make, but it's not 100% T-Mobile fault. infact it's not that fault at a 1% level.
Flashed recovery
For other idiots besides myself who think that custom stock-based kernels could be compatible with the update: they are not.
I did get this fixed. Personally I'm more comfortable with fastboot than I am with adb (no command-line completion, and imho it's the appropriate tool). After flashing clockwork recovery:
fastboot erase recovery&&fastboot flash recovery ${fastboot_location};
You can subsequentially mount it as a usb device (through recovery > mount... > USB). Copying a zip is necessary because (to my knowledge) tools to package the directories directly into a .img for fastboot have yet to be written.
Running a relatively stable cyanogenmod 7 nightly #18 with IMT/BT/GPS/SCCP. 801.11 drivers aren't working just yet. I might check through the git to see if there are pertinent commits.
Agreed
Hopefully you got it to work....
Sent from my HTC Glacier using XDA App
poseidon1157 said:
Figures. I post a technical problem and everyone chimes in on something I said while frustrated. Not the problem. Thank you very much setzer for the recommended fix.
Click to expand...
Click to collapse
Yeah, I guess your right, everyone did focus on that part, but it was the first thing you said. And you have to admit that the way your wrote your post you blamed TMO for messing up your phone. To most, that just seems stupid as it wasn't TMO that did anything wrong. All they did was try to push an update.
I'm sorry you had an issue, but you should have started out saying YOU messed something up. It's like having someone else root your phone and they say, "I'll try but there is a chance it will brick". And you saying, "it's cool dude, just give it a shot". Then when it bricks you blame them even after the warning.
Sorry, just trying to point out why everyone here thinks your post is lame. Please don't take offense to everyone, just realize that you blamed someone else for your OWN mistakes and then expect everyone to 'read your mind' and KNOW it was because you were frustrated.
I've just done a cleanup of the thread and had to remove half of the posts. I suggest if you have nothing helpful to say, please don't post at all.
Related
Hey,
I was wondering, is there anyway to gain temproot until we have full root? Am I right in thinking that temproot allows programs requiring root access to work e.g. AdFree?
Thanks
Sent from my HTC Sensation Z710e using XDA Premium App
There's an app called gingerbreak which works on the S E Arc (it roots anything on Gingerbread) so I wonder if it will work on the Sensation?
I'm waiting to get mine at the moment...
Hopefully tuesday
Hi !
I've fund this, but can't try, the sensation is not yet available in France
http www zenilshroff.com/ how-to-root-htc-sensation-android-2-3-gingerbread-smartphone/
(sorry, I can't post URL, i'm new on this forum)
-------------
HTC P3600 WM6.1
HTC HD2 WM7+Android 2.2
Roccoswell said:
Hi !
I've fund this, but can't try, the sensation is not yet available in France
http www zenilshroff.com/ how-to-root-htc-sensation-android-2-3-gingerbread-smartphone/
(sorry, I can't post URL, i'm new on this forum)
-------------
HTC P3600 WM6.1
HTC HD2 WM7+Android 2.2
Click to expand...
Click to collapse
Is that saying you need to remove HTC Sync from the device, and then run Gingerbreak?
Sent from my HTC Sensation Z710e using XDA Premium App
credits to this guide: http://www.zenilshroff.com/how-to-root-htc-sensation-android-2-3-gingerbread-smartphone/
1. First download the Gingerbreak.apk file.
2. Save on your computers desktop.
3. Connect the phone to your computer. (do not connect using htc sync)
4. Mount SD card as flash drive as you generally do for USB cable file transfers.
5. Copy the downloaded Gingerbread apk file to SD card root.
6. You should have any File Manager (e.g., Astro File Manager) on your phone. If not, download from Market. These are generally free apps.
7. Disconnect your phone from computer and launch File Manager. You will find in the menu of the phone.
8. Follow the onscreen instructions on File Manager to install APK to your phone from SD card root. You may also use the default application installer software to do this.
9. After installation completes, open the APK.
10. Press ‘root’ button. Simple, isn’t it?
11. The APK exploit will run for some time. Usually it runs for around 10 minutes. Your phone will be rebooted. In case it takes more than ten minutes for auto reboot, please reboot it yourself. Not to panic, this happens a lot of times.
12. Your device is now rooted. Congrats!
13. Make sure that SuperUser app is installed and is running. This is very important for you to enjoy the benefits of rooting.
In order to test if your phone has been successfully rooted, just click a screenshot of your phone. That should show that your phone has been rooted.
Yeah, but does it REALLY work?
Sent from my HTC Sensation using XDA Premium App
Gingerbreak exploit is patched on the SGS II so doubt that will work. Also if phone needs to reboot, no way will root persist due to signed locked bootloader. Go ahead and try but we will need some L33t devs to break this phone.
Sent from my HTC Hero using XDA App
drspikes said:
Gingerbreak exploit is patched on the SGS II so doubt that will work. Also if phone needs to reboot, no way will root persist due to signed locked bootloader. Go ahead and try but we will need some L33t devs to break this phone.
Sent from my HTC Hero using XDA App
Click to expand...
Click to collapse
Yeah, I'm not really willing to believe it works either mate.
If the guide has some proof (i.e. a bootloader photo) then I will try it. If not, it's all just based on theory, but nothing practical.
Somebody has to be the guinea pig.
Darnell_Chat_TN said:
Somebody has to be the guinea pig.
Click to expand...
Click to collapse
Well, I have tried it, doesn't seem to do a thing so far.
It does say it fails a lot, but still, zero proof that is works, I'm very suspicious that it's all ********
It would be great if we could get this partial root. I personally don't mind not being able to flash custom ROM, but it is very important to me to be able to use some apps that require root permissions like adfree or titanium backup. From what I understand, this 'half-root' should not be very difficult to achieve cause it is not needed to mess with the bootloader for this purpose. The only requirement is to be able to uninstall htc sync for some time.
Here also a link detailing the differences between root levels and clarifying vocabulary. I am posting this cause it has been very useful for me to help understand, so it might also serves others..
http://androidforums.com/evo-3d-all-things-root/329819-no-need-panic-about-locked-bootloader.html
madindehead said:
Well, I have tried it, doesn't seem to do a thing so far.
It does say it fails a lot, but still, zero proof that is works, I'm very suspicious that it's all ********
Click to expand...
Click to collapse
Thank you for trying it. I think you should now do a full factory reset, to totally get that thing off your Sensation. It does not do what it's supposed to do and who knows what it might be doing behind the scenes. Yea, be very suspicious!
Darnell_Chat_TN said:
Thank you for trying it. I think you should now do a full factory reset, to totally get that thing off your Sensation. It does not do what it's supposed to do and who knows what it might be doing behind the scenes. Yea, be very suspicious!
Click to expand...
Click to collapse
Yeah, doing a full reset was in the back of my mind. Think I will go do that now
I'm not optimistic thought. They who owns the website emailed me (I posted a comment doubting it, and it was deleted, so I reposted, and he emailed me), to say the guy who posted it hadn't got back to him, so he was removing it from the site until he had confirmation that it did work. I am still VERY sceptical of it. He said, uninstall HTC Sync from the PC, as that causes problems with root? VERY random thing IMHO.
madindehead said:
Yeah, doing a full reset was in the back of my mind. Think I will go do that now
I'm not optimistic thought. They who owns the website emailed me (I posted a comment doubting it, and it was deleted, so I reposted, and he emailed me), to say the guy who posted it hadn't got back to him, so he was removing it from the site until he had confirmation that it did work. I am still VERY sceptical of it. He said, uninstall HTC Sync from the PC, as that causes problems with root? VERY random thing IMHO.
Click to expand...
Click to collapse
Well, a factory reset and trying to run GingerBreak right after hasn't done a thing. It says to reboot after it doesn't succeed after 10 mins, and that this happens a lot. But EVERY attempt I have been rebooting after 10 mins.
If the guy who "discovered" it can't even post proof, it sounds like a load of ****.
madindehead said:
Well, a factory reset and trying to run GingerBreak right after hasn't done a thing. It says to reboot after it doesn't succeed after 10 mins, and that this happens a lot. But EVERY attempt I have been rebooting after 10 mins.
If the guy who "discovered" it can't even post proof, it sounds like a load of ****.
Click to expand...
Click to collapse
Yea, if they discovered it they can prove their claim with a simple photo.
This speaks to not only the lack of credibility of the person who posted it, but also to the site that allowed it to be posted and remain till the complaints came in. A very untrustworthy source is how I view them because of this.
Gingerbreak won't help you, as there will be a nand lock, and the fact the kernel will be patched...
pulser_g2 said:
Gingerbreak won't help you, as there will be a nand lock, and the fact the kernel will be patched...
Click to expand...
Click to collapse
Yeah, I didn't think it would work to be honest. That really as wishful thinking. The person who posted that seems like a proper idiot
this will work once we get s-off to perminate root and then you can flash the recovery from fastboot or rom manager
xboarder56 said:
this will work once we get s-off to perminate root and then you can flash the recovery from fastboot or rom manager
Click to expand...
Click to collapse
Given your confidence, we'll let you test it first.
Darnell_Chat_TN said:
Given your confidence, we'll let you test it first.
Click to expand...
Click to collapse
Gingerbreak won't help you, as there will be a nand lock, and the fact the kernel will be patched...
Click to expand...
Click to collapse
Even the website states we need s-off so when that is achieved it will work and i will test it once we find a crack for the radio to get s-off/nand lock.
I was one of the unlucky testers before Steve0007 closed the thread. Did anyone figure out how to save our Sensation after the bad flash? My phone does not light up or respond to any button presses but when plugged into the computer it is recognized as an "unrecognized device."
I guess this is the risk we run being early testers. Hopefully someone figures it out otherwise I've got myself very expensive paper weight.
I assume no two button rescue? And this should be in q/a or general
Can you get to the bootloader?
Sent from my Sensation using xda premium
what did he brick people's phones with what was it supposed to be?
Wrong section. And that happened to me when i got an hd2 and i bricked it. Luckily it was 2 days after i bought it so tmobile gave me another because they thought something was wrong with it. But next time please post in the right section. Thanks.
nba1341 said:
what did he brick people's phones with what was it supposed to be?
Click to expand...
Click to collapse
Its probably only a soft brick
Sent from my Sensation using xda premium
Thank god I didn't flash it, I just finished downloading it when people started reporting issues.
Anyway, I'm sure he didn't mean for it to happen. If you have a spare battery, have you tried putting that one in?
These things are usually flash at your own risk.
I would never flash a ruu, unless it's official it could cause problems.
Sent from my Sensation using Tapatalk
Also, if it doesnt work and if you have tmo. Tell them bs and they will get you one. Just some advice and please dont flame me.
tried spare battery. same result. And i'm sure he didn't do it maliciously I've flashed many of his things before with no problem. Just hoping to get some help. Phone doesn't respond. Can't get to bootloader. Only sign of life is windows recognizing that i plugged something into the usb slot.
Yes as I said, this happened to me exactly when i had a tmo HD2 and flashed a european ruu and it was dead. I tried everything. You will have better luck to talk to your insurance company.
Have you got ADB installed on your pc? If not start downloading and installing it. I will find some links, in just a sec.
Edit:
New to ADB CLICK HER
More to set up path CLICK HERE
http://www.mediafire.com/?rrwi4f258lie1r7
Extract to system 32 or sysWOW64 (64bit)
Try 3 finger salute (VOL UP,VOL DOWN + POWER) with your phone plugged into pc and pc volume up see if it makes a sound like a device has connected.
Whats was this RUU anyway?
if you just need ADB you dont need all of the stuff above or to set up a path if its extracted to those folders
duychau said:
tried spare battery. same result. And i'm sure he didn't do it maliciously I've flashed many of his things before with no problem. Just hoping to get some help. Phone doesn't respond. Can't get to bootloader. Only sign of life is windows recognizing that i plugged something into the usb slot.
Click to expand...
Click to collapse
This is excatly what happened to me.Computer wont see the phone though,so no adb fix can be applied.Mnn i'm so pissed as i dont have insurance.
usually blagging HTC will do the trick for a repair,dont mention XDA, ROOT, ICS or basically anything except your phone said update was available and the battery died
Click to expand...
Click to collapse
roflcopter is 10chars
duychau said:
tried spare battery. same result. And i'm sure he didn't do it maliciously I've flashed many of his things before with no problem. Just hoping to get some help. Phone doesn't respond. Can't get to bootloader. Only sign of life is windows recognizing that i plugged something into the usb slot.
Click to expand...
Click to collapse
What does it recognize it as?
unrecognized usb device
Ok guys, it looks like the firmware that I posted to another thread from 3.06 bricked few devices. I have flashed it and it worked fine, so i tried again with the package i posted and indeed it is corrupted as it bricked also mine
My device does not respond, so I would think it is dead
I feel sorry for those who have bricked also theirs based on the package i posted.
I am closing my Rom thread and starting now my Rom developments will be for my own use. I will not publish anymore my work.
Again I feel sorry for those who have lost their devices.
Steve
ok so now his rom thread is closed. Why not keep it open and work together to help those with bricked devices attempt to restore them to a working state?
That way you keep your reputation rather than running away after bricking devices?
Arrrggghhhh,This could not have come at a worse time
nba1341 said:
ok so now his rom thread is closed. Why not keep it open and work together to help those with bricked devices attempt to restore them to a working state?
That way you keep your reputation rather than running away after bricking devices?
Click to expand...
Click to collapse
Because as far as I know no way to get them back
I was trying to update my mom's Infuse to ICS, then all of a sudden this (attached) happened. Heimdall had just given me the libusb.dll error (I needed to update the bootloader cause I kept getting rainbows in CWM), so I was unplugging the phone so I could get the right drivers.
I have a horrible feeling I did something very wrong. I can't imagine why what I was doing would have caused this though, since the cmd had gone back to a default state after giving the error.
Is there any way to fix this?? Thanks a ton in advance!
mvgc3 said:
I was trying to update my mom's Infuse to ICS, then all of a sudden this (attached) happened. Heimdall had just given me the libusb.dll error (I needed to update the bootloader cause I kept getting rainbows in CWM), so I was unplugging the phone so I could get the right drivers.
I have a horrible feeling I did something very wrong. I can't imagine why what I was doing would have caused this though, since the cmd had gone back to a default state after giving the error.
Is there any way to fix this?? Thanks a ton in advance!
Click to expand...
Click to collapse
can you get it into download mode...?
if so run the one click again and you might have to check the box for bootloaders, on the second run...meaning I would run it twice...
It does that immediately on power up. Doesn't even get to the Samsung screen. Odin will recognize the phone, but when I try to flash a return to stock package (which I used earlier perfectly fine), it says the md5 is invalid.
Like I said, I never even got to the point of installing the bootloader since I forgot about the drivers. Are you saying I should install the drivers and try to flash the bootloader again?
Thanks so much for the help! I've never had this much trouble with a phone before
EDIT: I'm a dumbass. since I couldn't see the screen, I forgot to press up again after entering download mode. Odin is now in the process of installing the aforementioned return to stock package. And I think it worked!
You have no idea how grateful I am of you for pointing that out! I feel kind of dumb for not trying it, but when the screen looked like that I could only assume there was no functionality!
THANKS AGAIN! Times a million!
Lol ok let us know when you get it up and running....kk
Sent from my SAMSUNG-SGH-I717 using xda premium
What EXACTLY gave you the idea to put your mother's phone on a ROM that half works and has many bugs? Just trying to understand... I could have done this to my friend's mom's atrix, but I didn't because the stock ROM will always have the least bugs for unpopular devices like ours. (ones that don't get official support for CM or AKOP or anything)
wayzata said:
What EXACTLY gave you the idea to put your mother's phone on a ROM that half works and has many bugs? Just trying to understand... I could have done this to my friend's mom's atrix, but I didn't because the stock ROM will always have the least bugs for unpopular devices like ours. (ones that don't get official support for CM or AKOP or anything)
Click to expand...
Click to collapse
whooo there...slow your roll...
the op has the options to put what he wants, and actually if you have been tracking the ICS/CM9/AOKP threads they have made leaps in the smashing of bugs....actually very stable and good to go now, seeing how just months ago we didn't even have any ver of ICS, and yes it takes homework to install..
and you kept stock on your friends Mommy phone well that was between you and him and Mommy...
so long story short....as far as unpopular, I see this device being sold and for a high demand on CL and Ebay...with all the support given here...that is my IMHO...as is yours
+10 Char
bigjoe2675 said:
whooo there...slow your roll...
the op has the options to put what he wants, and actually if you have not been tracking the ICS/CM9/AOKP threads they have made leaps in the smashing of bugs....actually very stable and good to go now, seeing how just months ago we didn't even have any ver of ICS, and yes it takes homework to install..
and you kept stock on your friends Mommy phone well that was between you and him and Mommy...
so long story short....as far as unpopular, I see this device being sold and for a high demand on CL and Ebay...with all the support given here...that is plenty IMHO...as is yours
Click to expand...
Click to collapse
This makes about as much sense in English as it does in Japanese.
wayzata said:
This makes about as much sense in English as it does in Japanese.
Click to expand...
Click to collapse
You are a smart guy... i am sure you understood me....
Arigatou gozaimasu btw...just leave it as that....
Hajimemashita Joe sama
Sent from my SGH-I997 using xda premium
mvgc3 said:
I was trying to update my mom's Infuse to ICS, then all of a sudden this (attached) happened. Heimdall had just given me the libusb.dll error (I needed to update the bootloader cause I kept getting rainbows in CWM), so I was unplugging the phone so I could get the right drivers.
I have a horrible feeling I did something very wrong. I can't imagine why what I was doing would have caused this though, since the cmd had gone back to a default state after giving the error.
Is there any way to fix this?? Thanks a ton in advance!
Click to expand...
Click to collapse
Same thing happened to mine when i flashed back to stock. Kept trying download mode and finally worked. Keep trying and also try recovery. Worked for me
Sent from my SAMSUNG-SGH-I717 using xda premium
wayzata said:
What EXACTLY gave you the idea to put your mother's phone on a ROM that half works and has many bugs? Just trying to understand... I could have done this to my friend's mom's atrix, but I didn't because the stock ROM will always have the least bugs for unpopular devices like ours. (ones that don't get official support for CM or AKOP or anything)
Click to expand...
Click to collapse
First of all, every once in a while, she asks me if there are any updates yet.
Second, there's only a short list of insignificant bugs mentioned in the ICS topics.
I flashed GB on it a while back, and I figured since CWM and everything was set up already I wouldn't have a problem; flash, reboot, flash again, done. Unfortunately, it wasn't flashing the second time for whatever reason, and I figured it had something to do with the now half-functional CWM.
Anyway, to those of you who weren't unreasonably judging me, and rather decided to help: Thank you, the phone is now back up and running!
Prometh1216 said:
Hajimemashita Joe sama
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
LOL, woooooooootttttttt
Same thing happened to me. What I did was send my phone back to Samsung tell them everything ( except about rooting) they will email you a label then ship it off and get back in about 1 week. They will put stock gingerbread on it. Hopes this helps.
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2
hello to all, i was given this phone by a friend cuz its stuck in CWM. im not new to android but i am to this phone( i have a G2x wich was easier by far to figure out). anyways after much searching in these forums i couldnt find anything to do with this problem so here it is.
I am stuck in CWM. i try to flash a rom( i have tried multiple times with different roms) and i get an error 7. does anyone one know what that means, and if so how do i fix it?
ive been trying to re root or revert to stock but adb must have been disabled and or debugging. any help would be awesome. for now ill keep searching and trying to get adb up and going...
i wonder if having lg drivers for my g2x on my comp would mess with adb....
any comments and or suggestions would be greatly appreciated
lmao your lucky your friend never heard of google, but I guess you haven't either haha. Anyway, you need to download a new rom and flash because the one on your sdcard is corrupt
Yup more than likely a bad download or possibly a corrupt partition of sdcard, reformat card, redownload rom, check md5sums
Nope having lg drivers won't effect this phone, but not having the right drivers for this phone is probably why adb doesn't work
Also the g2x is kinda fake rooting funky business, as you found this phone is much different. I would suggest booting into hboot and checking what bootloader you have and if the security flags are still on or not, can make a difference when flashing a rom.
Probably worth your while to read through the stickies and search the forum a bit too
Sent from my MyTouch 4G Slide using xda premium
Lol. Seriously dude. I'm not a noob at flashing Roms. I have tried to flash at least 6 different Roms all ending up with error 7. I'm brand new to this phone so treat me like I need a step by step, but don't be condescending plz.
Sent from my LG-P999 using xda app-developers app
demkantor said:
Yup more than likely a bad download or possibly a corrupt partition of sdcard, reformat card, redownload rom, check md5sums
Nope having lg drivers won't effect this phone, but not having the right drivers for this phone is probably why adb doesn't work
Also the g2x is kinda fake rooting funky business, as you found this phone is much different. I would suggest booting into hboot and checking what bootloader you have and if the security flags are still on or not, can make a difference when flashing a rom.
Probably worth your while to read through the stickies and search the forum a bit too
Im gonna have to read the stickies. im gonna have to read the whole forum....dont let the g2xers hear you say its fake flashing lol. first order of buisness is figuring out how to get into this hboot you speak of. everytime i trun the phone on it hits lg splash and then goes straight to cwm
Click to expand...
Click to collapse
In my signature you'll see a "Mirrors" link. Go there and at the bottom of Post #1 you'll see HTCdrivers.exe. Grab them & load 'em up. ADB should work for you then. Then issue "adb reboot recovery" from a cmd line and when there go to "mounts & storage" & activate. Copy the ROM you want to your SD card while retaining your boot.img in your ADB folder. Wipe Dalvik twice. format cache & then factory reset. Format system then under "mounts & storage". After ROM has flashed from .zip in CWM leave it there and issue "fastboot flash boot boot.img" fom ADB. Reboot & let it settle. Should work.
Don't turn your phone on.....go to HBoot by holding volume down & power at the same time & bypass boot sequence..
I should also mention the reason why this phone is messed up like it is. It was rooted running a custom Roman and then the previous owner did and total. Is that gonna matter much?
Sent from my LG-P999 using xda app-developers app
grantusmantus said:
I should also mention the reason why this phone is messed up like it is. It was rooted running a custom Roman and then the previous owner did and total. Is that gonna matter much?
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
I don't think I understand.
---------- Post added at 11:12 PM ---------- Previous post was at 11:07 PM ----------
Sounds like maybe he was flashing while unlocked with the kernel going in seperately. Your HBoot will tell you that if it says "S-On".
All that aside, XMC is right though. Somehow your ROM is corrupt.
Sorry my typing sucks. The previous owner did an OTA update. i try to get to hboot but it goes straight to cwm. downloaded the drivers from the link provided even...still no adb devices listed in the device manager or when i type in "adb devices" command. if i can get adb working i can get this all fixed, but ill be a raped ape if i knew what the hell happened to this phone.
Sent from my LG-P999 using xda app-developers app
grantusmantus said:
Sorry my typing sucks. The previous owner did an OTA
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
Thats where your issues are coming from then. You probably have the ....1313 bootloader with S-On. Reread all your responses here & it should get you there.
Well I wouldn't be the first to say that about the g2x, a friend of mine has one and I needed to root it for him, kinda laughed as I read through the forum on how everything is done there, not saying devs aren't talented just saying the phone is well... I don't know how to say it politely so I just won't
Boot into your bootloader and write down everything on that screen here so we can help, if you get adb running just type
adb reboot bootloader
If not power on while holding volume down and you'll get there
My guess is the phone is s-on and the bootloader was at one point unlocked, glad you still have a recovery though, I warned people about this type of stuff before... not to say that I warned you or your friend, just feels as if people believe me some times
Read last post on page 4 some info about your situation, hell skim the whole thread to understand a bit more about htc phones
http://forum.xda-developers.com/showthread.php?p=35743946
Sent from my MyTouch 4G Slide using xda premium
WeekendsR2Short said:
In my signature you'll see a "Mirrors" link. Go there and at the bottom of Post #1 you'll see HTCdrivers.exe. Grab them & load 'em up. ADB should work for you then. Then issue "adb reboot recovery" from a cmd line and when there go to "mounts & storage" & activate. Copy the ROM you want to your SD card while retaining your boot.img in your ADB folder. Wipe Dalvik twice. format cache & then factory reset. Format system then under "mounts & storage". After ROM has flashed from .zip in CWM leave it there and issue "fastboot flash boot boot.img" fom ADB. Reboot & let it settle. Should work.
Don't turn your phone on.....go to HBoot by holding volume down & power at the same time & bypass boot sequence..
Click to expand...
Click to collapse
got adb working...well, adb recognizes a device.....it give me no name just a string of numbers and letters
i followed your instructions to the T. got as far as flashing the rom...error 7 again(big suprise lol)after said error, flashing boot.img doesnt work terminal hangs at waiting for device.
In case your wondering what comes before the error 7....here is:
assert failed: getprop("ro.product.device)=="doubleshot"
E:Error in /sdcard/mikTouch.zip
(Status 7)
String of numbers is your phone, that's normal
Flashing boot.img is done through fastboot not adb, did you ever make it into your bootloader? It may help if you do and write down everything here.
Sent from my Nexus 7 using xda premium
Your gonna laugh at me. Idk what happened, but cwm is gone now. Device isn't recognized by the computer.
Sent from my LG-P999 using xda app-developers app
Pull your battery for 15 seconds then pop it back in. Then hold volume down + power & make sure your usb cord isn't plugged in or it will just start booting. That will take you to your bootloader. Write all that down the use volume down to navigate to the "recovey" option. Use power button to select it. From recovey's initial screen use trackpad to to get to the "install from .zip". Next screen select ".zip location" (or something like that). Trackpad down to the ROM.zip file & select. Install. After done...."fastboot flash boot boot.img" then reboot. Let it settle for 5 minutes.
grantusmantus said:
everytime i trun the phone on it hits lg splash and then goes straight to cwm
Click to expand...
Click to collapse
You get an LG splash??? The MyTouch 4G Slide is made by HTC, not LG. If you get an LG splash, either you have a different MyTouch phone, or something is seriously wrong.
Fuzi0719 said:
You get an LG splash??? The MyTouch 4G Slide is made by HTC, not LG. If you get an LG splash, either you have a different MyTouch phone, or something is seriously wrong.
Click to expand...
Click to collapse
Nice catch Fuzi! That passed right on over my head. Unless the guy before changed the splash screen this is a big UH-OH!!
Fuzi0719 said:
You get an LG splash??? The MyTouch 4G Slide is made by HTC, not LG. If you get an LG splash, either you have a different MyTouch phone, or something is seriously wrong.
Click to expand...
Click to collapse
Wow didn't even see that!
Yeah if the phone you have in your hands is made by lg then that's your issue, you have a my touch q or something, this forum is for the HTC made mytouch 4 g slide. If this is the case it makes a whole lot of sense your errors when flashing, not being able to get into bootloader, etc.
The old good news would be you probably didn't brake anything, just find the right forum, put it into download mode and restore with some kinda lg stock thing.
Sent from my Nexus 7 using xda premium
Lmao. Sorry guys,i wish this was my phone, you guys have a really great community and I was happy to be part of it for the night.
Sent from my LG-P999 using xda app-developers app
grantusmantus said:
Lmao. Sorry guys,i wish this was my phone, you guys have a really great community and I was happy to be part of it for the night.
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
come back anytime
Hi Im a complete Noob for doinf this :silly:
Coming from Htc One there was a method posted on the Htc one forums to get the bootloader locked.
http://forum.xda-developers.com/showthread.php?t=2475914
And stupid me without thinking I used the command echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
to reset the unlocked to lock stats.
Well now the phone doesnt even turn on no booloader no recovery nothing, pc detects it as an unkown device but I dont know what to do with it.
is there anyway possible to bring this brick back to life or do i have send it back to google?
Any suggestions or Advice is welcome.
Thanks
If it doesn't turn on I think you're hosed. You messed up one the partitions running the commands you did Please read the pinned (stickies) threads on the general forum before you do anything on your new device.
You wiped an important partition of the phone, and now it won't boot. Looks like you are out of luck. You can probably call Google and tell them your phone won't turn on, but technically that would be lying because you broke it without reading.
If you do get a replacement, and want to unlock the bootloader just get fastboot and type 'fastboot oem unlock'. That's it. This is a Nexus.
You kinda asked for it by attempting to follow a guide that is not for your device. HTC One =/= Nexus 5.
Like the above said, you wiped a partition essential to the function of your device. No way to fix it. Gonna have to send it back to Google, hopefully when you do they won't charge you and will just send you another. They might be used to having a million returns because when a device launchers there is a massive amount of nitpicking customers trying to get replacements and/or their are legit issues with the devices and they won't bother to check whats wrong with your phone. Most likely they will though, and who knows what you'll be charged. Good luck!
xXxG0dzRAgexXx said:
You kinda asked for it by attempting to follow a guide that is not for your device. HTC One =/= Nexus 5.
Like the above said, you wiped a partition essential to the function of your device. No way to fix it. Gonna have to send it back to Google, hopefully when you do they won't charge you and will just send you another. They might be used to having a million returns because when a device launchers there is a massive amount of nitpicking customers trying to get replacements and/or their are legit issues with the devices and they won't bother to check whats wrong with your phone. Most likely they will though, and who knows what you'll be charged. Good luck!
Click to expand...
Click to collapse
I hope I do get a replacement , Im in the Uk so i cant get in contact with Google support till Monday now. I was stupid for doing that and I have learned a valuable lesson.
That's what happens when you do not read. Good luck.
xXxG0dzRAgexXx said:
You kinda asked for it by attempting to follow a guide that is not for your device. HTC One =/= Nexus 5.
Like the above said, you wiped a partition essential to the function of your device. No way to fix it. Gonna have to send it back to Google, hopefully when you do they won't charge you and will just send you another. They might be used to having a million returns because when a device launchers there is a massive amount of nitpicking customers trying to get replacements and/or their are legit issues with the devices and they won't bother to check whats wrong with your phone. Most likely they will though, and who knows what you'll be charged. Good luck!
Click to expand...
Click to collapse
this just scares me about android. I am getting a nexus 5 soon, and love tweaking with my phones, so im pretty sure theres nothing to worry about, but still.... not trying to troll or anything, but on iPhone, its ridiculously hard to "hard brick". I've seen posts online, but most of the time its just users who end up thinking they've done a fix with no result, when in reality, ive had to fix plenty of iphones in the past, and some have come in horribly screwed up. always been able to fix them and restore though, even if it meant wiping a users data. With android, while I understand there are options to restore and such, it still seems rather easy to totally brick if you miss a step or something were to happen.
hoping I will never have this issue.... :-\
unvaluablespace said:
this just scares me about android. I am getting a nexus 5 soon, and love tweaking with my phones, so im pretty sure theres nothing to worry about, but still.... not trying to troll or anything, but on iPhone, its ridiculously hard to "hard brick". I've seen posts online, but most of the time its just users who end up thinking they've done a fix with no result, when in reality, ive had to fix plenty of iphones in the past, and some have come in horribly screwed up. always been able to fix them and restore though, even if it meant wiping a users data. With android, while I understand there are options to restore and such, it still seems rather easy to totally brick if you miss a step or something were to happen.
hoping I will never have this issue.... :-\
Click to expand...
Click to collapse
iPhone's are pretty much impossible to hard brick. Was in the jailbreak scene for 2 and a half years, and there is no way to hard brick one. Very early on it was possible, but not anymore. Android devices are pretty hard to brick usually. Just make sure you follow a guide for your device and all should be well. Only risky thing really is flashing the wrong firmware or radio on a device. Flashing roms, mods, or wiping the entire device is always fixable (not important partitions though, but that's only possible via command terminal like in this case). I was at first scared with my HTC One since it was my first android device, but realized as long as you know what your doing all should go well.
unvaluablespace said:
this just scares me about android. I am getting a nexus 5 soon, and love tweaking with my phones, so im pretty sure theres nothing to worry about, but still.... not trying to troll or anything, but on iPhone, its ridiculously hard to "hard brick". I've seen posts online, but most of the time its just users who end up thinking they've done a fix with no result, when in reality, ive had to fix plenty of iphones in the past, and some have come in horribly screwed up. always been able to fix them and restore though, even if it meant wiping a users data. With android, while I understand there are options to restore and such, it still seems rather easy to totally brick if you miss a step or something were to happen.
hoping I will never have this issue.... :-\
Click to expand...
Click to collapse
Don't be too scared. Honestly bricking a nexus device is quite hard as long you are somewhat literate. With most situations (if you have access to the bootloader) you have the option of flashing the factory images which will get your phone up and running 95% of the time. Basically if you can access the bootloader, there is nothing to panic or worry about.
The only reason this guy bricked his phone is because he thought it was a good idea to root his nexus 5 using a guide that teaches you how to unlock the bootloader on an HTC One.
Just make sure you read a bit, understand what you are doing, and don't blindly follow random instructions that you find on the interwebz. If you follow that advice i doubt you will have any problems.
Sent using xda-developers app
uronfire said:
Hi Im a complete Noob for doinf this :silly:
Coming from Htc One there was a method posted on the Htc one forums to get the bootloader locked.
http://forum.xda-developers.com/showthread.php?t=2475914
And stupid me without thinking I used the command echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
to reset the unlocked to lock stats.
Well now the phone doesnt even turn on no booloader no recovery nothing, pc detects it as an unkown device but I dont know what to do with it.
is there anyway possible to bring this brick back to life or do i have send it back to google?
Any suggestions or Advice is welcome.
Thanks
Click to expand...
Click to collapse
Still having issues? I've got a couple of ideas you could try. I managed to fix my nexus after I completely screwed up the bootloader, willing to share how I fixed it
daniel.kusy said:
Still having issues? I've got a couple of ideas you could try. I managed to fix my nexus after I completely screwed up the bootloader, willing to share how I fixed it
Click to expand...
Click to collapse
How did you manage to fix yours? Mine's still bricked but can only get access to the bootloader. Have tried every option of flashing factory but still no luck.
How do you brick a Nexus?
I wish I could feel pity but man....
Tell them it won't turn on. Send it back I'm sure they won't know. Hope they don't at least. Better than keeping a paperweight.
sent from my Nexus 5
jphilippon said:
How do you brick a Nexus?
I wish I could feel pity but man....
Tell them it won't turn on. Send it back I'm sure they won't know. Hope they don't at least. Better than keeping a paperweight.
sent from my Nexus 5
Click to expand...
Click to collapse
I used ChainFires auto root and it quite simply did not work and bricked my phone. Nothing else to it… it just bricked my N5. No interruptions, all correct drivers installed. Now I'm stuck with a phone displaying unlocked boot loader (which I can lock temporarily using fast boot command.) but when the device restarts into fast boot it's back saying unlocked. Nightmare really.
Meakii said:
I used ChainFires auto root and it quite simply did not work and bricked my phone. Nothing else to it… it just bricked my N5. No interruptions, all correct drivers installed. Now I'm stuck with a phone displaying unlocked boot loader (which I can lock temporarily using fast boot command.) but when the device restarts into fast boot it's back saying unlocked. Nightmare really.
Click to expand...
Click to collapse
there is a person in the franco's thread who even corrupted the bootloader he managed to recover using some lg flsh tool something like kdz
it was some kind of methord used to unbrick nexus 4
Meakii said:
How did you manage to fix yours? Mine's still bricked but can only get access to the bootloader. Have tried every option of flashing factory but still no luck.
Click to expand...
Click to collapse
have you tried the flash-all.bat (factory image using command prompt from the sdk/platform-tools folder )?
Sent from my Nexus 5 using Tapatalk
floxrin said:
have you tried the flash-all.bat (factory image using command prompt from the sdk/platform-tools folder )?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yea mate. No luck.
Meakii said:
Yea mate. No luck.
Click to expand...
Click to collapse
If you can get into bootloader does fastboot work? If you can get into the bootloader virtually anything can be fixed. What happens when you click the flash all.bat file?
Try LG download mode
Sent from my Nexus 5 using Tapatalk
daniel.kusy said:
If you can get into bootloader does fastboot work? If you can get into the bootloader virtually anything can be fixed. What happens when you click the flash all.bat file?
Click to expand...
Click to collapse
See the attached. I can't do anything. Every attempt to write anything to the internal SD fails. I wish it could be fixed but have tried everything. Worst part is even after fastboot oem lock cmd when it restarts it's unlocked again. Meaning when I return it warranty will probably be void.
This guy has the same problem. http://forum.xda-developers.com/showthread.php?p=315800
Sent from my SAMSUNG-SGH-I957 using xda app-developers app