Hey guys,
I'm new to the MT4G scene and I have yet to root or flash anything yet because I love the way this phone is stock. However that doesn't mean I'm not familiar with flashing ROMs and such (myTouch 3G was my first smartphone).
I purchased this device off Craigslist in used but perfectly good condition, but the phone wasn't problem free as I thought it was. I noticed there was a hardware defect with the SD card slot I didn't notice until syncing the device to my PC, and at that same time I also noticed there was Clockwork Recovery Mod and a downloaded ROM inside the sd card.
I'm unfamiliar with how this particular device is supposed to be with complete stock radio, hspl, etc. because I'm not even sure if its safe to ship it off to the RMA department. Can anybody tell me what I'm supposed to be looking at in Recovery mode under stock settings so I can ship it off for a replacement?
Sent from my HTC Glacier using Tapatalk
First, turn off fastboot in the settings (under applications IIRC). Power down. Hold vol-up and power back up. This should bring you to hboot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Except it will state S-OFF in the top right. If your hboot is 0.86.000 and S-OFF odds are good you are on stock. If either of these is different, you most certainly are not on stock
You can also install Terminal Emulator and try to su at the prompt. If the command works and you successfully see a #, you are rooted.
I thought s-off was "security off", me meaning the bootloader is unlocked?
Sent from my Nexus One using XDA App
danger-rat said:
I thought s-off was "security off", me meaning the bootloader is unlocked?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Yes. You will never have S-OFF on a "stock" phone in regards to the thread title "Purchased used MT4G, how do I know everything is stock?".
You can still run stock ROM with S-OFF, but then the phone is not "stock" as shipped from HTC. Direct from HTC you will have an unmodified ROM (duh, lol), S-ON, stock recovery (triangle with exclamation mark), and Hboot 0.86.0000. This is how you would want to see a phone prior to shipping it off for RMA services.
S-on is stock.
Sent from my HTC Glacier using XDA App
if it has clockwork, it can't have s=on. you need to turn s=off before any changes can stick.
option94 said:
if it has clockwork, it can't have s=on. you need to turn s=off before any changes can stick.
Click to expand...
Click to collapse
The OP only stated that CWR app was installed and a ROM had been downloaded. You can install the market app and download a ROM without having turned S-OFF. Need more specifics from the OP.
The OP said clockwork recovery, not ROM Manager. He may have meant ROM Manager, but that isn't what he said...
Sent from my Nexus One using XDA App
Related
Hi all,
Here's short history of the phone:
Friend of mine drop his on the concrete about June of last year and whole screen was cracked (not pretty). About month ago I found LCD Screen with Digitizer on ebay bought it and replaced it.
After turning it on everything was working except random reboots. Phone was not registered to any account so there was no internet only WI-FI.
So I started going into system updates and downloading HTC updates it did two of them and I think on the 3rd one it just starts to boot white HTC EVO 4G screen comes on and then it reboots.
Only pulling the battery will stop it.
This is all on stock HTC Sense ROM, rooting was never attempted!
I've searched thru the forums here but everything here relates to failed rooting process.
Can someone please make any suggestions?
Bellow is the pictures of boot loader.
Help is greatly appreciated!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
These directions are for un-rooting, but should fix your phone:
http://forum.androidcentral.com/htc...19278-how-unroot-return-stock-ruu-method.html
Fazulka said:
These directions are for un-rooting, but should fix your phone:
http://forum.androidcentral.com/htc...19278-how-unroot-return-stock-ruu-method.html
Click to expand...
Click to collapse
Thank you!
Followed the instruction, run RUU and it starts to check the phone after this I get error[170]: USB connection error.
I've tried over 10 times.
Step 4 says "Make sure USB debugging is enabled on your phone."
I can't even log into Sense?
The only other thing you can do is find a PC36IMG.zip and put it on your microSD card, then reboot into the bootloader. It should find it and reflash everything, the same as using the RUU.
ffolkes said:
The only other thing you can do is find a PC36IMG.zip and put it on your microSD card, then reboot into the bootloader. It should find it and reflash everything, the same as using the RUU.
Click to expand...
Click to collapse
I've tried using this method found here
I placed PC36IMG.zip in root of the SD card. But when I boot into recovery I can see for about 3 seconds on the right side status bar how it checks PC36IMG.zip file but then it goes back to recovery. It never ask me if I want to update like it says in the above tutorial "Do you want to start update?"
Any other suggestions?
JohnnyBeGood113 said:
I've tried using this method found here
I placed PC36IMG.zip in root of the SD card. But when I boot into recovery I can see for about 3 seconds on the right side status bar how it checks PC36IMG.zip file but then it goes back to recovery. It never ask me if I want to update like it says in the above tutorial "Do you want to start update?"
Any other suggestions?
Click to expand...
Click to collapse
I had to unroot mine and I found that u have to have the right pc36img file. If you dont know what ver rom was running then you may need to try them all. But I had the same problem it just wouldent install the file. Keep trying and if you need help finding them Ill help ya.
I found this but its not the same place I got mine from. http://www.filecrop.com/htc-evo-4g-roms.html
Thanks for the reply!
Somewhat of a progress. I tried countless times and it always gives me USB connection error: Then I downloaded HTC Sync and and I think I went to Hboot and I heard sound on windows it seemed like phone got recognized and I was able to finish the processes. It was flashed using RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed. Then when I went to again in recovery it was again red triangle over the phone.
After that I just let it try to boot and it finally booted into HTC sense!
Turned on WI-FI and wanted to check if there's any updates and it said no updates?
This is what recoveries I've tried so far:
Amon RA 2.1.1
Amon RA 2.2.1
Amon RA 2.3 (Added 02/09/2011)
Stock Recovery 3.26.651.6 (Added 01/18/2011)
Stock Recovery 3.29.651.5 (Added 01/18/2011)
Stock Recovery 3.30.651.3 (Added 01/18/2011)
Stock Recovery 3.70.651.1 (Added 01/18/2011)
One by one I tried each one renaming to PC36IMG.zip and none of them asked me if I want to do the update. It just checks it and goes back to bootloader.
Why do I get red triangle?
What should I do now?
Help is appreciated!
So I'm not new to flashing roms, bootloaders, recoveries, or rooting. Ive had a wing, a G1, a Behold II, a G2, and a mytouch 3g slide. All rooted, re-rom'ed, etc. Not to mention various friends and family phones I've worked with.
Anyway, I'm about to send my G2 in for warranty so I figured I need to at least unroot it if not S-on. Unfortunately I don't remember what exact method I used to reach Root and S-off, which is probably one of my problems, But it didnt have anything to do with Gfree. It was way before that and quite a while ago.
I've been over the G2 unroot thread here over and over again, as well as other forums and they all seem almost exact to what is posted here. I've tried this method over and over and I'm not getting anywhere. I have a few problems that I'm sure are what is keeping this from progressing. I cant seem to flash the PC10IMG - I get a no image or bad image error. I can't flash the stock_root rom via clockwork recovery due to some sort of scripting error. I have no Idea where to head from here, I can't seem to find any different methods to remove perm. root. Also that thread mentions using the hex editor to change the version number. When I open my misc.img it already shows the 1.19.531.1.
I'll include a few hopefully helpful images, Any help would be GREATLY appreciated. I should be getting my new one today, maybe tomorrow (I haven't been tracking it), and need to send my old G2 back in before too long.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
flash a stock 1.19 rom through bootloader or fastboot RUU.
If you have fake s-off, then it will be straight to stock.
otherwise just run gfree with -s on switch after flashing a stock rom.
-Nipqer
Do you have any idea, preferably a link, to find a stock 1.19 rom? I feel like ive been looking all day and nothings turned up.
http://www.shipped-roms.com/download.php?category=android&model=Vision&file=PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip
md5: 531c08dc402e15577b947bf4cd22aec2
-Nipqer
Thanks man! I really appreciate it. I don't know why but I just could not find it yesterday. I'm not usually this slow =x lol.
I went through the same thing last week....After receiving the replacement G2, and using ADB to use the recommended gfree method and did a CLEAN PERFECT root I went about removing root from the old phone....No matter what I did I could not get the old root removed, so I did the unthinkable.....I creatively changed the dd command and was able to brick the phone.....Hopefully that will prevent any notice of previous rooting....(I couldn't boot, bootloader, etc...)
Sprint NS4G
Rooted
SU 3.0.7
CWM 5.0.2.3
used ICS ROM p://android.clients.google.com/pa...o/ZD3PyN0t.zip
Installed the wrong ICS version. No Mobile Network available.
Issues:
Computer can NOT recognize devices. Check for MTP Protocal under Setting > Device > Storage > Menu >>> no option exist.
Is there another way to run fastboot and get CWM recovery to install?
Any solution how to flash the CDMA version of ICS?
Not only wrong version of ICS, wrong section for this question. But since we here... volume up + Power = bootloader menu.
Download the drivers and adb flash recovery.img
ns4g via xda app
Dude get this crap out of here
Sent from my Nexus S 4G using XDA App
Ive already done all that. After getting to recovery I receive triangle brick android. Power and up v
I've rooted my phone and done many updates priors. OCD changed protoval on how computer recognize your phone.
Power + up volume get you to next screen where I can flash however flashing any Of the other rOm gives me an error. I can't flash recovery
seconds2none said:
Power + up volume get you to next screen where I can flash however flashing any Of the other rOm gives me an error. I can't flash recovery
Click to expand...
Click to collapse
If you flashed before have you saved any ROM's on you phone? If so did you try to wipe and restore one of your old roms?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Wrong thread
Sent from my Nexus S 4G using XDA App
Lol double fail.
Sent from my Nexus S 4G using xda premium
travisd4est said:
Wrong thread
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
no need to be a jerk.
Sent from my Nexus S 4G using Tapatalk
I'm not being a jerk. just giving him a hard time. Lighten up brother
Sent from my Nexus S 4G using XDA App
have you tried connecting it to your pc via linux? since it doesn't need usb drivers to connect, you may be able to flash recovery via terminal then.
hp420 said:
have you tried connecting it to your pc via linux? since it doesn't need usb drivers to connect, you may be able to flash recovery via terminal then.
Click to expand...
Click to collapse
Thanks HP420. I'll give that a try. This is what I pulled up.
forum.xda-developers.com/showthread.php?t=1397393&page=1
Sux for me! After installing Ubuntu, applying all java updates, and running the unbricking app, my NS4G is still not recognized by a computer. I've also applied updates of the MTP drivers. Sigh, I'm doom til the actual release from sprint.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Motorola Defy XT: So what does it mean when this is the only screen your rooted Defy XT can make??? Once i turn it on this the first and only thing that appears on the screen but after a few min. my phone starts being a phone and everything, well at least making all the sounds it used to and receiving messages still, but the screen is kaput. Is my phone Bricked for good? or is there anything I can do? Please someone help!!! :crying:
Did this happen after rooting or anything else
If you have cwm then find your rom And flash it
If you don't have cwm and you have enabled USB debugging then flash it via adb
If you are able to get in recovery mode then your phone is not bricked. It's just a system crash
Did you flash any zip from pimp my rom then flash the rescue package
By the way just stay cool. It will only take not more than a week or two to know the cause and repair it
Sent from my A11 using xda app-developers app
arnabbiswasalsodeep said:
Did this happen after rooting or anything else
If you have cwm then find your rom And flash it
If you don't have cwm and you have enabled USB debugging then flash it via adb
If you are able to get in recovery mode then your phone is not bricked. It's just a system crash
Did you flash any zip from pimp my rom then flash the rescue package
By the way just stay cool. It will only take not more than a week or two to know the cause and repair it
Sent from my A11 using xda app-developers app
Click to expand...
Click to collapse
Hey thanks for the response!
I've actually only just rooted my phone. I haven't put any rom on it. It is still running the factory gb on it. Only rooted it so that I could run a screen shot app on it, and was probably eventually going to rom it once I became a little more knowledgeable about doing so. But everything was working fine with the phone after rooting it, for about 2 weeks even, but yesterday I just pulled out my pocket after coming out of the grocery store, clicked it to unlock it and there was that screen. Tried everything to get rid of it, took the battery out, plugged it in the wall, my computer. Nothing. Weird thing is though, after 5 min of being on, it will continue being the phone that it is, making all its regular sounds and receiving messages and notifications, just with that pixelated screen, which leads me to believe that it might be a hardware/bios problem, or if phones even have bios. This is my first smart phone so I'm just really starting to get to know it. Again, appreciate all help given! Just bummed this phone I've had for a month has already crashed on me.
arnabbiswasalsodeep said:
Did this happen after rooting or anything else
If you have cwm then find your rom And flash it
If you don't have cwm and you have enabled USB debugging then flash it via adb
If you are able to get in recovery mode then your phone is not bricked. It's just a system crash
Did you flash any zip from pimp my rom then flash the rescue package
By the way just stay cool. It will only take not more than a week or two to know the cause and repair it
Sent from my A11 using xda app-developers app
Click to expand...
Click to collapse
Also forgot to mention I tried a factory reset by memory but with no visual it's hard to see if I'm even doing anything.
Search for your stock from and flash it
You can also use the custom from like miui v5 for defy/defy+ http://forum.xda-developers.com/showthread.php?t=2232947
Do you have a cwm recovery? Or you have to use the fastboot method
Sent from my A11 using xda app-developers app
I read through the similar thread from yesterday, but this is a different issue...
I had unlocked, installed TWRP, and had been running a custom ROM (BadBoyz 1.2). This morning I re-locked so I could flash the updated firmware (v1.80) and now I am unable to re-unlock.
When I issue the command fastboot flash unlocktoken Unlock_code.bin, it works without errors, and the phone goes to the "Are you sure you want to unlock your bootloader?" screen.
However, at that screen, the volume buttons do nothing. I can't select yes OR no, it just sits there. Eventually it times out and just shows the battery charging on a black screen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I flashed the firmware, it removed TWRP, and with a locked bootloader, I can't re-flash it.
I was able to get a fully stock rom up and running, so I'm not in brickville anymore (had a few hours of panic earlier today), and I've been able to confirm that the OEM Unlock option is checked. I've even unchecked and re-checked to be sure. Everything works except the ability to confirm my choice and move on. I'm kind of afraid that it's a glitch in the new firmware, at this point...
Anyone got any ideas?
Thanks!!
deleted
So, it removed TWRP and replaced the stock recovery? And now you can't reinstall TWRP because bootloader is locked? Is that where you're at?
Sent from my 2PS64 using XDA-Developers mobile app
have you tried running RUU.exe? i took that route and was able to unlock my bootloader again, flash twrp and upgrade to bb 2.0 with no problems
I had the same problem and had to flash a stock rom back on the phone before the unlocker would work.
I figured it out! I can't explain WHY it worked, but it worked...
I had re-flashed several times using the official RUU, and the results never changed...
Then yesterday I went through a mental checklist of what was different when I unlocked the first time... and the only thing, was that I hadn't put my SD Card in the phone yet when I unlocked the first time. So I went through the motions again to verify that it still didn't work, and it didn't. Then I ejected the SD Card and tried it - and BOOM, I was able to unlock!
The only thing I can think of is that the SD Card did have the Firmware .zip on it, which the phone auto-detected and asked if I wanted to install... even though I said no. As soon as I tried it without the card, it worked like it always had, I'm back to unlocked, and back to the custom ROM I had been enjoying so much...
Thanks for the tips, everyone, and I hope this thread helps someone else who finds themselves in the same boat!
scottspa74 said:
So, it removed TWRP and replaced the stock recovery? And now you can't reinstall TWRP because bootloader is locked? Is that where you're at?
Sent from my 2PS64 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, that is EXACTLY where I was at. However, finally found the way out of the mess.. (see above post)