Has anyone tried porting this over yet? For those of us with bricked devices, the "format all partitions" option would be our only savior.
I'm scared of porting it since there's no source code available. Only option for port is by extracting a binary from another device and reusing it on ours. But has high chances of bricking a device also.
I have a suggestion why not ask any official developers of 4ext to develop for our device and giving a bounty?
I'm willing to give a $50-$100 or even higher bounty for this recovery... The question is... Knowing this device is already getting old other than me is there anyone else willing to donate for a 4ext recovery on our device? As I don't think $100 is enough to give motivation to the developer.
To be perfectly honest with you Riyal, I would have been MORE than willing while I was holding my bricked DS in my hands. But since I've already replaced it and, like you said, it's getting some age on it, I'm just as happy right now with a CWM that works fine although a bit slowly.
On the other hand there MAY be enough people that haven't been able to replace theirs that crapped out that might be. No matter this baby's age, it's STILL a pretty hot phone and one of the very few good ones with a qwerty keyboard. The way things are looking.....maybe one of the LAST too. (and that's a shame IMO)
Well when it comes to qwerty I think the captivate glide is another good candidate it's just that I hate it's form factor.
I talked to Madmaxx a while back about this, and he told me that he had his hands full because he had promised to release it on other devices such as the S3 and OneX etc before he could start working on a port/recovery for any other devices.
From our conversation, my understanding was that he probably would have let me assist with this device's 4EXT recovery if I had the know how to actually build a recovery from source for a particular device and have all the features and partition table entries working as they should. I have never done so and I'm actually not confident I can at the moment so I decided I shoudl probably brush up on this knowledge first before I attempt. Lest I end up bricking more devices in the process.
Anyway, long and short of it all, is all I'm saying is, if you are a dev and have the knowlegde and are willing to get your hands dirty, I think you should contact him via PM and talk to him about it. He is a very good person and I think he would let someone work on a recovery for our device.
Sent from my HTC Vision using xda app-developers app
I already made a CWM recovery once but it's from a sony device which like I said has no real recovery partition. What we did in the recovery was hack up the ramdisk and insert a recovery binary from the chargemon or init.rc. I could work on another recovery sure but problem is I don't know what kernel to use for the recovery and where to get the offset value inorder to merge bother the recovery kernel and the recovery itself. If he can assist me or any of the devs here with knowledge in making a recovery(like xmc) the very basics I can make this for mt4gs.
cybot_x1024 said:
I talked to Madmaxx a while back about this, and he told me that he had his hands full because he had promised to release it on other devices such as the S3 and OneX etc before he could start working on a port/recovery for any other devices.
From our conversation, my understanding was that he probably would have let me assist with this device's 4EXT recovery if I had the know how to actually build a recovery from source for a particular device and have all the features and partition table entries working as they should. I have never done so and I'm actually not confident I can at the moment so I decided I shoudl probably brush up on this knowledge first before I attempt. Lest I end up bricking more devices in the process.
Anyway, long and short of it all, is all I'm saying is, if you are a dev and have the knowlegde and are willing to get your hands dirty, I think you should contact him via PM and talk to him about it. He is a very good person and I think he would let someone work on a recovery for our device.
Sent from my HTC Vision using xda app-developers app
Click to expand...
Click to collapse
Hi guys! As said TWRP recovery coming soon!
{
"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"
}
Still has bugs like uncalibrated battery so I won't release it yet.
Riyal said:
Hi guys! As said TWRP recovery coming soon!
Still has bugs like uncalibrated battery so I won't release it yet.
Click to expand...
Click to collapse
That's going to be AMAZING Riyal!! Great job. You GO Buddy!
team win is a great recovery, perfect for my n7!
not a fan of clockwork so i would take almost any recovery that is stable over koushs. but i will say that 4ext is by far the best recovery ive ever used on any android and would still love to see it come here... but awesome for twrp, really excited!
4EXT is not opensource so there's no other developer who can compile it other than madmaxx. Anyways as said before he's gonna make one soon for our devices. Let's just hope he doesn't forget
Riyal said:
Hi guys! As said TWRP recovery coming soon!
Still has bugs like uncalibrated battery so I won't release it yet.
Click to expand...
Click to collapse
Good stuff man! This is very good news!
Riyal said:
Hi guys! As said TWRP recovery coming soon!
Still has bugs like uncalibrated battery so I won't release it yet.
Click to expand...
Click to collapse
Nice, lol you didn't even give me a chance!
xmc wildchild22 said:
Nice, lol you didn't even give me a chance!
Click to expand...
Click to collapse
try one xmc my build still has alot of bugs lol! One big bug is when I charge the phone while off it reboots to recovery instantly maybe you can make a better one
Or you could take over the project I've got something on my mind
Riyal said:
try one xmc my build still has alot of bugs lol! One big bug is when I charge the phone while off it reboots to recovery instantly maybe you can make a better one
Or you could take over the project I've got something on my mind
Click to expand...
Click to collapse
Is there an issue on twrp and this device where it wont flash Sense ROMS right and causes issues?
Sent from my myTouch_4G_Slide using Tapatalk 2
Hello guys! I've got some sneakpeak here for all of you!
I got a little naughty today and decided to venture out with some reverse engineering stuffs and here's the result!
Sadly this will be a personal use & I can't release it to the public just like that. I need a go signal from madmaxx for this one because obviously he did not gave me permission to make a port of his works for our device officially or not.
So anybody want to ask him for this? If he says yes then I'll release it at once.
Take note this is done through reverse engineering the recovery binary! 4ext won't work out of the box without proper modifications. So don't go flash any 4ext from other devices to doubleshot or else you might end up bricking your device. Also don't ask how to do it cracking software is not something you learn in a day
A PM has been sent. Keep your fingers crossed guys.
all I can say is wow, a couple of hours an you produce?
hopefull we get the go or at least a sped up offical release! thanks, you got talent!
Sent from my HTC Vision using xda premium
Riyal said:
... when I charge the phone while off it reboots to recovery instantly ...
Click to expand...
Click to collapse
...doubleshot has no hardware charging circuit - which threw makers of custom clockwork for a loop...
4.0.0.8:
Blue6IX said:
To Computer:
-Java SDK 7.
-Android SDK 12.
-HTC Sync.
-HTC USB Drivers. (fastboot drivers)
-(exit htc sync)
To doubleshot:
-Backed up phone data
-Copied all system numbers
-Format MicroSD Card.
-Factory system reset on phone.
-Verified all system numbers.
-Attach to local wireless network.
-Attach Gmail Account & set up market.
-Delete all desktop shortcuts and widgets, remove bottom 3 app shortcuts from dock bar.
-/settings/power/ uncheck fastboot
-/settings/applications/development/ check usb debugging
-/settings/applications/ check unknown sources
-/settings/display/screen timeout (set 10 minutes)
-Power down.
-Power on, plug into computer after fully booted.
-Run revolutionary-0.4pre3.
-Install Clockworkmod through revolutionary (4.0.0.8)
-CWM backup.
-Boot phone to OS. (Deny HTC crash report)
-Plug into computer, copy backup from device.
-Safe remove from computer, reboot to CWM.
-CWM Backup (2) of first run for OS after patching.
-Install Superuser (su-2.3.6.3-efgh-signed.zip)
-Reboot to OS. (Deny HTC crash report)
-Check everything is working, then reboot to CWM.
-CWM Backup (3) Superuser installed.
-Boot to OS, download and install busybox & root checker from market. Verified SU & busybox, reboot to CWM.
-CWM backup (4): S-OFF, CWM 4.0.0.8, SU 2.3.6.3, Busybox 1.18.4 (root checker 3.4)
-Reboot to OS. (Deny HTC crash report)
-/settings/applications/development/ un-check usb debugging.
-/settings/applications/development/ check stay awake.
-Tested charging through USB to PC: Verified working.
-Delete SU.zip from Sdcard.
-Delete all CWM backups except most recent from sdcard. (backup files saved to cd & seperate flash media.)
-Pair Bluetooth headset with device, headset to be left on for the rest of testing to test auto-pairing.
-power down, then back up device, unplugged, no fastboot.
-Start reset testing:
(reset tests include connecting to cell, wireless, and pairing a bluetooth device after powering on. BT device auto-pairs on boot.)
-Test power off/on while not plugged in, no fastboot: Verified working.
-Test power off/on while not plugged in, fastboot: Verified working.
-Test restart while not plugged in, no fastboot: Verified working.
-Test restart while not plugged in, fastboot: Verified working.
-Test power off/on while plugged to pc, no fastboot: power off fine, charge light goes out. Power on fail, charge light comes orange and device won't turn on. Un-plugging cable leaves orange charge light on, device still won't power on. Battery pull and charge light goes away, device boots fine.
-Test power off/on while plugged to pc, fastboot: power off fine. Charge light goes out, then comes back on (1, maybe 2 seconds delay). Device boots fine.
-Test power off/on while plugged to pc, fastboot: power off fine. Charge light goes out, then comes back on like above. Un-plug cable, charge light goes out. Device boots fine.
-Test restart while plugged to pc, no fastboot: powers down fine, all lights go out, no charge light until second splash screen blinks (goes black then comes back in an instant). Charge light then comes on, device boots to OS about 2-3 seconds later.
-Test restart while plugged to pc, fastboot: same as restart with no fastboot. Fastboot not working when selecting restart.
-Re-test power off/on while not plugged in, fastboot: verified working. Fastboot only broken on restart while plugged into pc so far.
-Test power off/on while plugged to outlet, no fastboot: power off fine. Charge light stays lit orange. Device won't turn on. Cable un-plugged, orane charge light still lit. Battery pull and charge light goes away, device boots fine.
-Test power off/on while plugged to outlet, fastboot: Power down fine. Orange charge light blinks off briefly, less then 1 second. Device boots fine.
-Test restart while plugged to outlet, no fastboot: power off fine. Charge light goes off. Device powers back up fine, charge light returns when second splash screen flickers.
-Test restart while plugged to outlet, fastboot: same as restart with no fastboot. Fastboot broken on restart while plugged into outlet.
-Test power off/on while plugged to car adapter, no fastboot: power off fine. Charge light stays lit orange. Device won't turn on. Cable un-plugged, orange charge light still lit. Battery pull and charge light goes away, device boots fine.
-Test power off/on while plugged to car adapter, fastboot: Charge light blinks off briefly, less then 1 second. Boots fine.
-Test restart while plugged to car adapter, no fastboot: Power off fine. Charge light goes off. Device powers back up fine, charge light returns when second splash screen flickers.
-Test restart while plugged to car adapter, fastboot: Identical to restart with no fastboot. Fastboot broken here too.
-Test power off/on while plugged to car adapter + cradle, no fastboot: Power off fine. Lose charge light for about 10 seconds. Comes back, then device won't boot. Charge light stays on after plug pulled, and still won't boot. Battery pull to reset charge light and boot fine.
-Test power off/on while plugged to car adapter + cradle, fastboot: power off fine. Charge light blinks briefly, power on fine.
-Test restart while plugged to car adapter + cradle, no fastboot: Power off fine. Charge light goes off. Powers up fine, charge light returns when second splash screen flickers.
-Test restart while plugged to car adapter + cradle, fastboot: identical to restart with no fastboot. Fastboot broken here as well.
Cables:
-Stock usb to AC adapter, came with the device.
-Stock usb charge cable, came with the device.
-Car adapter: T-Mobile universal MicroUSB car charger (SUPA34214/738516342146 - Bar code numbers on package)
-Cradle: T-Mobile universal car cradle (SUPA34540/738516345406 - Bar code numbers on package)
Quick summary:
-Power off then on or reset while not plugged in to anything, fastboot or not, all working as it should.
-Power off then on while plugged in to power, no fastboot: Power down fine. Charge light won't go away, only way to boot is with a battery pull.
-Power off then on while plugged in to power, fastboot: Boots fine, the way it should.
-Restart while plugged in to power, no fastboot: Power off fine, device powers up normally. Charge light returns when second splash screen flickers.
-Restart while plugged in to power, fastboot: Acts like fastboot is not turned on. Boots like it would without fastboot checked.
Test Charging: (actual charging, nothing else)
Outlet- Verified working.
Computer- Verified working.
Car Charger- Verified working.
Car Charger + Cradle- Verified working.
It looks like you can get stuck having to do a battery pull if you leave your charge cable in the device after powering down under the right conditions.
Recommend to make sure that power cable is disconnected before powering off, should have no trouble with it.
Can anyone else confirm any of my findings here?
Still have yet to test gps or other functions, will get to it soon.
Click to expand...
Click to collapse
4.0.0.9:
Blue6IX said:
-Download CWM 4.0.0.9
-Plug phone in to pc, drop CWM image on to sdcard main directory.
-Safe disconnect from pc.
-Install terminal emulator and a root file manager from the Google market.
("File Expert" was chosen as the file manager, as some people haven't bought Root Explorer yet. This makes what i've done able to be duplicated by more people more precisely, if that matters at this point)
...install recovery through terminal emulator...
-Deny HTC crash report.
-Hboot to recovery, verify CWM 4.0.0.9
(*NOTE - must use trackpad button to select options in CWM now, power button no longer performs that function)
-CWM Backup.
-power down, then power on device.
-Copy CWM backup to pc, delete previous current backup on card.
-Power down device while plugged in to the pc, fastboot off.
*first press of the power button gets orange charge light, and nothing else. Pressing the power button again makes the charge light go out. Pressing it a third time boots the device normally.
-Power off/on plugged to pc with fastboot on: Works as it should.
-Restart while plugged into pc with fastboot off: Device took a longer time to power down and have the charge light go off then normal. After a brief (about 1 second) pause the charge light came back on, system did not start itself. Pressing the power button turned the charge light off, which came back on after a few (about 4) seconds. Pressing the power button again turned off the charge light, and an immediate re-pressing of the power button booted the device. Booted normally.
Repeated that restart three times with the same exact result each time.
-Restart while plugged into pc with fastboot on: Same as reboot with fastboot off. On this boot the computer (windows xp x86) popped up to say the hardware was not properly installed, so not sure what went on there. Normally booted to the os, not fast.
-Safe removal from pc. Plug back in, opens folder to the sdcard in the phone like it's supposed to. Safe remove again.
-Plug into ac power:
-Power off/on no fastboot: power down, charge light off, back on after about 10 seconds. Press of power button turns off charge light, which returns after a few seconds. Subsequent power press must turn off orange charge light and then turn on the device before the light comes back on, as with being plugged into the pc. Device booted normally.
Tried it two more times, three total. Definitely have to turn the charge light off before I can power on the device.
-Power off/on fastboot: Works as it should.
-Restart with fastboot off: Works just like power off/on no fastboot. Does not restart itself, and must turn charge light of before device will power on.
-Restart with fastboot on: Works just like power off/on no fastboot. Does not restart itself, and must turn charge light of before device will power on.
-End test for the moment. Charged battery to full, fastboot off and powered down while plugged in to AC.
-Power up to Hboot while plugged in to AC.
-Recovery, then advanced, then wipe battery stats.
-Hit back, then power off.
-Unplug AC power after powered down, charge light goes off after about 5 seconds.
-Device powers up normally, i'm off to drain the battery playing with the gps.
So that covers both plugged into the computer and the surge protector/wall outlet. Using the same hardware it came with in the box, as per my prior post.
So far, CWM 4.0.0.9 is better then CWM 4.0.0.8 because I have not had to do a battery pull to get it to boot. In all cases I was able to boot by manipulating the actual power button. Definitely preferred to opening the case any more then necessary.
I'll get to the tests on the car adapter and the cradle later, i'm going to play with it for a little while first.
The bluetooth headset auto paired after every boot, my wireless network was acquired, and cellular service was established.
While not plugged in to a power source, power off/on worked as it should, with fastboot on or off. Restart worked for fastboot off, fastboot on for restart worked the same as fastboot off.
I still have no icons or widgets on my desktop, or in my dock bar. This will change while i'm out playing with it, and i'll make sure to update that when I get back with a gps report.
(but, hey, i'm not responsible for what happens if someone does what i've done here. We're all beta testers and this device is brand new, anyone diving into this pool is at their own risk.)
I'm going to update Google maps, then go kill my battery to get it calibrated.
Click to expand...
Click to collapse
...though we never were at the point where it just wouldn't charge, so you couldn't end up with a dead battery you couldn't juice up - regardless the dark rumor floating around otherwise - trust me it isn't true. Been there, intentionally and done that, can't happen on the recoveries we have out now.
Slapped this in here in part so anyone doing testing for you would have a rough outline of steps to create their own test method from.
Hope this helps, little though it is, because seeing people working on new recoveries is fantastically awesome!
Renamed thread. It's obvious there's a lot of progress in a short amount of time.
Thanks! TWRP2 is ready for release now. Almost fixed all major bugs and I already got the headsup from Dees_Troy. So will be making a release thread later.
Regarding 4ext. Still no word from madmaxx.
what am I supposed to do in this instance?
matt2k12 said:
what am I supposed to do in this instance?
Click to expand...
Click to collapse
Ok when I leave it there to charge after about 5 minutes it tries to boot up again on its own... its like a boot loop but it stays turned off for about 5 mins in between.
Now I believe its officially stuck at the CM logo screen after the data only back up and restore. It stopped turning off which I think was due to battery and when I plugged it into the PC it turned on and has been at the CM logo screen for about an hour now.
It also refuses to boot into recovery now. Stock or Open Recovery. It only shows the green charging LED and when I do a force shut down it blinks on and back on in about 1 second. I have no clue what the deal is. I'm going to try and flash a stock image with RSD Lite and try it all again.
Click to expand...
Click to collapse
Your battery is empty. You can't flash anything via fastboot in such state.
When the battery is empty while starting the phone, the bootloader charges it a bit first (that green LED). Only when the battery is charged a little, it switches to boot.
What you want to do is to catch the moment when it starts to boot and hold the volume-up to get to OpenRecovery. OR supports charging so you can let the battery charge more there.
kabaldan said:
Your battery is empty. You can't flash anything via fastboot in such state.
When the battery is empty while starting the phone, the bootloader charges it a bit first (that green LED). Only when the battery is charged a little, it switches to boot.
What you want to do is to catch the moment when it starts to boot and hold the volume-up to get to OpenRecovery. OR supports charging so you can let the battery charge more there.
Click to expand...
Click to collapse
Thank you again for your responses.
I was thinking along those lines... But it seems like as soon as it gets a charge that it goes right into the boot logo. There doesn't seem to be any middle ground to go to any recovery mode. I was stuck in a similar situation before but it wasn't constantly trying to boot.
Here is what happened:
When I flashed data only, I selected "reboot after" option so it is constantly trying to do that re-boot but since it cant boot it stays at the CM logo I guess until the phone dies. Then it charges for a while with the green LED and then it tries to boot again. I have tried to access all kinds of recovery and fastboot and everything at the usual intervals and I cant get it to start any recovery mode because it is still following the re-boot command from Open Recovery.
I will keep trying but this time seems different than when I had low battery/no recovery in the past instances. Something is overriding my recovery and I think it has to do with the Open Recovery reboot after flashing command.... I even opened up the back of the phone and disconnected the battery and its still not working.
kabaldan said:
Your battery is empty. You can't flash anything via fastboot in such state.
When the battery is empty while starting the phone, the bootloader charges it a bit first (that green LED). Only when the battery is charged a little, it switches to boot.
What you want to do is to catch the moment when it starts to boot and hold the volume-up to get to OpenRecovery. OR supports charging so you can let the battery charge more there.
Click to expand...
Click to collapse
matt2k12 said:
Thank you again for your responses.
I was thinking along those lines... But it seems like as soon as it gets a charge that it goes right into the boot logo. There doesn't seem to be any middle ground to go to any recovery mode. I was stuck in a similar situation before but it wasn't constantly trying to boot.
Here is what happened:
When I flashed data only, I selected "reboot after" option so it is constantly trying to do that re-boot but since it cant boot it stays at the CM logo I guess until the phone dies. Then it charges for a while with the green LED and then it tries to boot again. I have tried to access all kinds of recovery and fastboot and everything at the usual intervals and I cant get it to start any recovery mode because it is still following the re-boot command from Open Recovery.
I will keep trying but this time seems different than when I had low battery/no recovery in the past instances. Something is overriding my recovery and I think it has to do with the Open Recovery reboot after flashing command.... I even opened up the back of the phone and disconnected the battery and its still not working.
Click to expand...
Click to collapse
I got fastboot working by plugging the phone into a dedicated AC power charger, not one with a USB adapter. Then I let it sit on the boot screen for a couple hours. This way it fully charged the battery and I could bring up fastboot.
What was happening with the USB adapter was that it would try to boot, die, and refuse to go to fastboot, over and over again. I would not have got it working without a dedicated AC power charger.
That literally happened to me a few days ago. Fastboot will say a warning on the screen, somewhere around the middle, "Battery Low" or something along those lines, I paid it no attention, as I knew it was plugged in and should've been charging through my processes. Well, the battery has to be at least 50%+ charged before fastboot will allow any connectivity or communication with ADB or Fastboot on pc. Facepalm.
Always double check battery charge at least 60% or more to be in the safe side, or you risk to soft-brick to even hard-brick your phone.