Database Users

Reflash Recovery Trouble

Hey Everyone,
Thanks to everyone that has been posting information and howtos for this incredible (no pun intended) phone. I finally got rooted yesterday after hours and hours of trying with a few cards that just did not want to work. (Go spend the $10 at walmart, PNY 2GB, if you still cant get root using other cards.)
From what I understand, you need a customer recovery flashed to the device to start playing with roms, creating nandroid backups, and other such fun.
I am trying to use the unrevoked 'painless' reflash on my linux laptop. Using root to run it. It goes through its process, but hangs on 'Waiting for reboot...'.
Soooo, seeing that message, I initially thought that it worked, and just had that as its last message, but I am not able to use rom manager to create a backup or reboot into any 'custom' recovery, just the default one.
I then tried to use Rom Manager to flash a custom recovery, hit the button, and it says that it has ClockworkMod Recovery 2.0.1.3. Still no luck on creating backups, or installing roms, or rebooting into the custom recovery. I just get the phone with a big red question mark.
Any advice/hints/help would be greatly appreciated.

you are not done on the custom recovery till it says done... did u ave usb debugging on?

Yeah, Charge Only, Debugging Mode, Stock Cable.
I did switch back to my better card, not the card I rooted with (Cheap walmart one)

Just tried it with the other card as well... It is still just sitting at waiting for reboot. Anyone else have this happen?

stephen.j.cotton said:
Just tried it with the other card as well... It is still just sitting at waiting for reboot. Anyone else have this happen?
Click to expand...
Click to collapse
Make sure your USB drivers are updated. The drivers the reflash uses can be different then the older ones you used to ADB to the device

I am using linux to reflash, I thought that there was no need to update on linux and that this was self contained.

i believe you need to change some udev things
ubuntu instructions are on here:
http://forum.xda-developers.com/showthread.php?t=537508
run (basically just creates the file)
Code:
gksudo gedit /etc/udev/rules.d/51-android.rules
put this in that file that file, then save:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
restart udev:
Code:
sudo /etc/init.d/udev restart

+2 to invisiblek.
Thank you so much for your help. That was the trick that allowed it to pass the waiting for reboot and onto the actual flashing. Perhaps this can be appended over onto the main thread for other people that run into this.

what its actually doing is giving you access access through fastboot as your user user instead of only root

A little stuck

Hopefully others are seeing this and it will help them as well.
I was running stock 2.2, decided to root, no ROMS. Saw that the latest update was coming out so I unrooted, not problem (really). But since unrooting I would always boot in clockwork which pissed me off. So I started playing, tried the update that's floating around (update.zip) and that worked but still boots me in Clockwork. So then I tried factory reset, still no go. last night I decided to restore a backup from the past which was immediately after I rooted the first time. Everything was back, and botting was normal. Now, I think it gave me back root which was how the phone was when backed up, but not 100% sure. The SU icon was present, and I think the Ti loaded without error just can't remember, things getting blurry.... This am I rechecked for the OTA update and it was there. Updated figuring as others are finding that it will kill root and be fine, just re-root again. Well things not fine. since OTA I'm booting back to Clockwork and Ti says it can't find root, this leads me to believe that I don't have root, even though the SU icon (ninja) is present. Tried RootMyX2 which I used in past, but it gets hung up at "Waiting for Device" right after loading the arm5.bin file thingy. I've cycle USB modes, debugging is on. Tried Z4root which I can't even install because it says that the "file can not parse".
Someone please help, I can't take this **** anymore and getting very frustrated.

I think your at about where i am..
http://forum.xda-developers.com/showthread.php?t=867694

clockwork needs root to remove the signal file it creates that tells it the boot completed successfully. You will need to remove clockwork to fix or re-root.

That's fine, but how is this accomplished? The issue seems to come up alot, but no one has ever posted something (that I've seen) that actually addresses the removal of clockwork. I agree though, this is what I need to do. Any thoughts now?

I've not tried this method, so use at your own risk!
to remove it with adb shell:
first do this:
Code:
ls /system/bin/logwrapper.bin
If the file logwrapper.bin isn't found then you've lost the original due to flash/updates and can't remove clockwork until you locate it. Don't continue.
If the file is found then do the following:
Code:
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 / system
rm /system/bin/logwrapper
rm /system/bin/hijack
cp /system/bin/logwrapper.bin /system/bin/logwrapper
exit
exit
(you should have a command prompt back)
adb reboot

Thanks Slueth
But I don't really do the whole code thing. I know I have to start an emulator and such, but was hoping that I would have to go that route.
I was able to restore again to previous version when I had root, so now I have root again. Still don't feel like things are right in the world with it, but I'm kind of getting tired of searching for answers that don't seem to exist.
Basically now I would think that I can update, probably lose root, then re-root, but for some odd reason I can't find an app to root/unroot with. No clue why and at this point I would take going back to stock but I believe that requires coding too? Second part of this is I'm on Mac at home, only have access to PC at work and think I've spent enough wasted time there playing with my phone.
If you could come up with some way to get Z4 to work that would be swell.
On a side note, now my .mp3 ringtones wont recognize...

[Q] HEEELPPP please

I have a Samsung Epic and i rooted it to put the wifi tethering. Everything had worked fine and i decided to try some rom's out and try to upgrade to 2.2 before my provider decided to senf my the download. Anyways i tried to do some stuff with odin in that regaurd and it would never work. I came to find out that it was not reconizing my device on the computer. I have had the phone hooked up before after rooted and it worked fine and i was able to see my sd card and do everything. For some reason no computer will reconize my phone. It installs only three drivers and reconizes all of them, but they are named different then before. It seems that something has happened to the internal program of the phone were it is not sending the correct driver look up to the computer. I dont get the ADB interface driver install to even pop up and try to install. I took my buddys epic and hooked it up to the same computer and it did the proper driver recognition and installed fine as well as the adb driver. I mounted his sd card and it worked fine. I plugged my phone in to same computer it did a totally different 3 driver download all sucessfull put they had different driver names and there was no ADB driver reconized or attempted to install. The proper drivers are already on the computer and every epic will connect just fine except mine. I have done a factory reset and data wipe as well as my sd card wipe and it still does not connect to my computer. The drivers that keep installing when my phone is hooked up is modem cdma technology driver and usb device. Who ever has an epic will know that when you first plugged your phone in you got the name of the drivers as they were trying to install well for some reason mine now say ( unreconized device ) on the three drivers and then downloads them from microsoft and all say sucessfull. Unfortunately sucessfull is not the correct word cause without that adb interface driver loading i cannot mount my SD card. I have tried this on 4 computers with different operating systems and none will see the phone they all load these three wierd never seen driver descriptions and none enable the sd card to be mounted. I dont know what to do i cant take the phone back to sprint to have the factory origianl program put back on it with the correct drivers cause the phone is still rooted. Factory reset did not un root it and i cant connect the computeer to my phone to unroot it. Any advise would be great. thanks

For odin to recognize ur phone you have to be in download mode. To get download mode you have to hold the 1 button the the keyboard and turn the phone on at the same time. Also connect your phone to you computer after odin is already running.
Ps. This should be in general
Sent from my SPH-D700 using XDA App

i did the download mode and odin to reconize the com of the phone but fialed right offf the bat trying to install the new pit file and tar for the 2.2 upgrade so i gave up on that but i cant get my phone to connect to a cmputer to even mount the sd card to save my life. I can wait to get the update from sprint to 2.2 before i can install roms but i cant do anything until my phone will conect to a computer

Recovery mode and factory reset and then restore your nand backup.

Please post questions in General section.

i went into recovery mode then did the factory reset im not sure what (nand backup means) can you be more specific. thanks

swp22 said:
i went into recovery mode then did the factory reset im not sure what (nand backup means) can you be more specific. thanks
Click to expand...
Click to collapse
That just means a Clockwork backup. You made one, right?

unfortuneatly i deleted my sd card where clock work was and also when i tried to do clockwork before doing all this it failed as well to make a back up. I have had horrible luck trying to do anything with this phone other then the simpple one click root i did when i got it. So yeah sounds like im screwed cause i have no clockwork backup to refer to. Is there a way to take the sd card out of the phone put whatever it is i need ot on the sd card and then place it back in phone and try running it from there..I have rom manager installed on the phone once i had set it back to factory defaults so i can install custom roms from that. Would putting a custom rom on the phone fix the driver reconigtion problems im having or is that stuff burried deeper into the phone?

Also is it possible to take my friend epic that i have here with me and get the needed files from hhis phone back onto mine. I would hate to think i have a huge paper weight now cause sprint is going to tell me to pound sand cause the phones been rooted. Would this also be possible, If i was to take my buddies sd card put the foryo 2.2 update.zip folder on his sd card or simply place his sd card that has his stock update.zip file on it and place it into my phone and do a update.zip in recovery mode would that possibly fix the problem im having? Something must have happeend to mine cause when i try to do the update.zip from my sd card wit the one that came with the phone i get this meesage while it goes through the verifying update package. (e.file signature invalid abort installation) i can see in that folder from my phone that there is a adb file inside the bin folder which im hoping will fix my problem if i can get the phone to compleate the update.zip install.

[Q] please help with my nexus....

I went to flash cyanogenmod 10.1.
backed up rom via clockwork.
wiped data, flashed new rom.
flashed gapps.
I think i flashed the wrong gapps
upon boot I get "setup wizard has stopped" as well as one regarding gapps.
this prevents me from using the rom. I can access the calender and clock that is all. not the settings or reboot menu.
I can access the built in storage via windows, shows up as a nexus 7.
Ok, not a big deal, I will boot into recovery via the bootloader.
That no longer works. Sits at a google screen forever
Ok, I will use fastboot via the bootloader....
That no longer works. As soon as a usb cable touches the nexus either power or pc it freezes the bootloader requires a reboot.
windows rejects the usb and states is malfunctioned and unrecognised (though it works fine in the rom)
fastboot doesn't see the device.
I've tried:
three usb cables.
windows safe mode.
different ports
uninstall/install drivers.
nexus tool kit (doesnt recognise device)
wiggling the cable as suggested
anybody got an idea how I can either get the bootloader not to freeze when using a usb cable or how to boot into some kind of recovery (which was there!!!!!)
please? :fingers-crossed:

Something seems a little off here.
Was it a gapps package for some other device? Hard to see why flashing something to /system would produce the result you got, as the (gapps) edify script would at most specify a mount of "system", not a /dev/block/ device name.
Does adb work (with the ROM booted)? If so, can you get a root shell or install .apks?
The fact that the ROM boots suggests that the bootloader is working correctly enough to load and execute the LNX (boot) image. That means that in principle you could flash (using the "dd" command) a recovery image to the boot partition from a root-privileged command line (either an adb session or a terminal emulator). Performing a regular (power button) restart would boot you into a recovery session.
Obviously, this hinges on you getting a command line somehow with your reduced-functionality ROM limping along as it is. It's not obvious to me how you will make that happen though.
I am not at all confident that this will fix the bootloader <--> USB issue without somehow reflashing the bootloader without using fastboot!. The only way this has been observed for the N7 has been with the OTA process and a stock recovery - the OTA puts an image (**note - important!** this OTA bootloader image is slightly different from the bootloader image in the factory/fastboot ROMs) into the USP partition and some magic occurs on the next boot.
Well, anyway there's some ideas. Would you mind identifying the "wrong" gapps that you used? For the life of me I can't see how it caused the symptoms you are observing...
good luck

Hi. Many thanks.
Ok.....
Gapps. I downloaded the appropriate package via the link on the Rom page. However, I flashed a jellybean package I'd downloaded for my one x. I may be naive in thinking that Gapps is Gapps no?
I deduced it was that having googled the setup wizard problem and seeing that others had had it.
Bootloader.
Again. Ive googled around and can see many have the freezing bootloader with usb issue. Some say its the cable. Some say its the pc. But it does it with the charger as well. Again this is an issue for some. not sure what to do! Works fine until the cable goes in.
Recovery.
Again I know its an issue booting recovery from bootloader. I've read you need the usb in to a pc to make it happen. Obviously that's a no go for me
Adb.
Never really used it. Used fastboot many times. I assumed you need to be able to access the developer options and activate debugging etc within the Rom to allow it to work? I can not do that. Its around 10% funtional. I can place a reminder on the calender but that's about it! No way to system settings.
Sorry if thats teaching you to suck eggs. You obviously know your stuff, just wanted to make it clear.
Ta.
Sent from my HTC One X+ using xda app-developers app

olly2097 said:
Recovery.
Again I know its an issue booting recovery from bootloader. I've read you need the usb in to a pc to make it happen. Obviously that's a no go for me
Click to expand...
Click to collapse
A normally functioning tablet does NOT require you to be plugged in to a PC in order to boot the recovery from the bootloader menu. Maybe you are saying something else here, but I trust you've tried starting the recovery without anything plugged in at all.
Unless you can get the recovery working, the only hope you have is somehow levering up what you have available to gain a privileged thread of execution. Obviously that's going to be pretty challenging.
good luck - you're going to need it.
PS: could you provide a URL to the *wrong* One X gapps download? I think the gapps bundle ships with system libraries - I want to peek at those libs to see if there are any hardcoded block device paths that might explain the queerness you observed. (I can't imagine why this would be the case, but...)

bftb0 said:
A normally functioning tablet does NOT require you to be plugged in to a PC in order to boot the recovery from the bootloader menu. Maybe you are saying something else here, but I trust you've tried starting the recovery without anything plugged in at all.
Unless you can get the recovery working, the only hope you have is somehow levering up what you have available to gain a privileged thread of execution. Obviously that's going to be pretty challenging.
good luck - you're going to need it.
PS: could you provide a URL to the *wrong* One X gapps download? I think the gapps bundle ships with system libraries - I want to peek at those libs to see if there are any hardcoded block device paths that might explain the queerness you observed. (I can't imagine why this would be the case, but...)
Click to expand...
Click to collapse
yeah, tried both ways.
The gapps I downloaded was a while ago. I've deleted it. was for 4.1.1
anyway. I....
Booted to bootloader, selected recovery, pressed power and rammed in the usb cable at the same time.
recovery
now running rom fine after flashing TW recovery via toolkit and mounting to pc.
I cant explain it. it took forever. but thank you

Soft bricked HTC 10 - having issues getting back up and running

A lot of these I'm sure are general but since the HTC 10 is what I have and I'm using firmware and ROMs from within this subforum I thought this would be the most appropriate place to post. I have rooted/unlocked all of my (non-Nexus) phones over the years and like to think I have a moderate amount of experience with the process, but this is driving me up the wall and my searches for similar problems are turning up nothing but unrelated issues. My HTC 10 is unlocked and S-Off. I was running the ROM from this thread (the 6.0.1 version) for quite some time but stopped using the phone due to unrelated issues (screen is too big, can't get over the polarized screen and not being able to use the phone with sunglasses on). I'm now trying to sell it and therefore trying to get current firmware and a stock ROM onto it so potential buyers are not freaked out about modifications to the phone. I'd like to leave it unlocked and S-Off though.
I am able to successfully flash the firmware (from this thread), and have been going back and forth between the full stock ones and the ones with TWRP built in. As of right now the phone has no bootable ROM and I have been unable to load one. I can successfully get into Download, Recovery, and Fastboot modes. I see that I have three main paths to potentially flashing a stock ROM:
- Repair/Upgrade via HTC Sync with the phone in download mode
- Load the ROM onto the phone's SD card and use TWRP to flash
- Use ADB to sideload the ROM directly from Windows
My problems with these three options are thus:
- HTC Sync does recognize the device when put in Download mode. It even successfully downloads the update it perceives the phone needs. But at 20%, it claims the phone has too low of battery (it doesn't, it's locked at 100% and has been plugged in the whole time) and quits. It does this regardless of whether I select Upgrade or Repair. Tried multiple times, with both stock recovery and TWRP. I found one other case of this, and the only response was the OP saying he just sent his phone back to HTC. I don't think this is an option for me because it has sat unused basically since I bought it over six months ago.
- The phone does not read the SD card. Other devices read it just fine, but I don't have any SD card reader that can directly talk to my computer to do the file transfer through. I have not found any guides that allow me to mount the SD card without having a bootable ROM. Maybe this is where I simply don't know enough about ADB/TWRP and someone can point out a simple solution? I'm hopeful.
- I can get the phone into Recovery and then into "Sideload" mode. But trying to run "adb devices" or "adb sideload 2PS6IMG.zip" returns some variation of the following (the 31 and 39 are always there, sometimes it had more detail and sometimes it has less):
>adb server version (31) doesn't match this client (39); killing...
>error: could not install *smartsocket* listener: cannot bind to 127.0.0.1:5037: Only one usage of each socket address (protocol/network address/port) is normally permitted. (10048)
>This application has requested the Runtime to terminate it in an unusual way.
>Please contact the application's support team for more information.
I can't find anyone having these errors in this combination, but from what I can gather it's somehow tied to not having an up-to-date version of ADB... but I keep going and downloading the absolute most recent one (either from one of the threads here or Android Studio) and it just doesn't work. If I use one of the HTC_fastboot packages instead to try running the commands I just get "cannot read 'sideload'". I assume there is some kind of package or library missing from those directories.
Really I will take advice on troubleshooting any of these three angles, or one I have not though of. I'm sure all of the problems are stemming from one very annoying source but I just don't know what else to try. Thanks for any help you can offer.

I managed to get some ROMs onto a different micro SD card and the phone seems to at least recognize them. With stock recovery predictably I got "not signed" errors so I flashed the recovery that includes TWRP 3.1.1 from here, but it is giving me "corrupt file" errors for every single RUU .zip I have tried. They are all Verizon RUUs from here. Does not feel like I have actually made progress.

Valdair0 said:
I managed to get some ROMs onto a different micro SD card and the phone seems to at least recognize them. With stock recovery predictably I got "not signed" errors so I flashed the recovery that includes TWRP 3.1.1 from here, but it is giving me "corrupt file" errors for every single RUU .zip I have tried. They are all Verizon RUUs from here. Does not feel like I have actually made progress.
Click to expand...
Click to collapse
RUUs are to be flashed from download mode, not from twrp. Put your ruu in the root of your sd card and boot into download mode.

Tarima said:
RUUs are to be flashed from download mode, not from twrp. Put your ruu in the root of your sd card and boot into download mode.
Click to expand...
Click to collapse
Make sure it's named 2PS6IMG.zip

Thanks guys, it seems to be working okay now. It was upgrading to 7.0 when I left the house this morning. I'm going to flash stock recovery one last time tonight and hopefully it will be set.