Related
I have a BT338 bluetooth GPS adapter it will not get a lock on and I have been looking for a flash program for it to see if I can reflash it.
I followed a link from a site to this sites ftp server that used to have it but it looks like it has been taken down.
Does anyone know if flashing is possible and if so does anyone have a program to do so?
Thanks for any help.
Packrat,
I have had a BT-338 for two years and I love it. I don't recall that I was ever able to find a method to upgrade the firmware. I will watch this thread in case some one has an answer.
On the other hand, I did have problems when I first got this unit. If I played with changing setting between WAAS/normal and/or Sirf/NMEA modes, sometimes this thing was not get a lock. To fix it I would use a laptop tool to reset the unit to factor setting. I think it was GPSInfo connecting via a BT dongle.
Let me know if this might help and I will look into the exact detail if you need it.
whbell said:
Packrat,
I have had a BT-338 for two years and I love it. I don't recall that I was ever able to find a method to upgrade the firmware. I will watch this thread in case some one has an answer.
On the other hand, I did have problems when I first got this unit. If I played with changing setting between WAAS/normal and/or Sirf/NMEA modes, sometimes this thing was not get a lock. To fix it I would use a laptop tool to reset the unit to factor setting. I think it was GPSInfo connecting via a BT dongle.
Let me know if this might help and I will look into the exact detail if you need it.
Click to expand...
Click to collapse
Thanks for the reply, I tried to reset it to factory via the SirDemo program, but that didnt help. Hopefully I can find a way.
Yes reflash is possible...
You can use SirfDemo and SirfFlash
The procedure is almost the one described here....
http://web.mac.com/tomtastic/site/log/Entries/2007/6/18_Holux_GPSlim236_boot_mode.html
You can download the needed tools here...
http://www.falcom.de/support/software-tools/sirf/
To flash
- First you have to connect your bt-338 using SirfDemo.
- In Action/ Transmit Serial Message select NMEA and send this message
'PSRF100,0,38400,8,1,0' without quotes. This will put the GPS in SIRF Mode.
- After that choose Action / Transmit Serial Message select SIRF this time and send '94' without quotes. This will put the GPS in boot Mode.
- Disconnect now SirfDemo using the button and start SirfFlash without powering down the GPS.
- Choose the correct port and 38400 Baud and - very important -select 'external boot mode'. Browse for the new firmware .bin file and select 'program flash'.
- Execute and enjoy.
Cheers!
I have now (finally!) successfully read the firmware from my two BT338 and a TomTom Mk2 BT mouse. Also important to notice is the following:
- Address Range is 0x0 to 0x7ffff (4 times an "f") resulting in a 512kB bin file.
- Any other speed than 38400 will NOT work!
Did not dare yet to flash actually... I have now:
TomTom Mk-II
GSW3.0.2TomTom1.1_3.0.00.03-C3P1.02b
BT338 (NaviLock labled in Germany)
GSW3.0.2_3.0.00.03-C16P1.02a
GSW3.1.1LowV_3.1.00.07-C23B1.00
I know there must be newer one for BT338 as you can see from the FAQ at Globalsat USA at: http://www.usglobalsat.com/gpsfacts/bt338_gps_facts.html
The mention even different versions there (QA 38):
BT-338_GSW3V3.1.1LowV_F-GPS-03-0506222 and
BT-338_GSW3.1.1TO_F-GPS-03-0510032
I noticed that reading out the SW sometimes delivers different results after 7d008 when some time has passed. I suspect that some data is stored there which may vary over time (satelite positions, routes or whatever may be stored depending on the time).
bye
tobbbie
I can report success now in upgrading my BT338 from the old (3.0.2) FW to the later one (3.1.1) I have retrieved from my other BT338.
Main gain for me is the availability of geoid correction for the height.
Anynone has a later firmware for the BT338 or the TomTom MK2?
You can PM me if you don't want to post here.
bye
tobbbie
GSW3.0.2TomTom1.1_3.0.00.03-C3P1.02b
Hi tobbie,
have you managed to get some new firmwares , I am searching if there is a new one for the tomtom ( there is still some issues between the treo and the tomtom related to the bluetooth stack ). Is there a way to use the BT-338 or a part of the BT-338 firmware in the tomtom ?
thanks
Laurent
look here: http://www.gpspassion.com/forumsen/topic.asp?TOPIC_ID=27925&whichpage=11
please read all posts and follow the wohle story. My TomTom MkII currently runs the 3.2.2 of the latest BT338.
Thanks tobbie,
I have red the full thread, downloaded your dumps of the firmware, and dump my tomtom firmwarewith the sirf tools.
I have compared the dump from your tomtom and mine ( same version 302 ) and they are quite different beiginning in 6D008 :
your firmware :
6D008 : 06 3E 00 00 01 00 00 00 41 46 31 41 39 53 D8 19 ....
my dump :
6D008 : 20 C6 00 00 99 00 00 00 41 46 31 41 39 53 D8 19 ....
Is this part a variable part ( so may be a factory reset and a new dump will give a more comparable result ), or is there a real difference for two same version of the firmware ??
Can you tell me for upgrading the firmware of the tomtom have you used the full 3.11 firmware from 0 to 7FFFF or have you used a dump from 0 to 79999 ?
seeing the various problems some got after flashing their units I am a bit worried before flashing mine..
thanks
Laurent
Just do a system reset of your device and dump it again.
Depending how fast you are getting it into bootmode you have some data there (and not all default empty data). Doing the same after some time (e.g. after a fix was established) will again deliver different data there.
I think the main thing here is that the WHOLE data are dumped and then later flashed to another device. This may also be the rootcause of the failure to use the 0-79999 dump - where after 79999 data may confuse the device to get back online (very sad - it already cost 2 devices one BT338 and one TomTom MkII).
I have used my own dumps to crossupgrade from BT338 to TomTom and the 3.2.2 from antineutrino. After some back and forth I am on 3.2.2 again currently for all devices (living with the green-LED off until a fix).
BTW: I am quite sure that the bluetooth part is not touched by these updates.
The names of the devices as they are recognized on bluetooth are not changing after a FW update.
thanks tobbie ,
as I need this gps in the coming next weeks, I will not take the chance to do the upgrade just now. I will wait a quiter period of time to try it ( so if I brick it I will have time to make a replacement ).
thanks, I will come back for detailled instructions in some weeks.
Laurent
Hi Tobbbie,
I have a Globalsat BT 338, I would like to update the firmware. I downloaded your dumps from http://www.gpspassion.com/forumsen/t...5&whichpage=11, the 3.1.1 version.
Do I understand well that even exists a 3.2.2 version?
If yes where could I find it?
Thanks
patek
It's in the same forum a few post further down - it comes from another member there - just look it up.
Edit: just checked - it seems only the 3.2.4 of the BT368 is there.
I have edited my old post there with a new link that has all info - also for short here:
http://rapidshare.de/files/41287744/Firmware_Globalsat.zip.html
Please read the GPS passion forum entries very thoroughly - it MUST be complete dump that you insert - anything less than 512kB will kill your device (as a poor forum member there had to suuffer)..
Tobbbie,
Thank you for your prompt answer,
I checked my software version, Sirfdemo says: GSW3.1.1LowV_3.1.00.07-c23B1.00 - the same what yours was before upgraded.
I read your opinion about changing to 3.2.2 :
>As mentioned earlier I have yet to discover advantages of 3.2.2 or 3.2.4 over 3.1.1. I >think some trickle power options are more flexible and the DGPS could work - but so far I >could never get a DGPS fix.
So do you think is it worth enough to upgrade? (green lamp!)
Is the WAAS enabled in the 3.2.2 ? (maybe silly question)
Thanks
tobbbie said:
It's in the same forum a few post further down - it comes from another member there - just look it up.
Edit: just checked - it seems only the 3.2.4 of the BT368 is there.
I have edited my old post there with a new link that has all info - also for short here:
http://rapidshare.de/files/41287744/Firmware_Globalsat.zip.html
Please read the GPS passion forum entries very thoroughly - it MUST be complete dump that you insert - anything less than 512kB will kill your device (as a poor forum member there had to suuffer)..
Click to expand...
Click to collapse
hmm, i haven't used my trusty bt338 in quite some time, i might upgrade it just to see what happens..
Does anyone still have the 1.0 apk?
I upgraded to 1.1 now it will not find my sprint modem and problems here and there.
Here you go..... [removed]
taqulic said:
Here you go..... http://db.tt/jnAqmyXk
Click to expand...
Click to collapse
Thank you so much, to bad I can only give you one thanks :laugh: , now everything is working again. I dont know what the dev changed on the update but something did dealing with the sprint modem..etc. and it all went down hill.
Seems like someone else had that problem too.... thought I read it in the reviews..
taulic,
please be so kind and remove the public access to the APK file.
The original package is fixed now.
Note that the program itself is free of cost but not free to copy. If people run into trouble I will provide older versions when asked.
Regards,
Author of PPP Widget
JFDee said:
taulic,
please be so kind and remove the public access to the APK file.
The original package is fixed now.
Note that the program itself is free of cost but not free to copy. If people run into trouble I will provide older versions when asked.
Regards,
Author of PPP Widget
Click to expand...
Click to collapse
Done.
PPP works once, then ned to re-installed
taqulic said:
Done.
Click to expand...
Click to collapse
Hi There,
The app works fine when I install it first, my dongle i being recognized no problem. However if I disconnect, and unplug the dongle and try to connect again, the widget shows "no modem found".
I have tried forcing the app to stop, uninstall stickmount as I thought there was clash between both apps and still it doesn't work. the only work around I v found is to re-install the app, which is not very convenient when on the go and needing internet in the first place to be able to access it.
Would you be willing to provide me the APK installer as I am quite happy to install the app whenever I need it, or maybe suggest a workaround?
you have done a fantastic job by the way
G
file is no longer available
Will you please re-upload the file (PPP wedget 1.00 APK) in drop box since the hyperlink says (The file you are looking for has been deleted or moved). Thank you very much
You should first, email the author of the app and see if he can help you with your problem.
I'm not sure I still have the app in backup... as I only save them for so long. (But I'll check).
For those people having problems with this app, there is a forum and active discussion
Here, click forum link at bottom of page.
http://www.draisberghof.de/android/pppwidget.html
Will you please email this file; thanks
Unknown Zone said:
Thank you so much, to bad I can only give you one thanks :laugh: , now everything is working again. I dont know what the dev changed on the update but something did dealing with the sprint modem..etc. and it all went down hill.
Click to expand...
Click to collapse
Dear "Unkown Zone", will you please email this file (PPP Widget 1.00); thanks
Please email link
Unknown Zone said:
Does anyone still have the 1.0 apk?
I upgraded to 1.1 now it will not find my sprint modem and problems here and there.
Click to expand...
Click to collapse
If you have older version of PPP Widget 1.00 (apk file), please post a link. I have tried many changer.bat options since your last post; both uberoid v11 and 12.1. Nothing seems to work so far to make the ZTE-MF190 work again since upgrade from stock ROM. Tried 2 look for this file however no success. Thank you.
Deleted.
samsung note i717 no drivers found
PPP Widget version 1.3.3
USB_ModeSwitch log from Tue Sep 24 21:36:19 IST 2013
Raw args from udev: 1-1/1-1:1.0
Using top device dir /sys/bus/usb/devices/1-1
----------------
USB values from sysfs:
manufacturer ZTE, Incorporated
product USB Storage
serial 000000000002
----------------
bNumConfigurations is 1 - don't check for active configuration
SCSI attributes not needed, moving on
checking config: /data/data/de.draisberghof.pppwidget/app_tmp/19d2.fff5
! matched. Reading config data
devList 1:
config: TargetVendor set to 19d2
config: TargetProductList set to fff1,fffe,ffff
Driver module is "option", ID path is /sys/bus/usb-serial/drivers/option1
Command to be run:
usb_modeswitch -I -W -D -s 20 -u -1 -b 1 -g 2 -v 19d2 -p fff5 -f $cB
Verbose debug output of usb_modeswitch and libusb follows
(Note that some USB errors are to be expected in the process)
--------------------------------
Reading long config from command line
* usb_modeswitch: handle USB devices with multiple modes
* Version 1.2.7 (C) Josua Dietze 2012
* Based on libusb0 (0.1.12 and above)
! PLEASE REPORT NEW CONFIGURATIONS !
DefaultVendor= 0x19d2
DefaultProduct= 0xfff5
TargetVendor= 0x19d2
TargetProduct= not set
TargetClass= not set
TargetProductList="fff1,fffe,ffff"
DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
QisdaMode=0
QuantaMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
CiscoMode=0
BlackberryMode=0
PantechMode=0
MessageEndpoint= not set
MessageContent="5553424312345678c00000008000069f030000000000000000000000000000"
NeedResponse=0
ResponseEndpoint= not set
InquireDevice disabled
Success check enabled, max. wait time 20 seconds
System integration mode enabled
Use given bus/device number: 001/002 ...
Looking for default devices ...
bus/device number matched
searching devices, found USB ID 19d2:fff5
found matching vendor ID
found matching product ID
adding device
Found device in default mode, class or configuration (1)
Skipping the check for the current configuration
Using interface number 0
Using endpoints 0x0a (out) and 0x89 (in)
USB description data (for identification)
-------------------------
Manufacturer: ZTE, Incorporated
Product: USB Storage
Serial No.: 000000000002
-------------------------
Looking for active driver ...
OK, driver found; name unknown, limitation of libusb1
OK, driver "unkown" detached
Setting up communication with interface 0
Using endpoint 0x0a for message sending ...
Trying to send message 1 to endpoint 0x0a ...
Sending the message returned error -6. Trying to continue
Resetting response endpoint 0x89
Could not reset endpoint (probably harmless): -6
Resetting message endpoint 0x0a
Could not reset endpoint (probably harmless): -6
Device is gone, skipping any further commands
Bus/dev search active, referring success check to wrapper. Bye.
ok:busdev
--------------------------------
(end of usb_modeswitch output)
Checking success of mode switch for max. 20 seconds ...
Waiting for device file system (1 sec.) ...
Reading attributes ...
Mode switch has completed
Mode switching was successful, found 19d2:fff1 (ZTE, Incorporated: ZTE CDMA Tech)
Device class of first interface is ff
Now checking for bound driver ...
No driver has bound to interface 0 yet
Module loader is /system/bin/insmod
Trying to find and install main driver module "option"
Checking for active driver path: /sys/bus/usb-serial/drivers/option1
Driver not active, try to find module "option"
Can't find module "option"
Existing path found:
No way to use driver "option"
- try falling back to "usbserial"
Module "usb_serial" not found, can't do more here
Driver binding did not work for this device
All done, exiting
QUOTE=taqulic;34223799]Here.
http://www.filesend.net/download.php?f=4c6891af31cb635623fac53e094def52[/QUOTE]
Sir,
Using samsung note i717with official jb rom 4.1.2, ppp app says driver not found, device log is as above. Request you to help in this regard.
I hope I'm posting this in the proper forum, i seem to have a difficult time doing that.
Anyways, I'm new to rooting and installing roms on my device, so I figured I'd share a small package I use that's helped me a lot.
It contains instructions and all the files and programs needed to root Galaxy S3 SGH-i747M Rogers Canada, it also contains everything needed (minus the stock rom) to un-root, reset counter and return to stock rom.
I know this information is on these forums, but I had trouble finding it all and understanding some of it, these forums can be a bit overwhelming to someone new like me.
Each folder contains clear instructions, please read them if you use this.
Here's a virus scan output and the download http://www.mediafire.com/?dghrbsng7t1i6o7
SHA256: b0de26ac1b750750ea560d2fdce89729275d8cdb28426f87de6bde08f4fb700a
File name: Galaxy S3 SGH-i747M-Root-Unroot Kit.zip
Detection ratio: 0 / 44
Analysis date: 2013-02-09 20:02:59 UTC ( 1 minute ago )
Moving to General Section, as this is more of a guide. Don't worry, it will get more exposure that way.
Sent from my SGS III
Q&A for Smartwatch 2 firmware hacking
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Smartwatch 2 firmware hacking. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Hello everyone!
SW2 went into a state of brick.
issue:
The night was updated and hiking battery case has turned off, because the next morning found that the watch off when he saw the inscription included Sony, and the firmware version in the left corner.
Launched dfu-util flashed section of the Internal * .dfu
After that, the clock does not start, just a black screen.
After trying different dumps, bins from a sw2, extracted from custom * .apk files bl.bin and asw.bin
To update the internal address - 0x08000000 for eMMC - 0x00000000.
Everything goes well and without errors, shows a black screen continuously in DFU mode
The question is, do they really bring their condition brick, if you still so, how ???
Help who than can ... dumps, bins, address firmware =)
The conclusion of the process of the firmware:
C:\MinGW\bin>dfu-util -c 1 -i 0 -a 0 -D 1.dfu
dfu-util 0.7
Copyright 2005-2008 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2012 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to [email protected]
Opening DFU capable USB device... ID 0fce:f0fa
Run-time device DFU version 011a
Found DFU: [0fce:f0fa] devnum=0, cfg=1, intf=0, alt=0, name="@Internal Flash /
0x08000000/03*016Kg,01*016Kg,01*064Kg,07*128Kg,03*016Kg,01*016Kg,01*064Kg,07*128
Kg"
Claiming USB DFU Interface...
Setting Alternate Setting #0 ...
Determining device status: state = dfuUPLOAD-IDLE, status = 0
aborting previous incomplete transfer
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 011a
Device returned transfer size 2048
Dfu suffix version 11a
DfuSe interface name: "Internal Flash "
file contains 1 DFU images
parsing DFU image 1
image for alternate setting 0, (5 elements, total size = 858340)
parsing element 1, address = 0x0800c000, size = 24320
............
parsing element 2, address = 0x08020000, size = 111992
.......................................................
parsing element 3, address = 0x0803fffc, size = 392
.
parsing element 4, address = 0x08040200, size = 721592
................................................................................
................................................................................
................................................................................
................................................................................
.................................
parsing element 5, address = 0x080ffffc, size = 4
.
done parsing DfuSe file
*sorry for my English
Brick?
ok guys, i buy yesterday sw2 and i try update today by my xperia Z2. after this watch has stuck on update screen. i try reflash few times by dfu util but still nothing. someone on this forum attach the file original.dfu but dfu utili cant flash and give me error Only Dfsus file version 1.1a is supported. so at this moment ive got black screen but still computer see dfu usb when i plug watch to computer. can someone help me to reflash to stock or custom doesnt matter but i need to live this watch. im spend 60 Pound for this watch and now dead... Sorry for my bad english I am polish
It's been a while since this page was made and nobody has ported any custom recovery or rom to this phone, and I don't know why.
I know. It's crazy seeing as how popular this phone is. I don't think they're lazy, I think they are focused on, like, flagship devices and such. Which is really the opposite of how they used to be. They used to post EVERYTHING they tinkered with and they tinkered with EVERYTHING. Now it's as if nobody cares. As if their hobby has become a chore to them. Probably there is money behind it somewhere. Capitalism gets them all sooner or later. I'm really talking out of my ass, but it wouldn't surprise me. I guess I'm just bitter about how I got so much help with a junk phone like the L38C, but nobody has time for a $200 phone. Wack
R41N MuTT said:
I know. It's crazy seeing as how popular this phone is. I don't think they're lazy, I think they are focused on, like, flagship devices and such. Which is really the opposite of how they used to be. They used to post EVERYTHING they tinkered with and they tinkered with EVERYTHING. Now it's as if nobody cares. As if their hobby has become a chore to them. Probably there is money behind it somewhere. Capitalism gets them all sooner or later. I'm really talking out of my ass, but it wouldn't surprise me. I guess I'm just bitter about how I got so much help with a junk phone like the L38C, but nobody has time for a $200 phone. Wack
Click to expand...
Click to collapse
Nowdays, 200 for a phone is cheap.
Arealhooman said:
Nowdays, 200 for a phone is cheap.
Click to expand...
Click to collapse
That's the way I meant it. They are too busy working on flagship phones then to address the wee man. Or so it may seem
R41N MuTT said:
That's the way I meant it. They are too busy working on flagship phones then to address the wee man. Or so it may seem
Click to expand...
Click to collapse
well, you can always port it yourself, or request from a devoloper and in exchange give them a donation.
R41N MuTT said:
I know. It's crazy seeing as how popular this phone is. I don't think they're lazy, I think they are focused on, like, flagship devices and such. Which is really the opposite of how they used to be. They used to post EVERYTHING they tinkered with and they tinkered with EVERYTHING. Now it's as if nobody cares. As if their hobby has become a chore to them. Probably there is money behind it somewhere. Capitalism gets them all sooner or later. I'm really talking out of my ass, but it wouldn't surprise me. I guess I'm just bitter about how I got so much help with a junk phone like the L38C, but nobody has time for a $200 phone. Wack
Click to expand...
Click to collapse
You realize people out there have a life. "capitalism gets them all sooner or later" what the heck does that mean? Do you mean they want to spend their time working on things that better their life? Seems like a completely reasonable thing to do.
Tonyconman said:
You realize people out there have a life. "capitalism gets them all sooner or later" what the heck does that mean? Do you mean they want to spend their time working on things that better their life? Seems like a completely reasonable thing to do.
Click to expand...
Click to collapse
Of course it is. Everything is business. It does not say at the top of this site that this is for charity. I'm aware of that. I'm trying to use guilt to bait somebody into helping me. Lol. And you're ruining it.
Arealhooman said:
well, you can always port it yourself, or request from a devoloper and in exchange give them a donation.
Click to expand...
Click to collapse
How much does the donation have to be?
Liroa said:
How much does the donation have to be?
Click to expand...
Click to collapse
It doesn't have to be anything. But if you find a dev, a donation of how much you think the product is worth will motivate them.
Okay, I tell you what. I'm going to try and hunt down a copy of twrp for the mt6337 SoC. If I can find it there /is/ a way to port it over to work with the revvl v+ hardware. You should be able to flash it with sp flash tool. No promises because I still have to reinstall everything and resolve this sp flash tool error in receiving. I can't flash jack until I do, which means I can't test. Anybody want to provide me with sp flash tool operation error code list? Or maybe give me a hand resolving this error? I'm so vulcan close to finishing a complete guide.
R41N MuTT said:
Okay, I tell you what. I'm going to try and hunt down a copy of twrp for the mt6337 SoC. If I can find it there /is/ a way to port it over to work with the revvl v+ hardware. You should be able to flash it with sp flash tool. No promises because I still have to reinstall everything and resolve this sp flash tool error in receiving. I can't flash jack until I do, which means I can't test. Anybody want to provide me with sp flash tool operation error code list? Or maybe give me a hand resolving this error? I'm so vulcan close to finishing a complete guide.
Click to expand...
Click to collapse
What error did you get using sp flash tool?
Liroa said:
What error did you get using sp flash tool?
Click to expand...
Click to collapse
I'll let you know when I get home. I'll post again in 20 minutes. Basically, mt6833 scatter.txt got illegal file name. Then please choose a ROM. I could pick a disk image from the list of img fingers included in the stock rom, but I'm not sure which. This a/b partition is new to me. I mean, I get it, but some of the file names have changed, like boot_a and boot_b instead of image and recovery, for example. I'm trying to flash stock ROM to REVVL V+ 5g. I have the bootloader unlocked, I was rooted, but I unrooted. I have the firmware zip, a scatter file name 6833, same as the SoC... I even have payload.bin from an ota file, but failed to extract payload.bin and therefore no scatter there. I used
i have an OTA zip, stock firmware. i think my problem starts with not properly extracting scatter.txt from payload.bin. are you familiar with REVVL V+ 5g? Do you have a copy of these files? I thought I had the right ones, or maybe I'm doing something wrong. I could link you to the three different guides I tried with the same results. Without those files or knowing how to get them I'm at a standstill. If you know how to use payload dumper and SP flash and all that, I could use some assistance.
TWRP 3.6.0 released with support for devices that launched with Android 11
TWRP 3.6.0 is here, and it finally brings support for Android 11. The new release also improves the installation process. Check it out!
www.xda-developers.com
^twrp for revvl v+ 5g??? looking for 'sprout'
Tonyconman said:
You realize people out there have a life. "capitalism gets them all sooner or later" what the heck does that mean? Do you mean they want to spend their time working on things that better their life? Seems like a completely reasonable thing to do.
Click to expand...
Click to collapse
i thought you weren't supposed to solicit or spam on this site? so offering to do sruff for donations or offering donations technically is a violation of xda policy. of course, they'll probably make an exception. not to mention, if they want help, link them to your site where you can make money from marketing- oh wait. that takes away from xda making money from ads. btw, they make money from ads. anywaym yeah, it's not just feeding your family at that point. not to mention thats not what this site was supposed to be about. not what the x in xda stands for. lol
how do you delete posts?!
Liroa said:
It's been a while since this page was made and nobody has ported any custom recovery or rom to this phone, and I don't know why.
Click to expand...
Click to collapse
It is possible that the development community for this particular phone is not active or large enough to produce custom recoveries or ROMs. It could also be due to the phone's hardware limitations or the lack of resources and interest from developers' geometry dash lite. If you are interested in having a custom recovery or ROM for your phone, you could try reaching out to the development community and see if there is anyone who is willing to work on it. Alternatively, you could consider using a different phone model with a more active development community.
Dickent said:
It is possible that the development community for this particular phone is not active or large enough to produce custom recoveries or ROMs. It could also be due to the phone's hardware limitations or the lack of resources and interest from developers' geometry dash lite. If you are interested in having a custom recovery or ROM for your phone, you could try reaching out to the development community and see if there is anyone who is willing to work on it. Alternatively, you could consider using a different phone model with a more active development community.
Click to expand...
Click to collapse
i guess the developers choose not to buy this phone? it's a cheapie so we likely can't afford to pay a dev. they don't care about us anymore. they only do it for money unless it's convenient. o can show you messages from senior members that pretty much says exactly that. porting a rom or recovery isn't all that difficult in many cases. porting a custom recovery, if all goes well, can actually be done in about 10 minutes if one knows what one is doing. however, what it looks like on paper hardly works out that way in reality. where there's only a few steps to port twrp i've run into a host of hangups and i'm now on week 3 and i've gotten nowhere. thos device is crappy, the file system is relatively new and very different from previous devices, it's not very popular, or so it would seem, and there just isnt a lot of support for it. all this will certainly change when the a13 update rolls out and people start captiring bug reports and securing the elusive ota that is the master key. sadly, i feel like this phone will get left in the dust and just skipped over. which doesn't make sense because it's getting a13. and it's new enough it could potentially see a14. which means we SHOULD be working on it. a good, cheap, solid, modern device. that seems like a prime candidate for a custom rom. but it has 2 things against it- one it's a tcl and people seem to hate mediatek and tcl. Mediatek has a lpot of good sh!t though, says me. The other is that it's a/b and there's just not a fat lot of that floating around. it's BEEN around, since like 2015 or something, but it's just now becoming a standard. there's a lot more going on for the old recovery partition devices. that'll change, surely, but by the time it does, this phone will be obsolete, i'm afraid. let's hope not.
Liroa said:
What error did you get using sp flash tool?
Click to expand...
Click to collapse
i figured it out. all by myself, of course. don't know what i was expecting, but that's the sum of it. anyway, the trick was to bypass DA to flash with sp flash. twrp is unneccessary, unless you just want the ease of access. in which case, i'm working on porting out TWRP for the REVVL V+ 5g. Once again encountering yet more hangups. on the bright side, flashing back to stock is now possible. There is a guide in the forums. I'm not sure who wrote it. Must be one awesome guy. And handsome. Let's not forget handsome. And smart. Whoever that guy is.
R41N MuTT said:
i figured it out. all by myself, of course. don't know what i was expecting, but that's the sum of it. anyway, the trick was to bypass DA to flash with sp flash. twrp is unneccessary, unless you just want the ease of access. in which case, i'm working on porting out TWRP for the REVVL V+ 5g. Once again encountering yet more hangups. on the bright side, flashing back to stock is now possible. There is a guide in the forums. I'm not sure who wrote it. Must be one awesome guy. And handsome. Let's not forget handsome. And smart. Whoever that guy is.
Click to expand...
Click to collapse
I would love to flash mine back to stock!
R41N MuTT said:
i figured it out. all by myself, of course. don't know what i was expecting, but that's the sum of it. anyway, the trick was to bypass DA to flash with sp flash. twrp is unneccessary, unless you just want the ease of access. in which case, i'm working on porting out TWRP for the REVVL V+ 5g. Once again encountering yet more hangups. on the bright side, flashing back to stock is now possible. There is a guide in the forums. I'm not sure who wrote it. Must be one awesome guy. And handsome. Let's not forget handsome. And smart. Whoever that guy is.
Click to expand...
Click to collapse
I have always been interested in building roms. I just got access to this phone as a dev phone and, as long as flashing back to stock works reliably, I would be fine doing some messing around with rom building for it. If you get TWRP working that is awesome. Do you know if there is a list anywhere of device specific code?
Monsair said:
I have always been interested in building roms. I just got access to this phone as a dev phone and, as long as flashing back to stock works reliably, I would be fine doing some messing around with rom building for it. If you get TWRP working that is awesome. Do you know if there is a list anywhere of device specific code?
Click to expand...
Click to collapse
Could there be a guide you used or some specific steps to bring this phone back to stock?
Mine is not turning on the screen at this point and the mtkclient gives
DAXFlash - [LIB]: Error on sending parameter: DA exceed max num (0xc0070005)
mtkclient GUI Log:
Code:
..Port - Device detected :)
Preloader - CPU: MT6833(Dimensity 700 5G k6833)
Preloader - HW version: 0x0
Preloader - WDT: 0x10007000
Preloader - Uart: 0x11002000
Preloader - Brom payload addr: 0x100a00
Preloader - DA payload addr: 0x201000
Preloader - CQ_DMA addr: 0x10212000
Preloader - Var1: 0x73
Preloader - Disabling Watchdog...
Preloader - HW code: 0x989
Preloader - Target config: 0xe7
Preloader - SBC enabled: True
Preloader - SLA enabled: True
Preloader - DAA enabled: True
Preloader - SWJTAG enabled: True
Preloader - EPP_PARAM at 0x600 after EMMC_BOOT/SDMMC_BOOT: False
Preloader - Root cert required: False
Preloader - Mem read auth: True
Preloader - Mem write auth: True
Preloader - Cmd 0xC8 blocked: True
Preloader - Get Target info
Preloader - BROM mode detected.
Preloader - HW subcode: 0x8a00
Preloader - HW Ver: 0xca00
Preloader - SW Ver: 0x0
Preloader - ME_ID: 96C8388057AFD372754DCBB4B155D5B1
Preloader - SOC_ID: 116C6A57A536601BE60E0E7BA9C4E0B86D979A21F11E8ABA0FB2E6A7DAA9E062
Port - Device detected :)
DAXFlash - Uploading xflash stage 1 from MTK_AllInOne_DA_5.2152.bin
xflashext - Patching da1 ...
xflashext
xflashext - [LIB]: Error on patching da1 version check...
xflashext - Patching da2 ...
DAXFlash - Successfully uploaded stage 1, jumping ..
Preloader - Jumping to 0x200000
Preloader - Jumping to 0x200000: ok.
DAXFlash - Successfully received DA sync
DAXFlash - UFS Blocksize:0x1000
DAXFlash - UFS ID: H9HQ54ACPMMDAR
DAXFlash - UFS MID: 0xad
DAXFlash - UFS CID: ad014839485135344143504d4d444152
DAXFlash - UFS FWVer: 41303032
DAXFlash - UFS Serial: 323031304238453143413030
DAXFlash - UFS LU0 Size: 0xee5800000
DAXFlash - UFS LU1 Size: 0x400000
DAXFlash - UFS LU2 Size: 0x400000
DAXFlash - DRAM config needed for : ad014839485135344143504d4d444152
DAXFlash - No preloader given. Searching for preloader
DAXFlash - Sending emi data ...
DAXFlash
DAXFlash - [LIB]: Error on sending parameter: DA exceed max num (0xc0070005)
DAXFlash
DAXFlash - [LIB]: Error on sending parameter: DA exceed max num (0xc0070005)
DAXFlash
DAXFlash - [LIB]: Error on sending parameter: DA exceed max num (0xc0070005)
DAXFlash
DAXFlash - [LIB]: Error on sending parameter: DA exceed max num (0xc0070005)
DAXFlash
DAXFlash - [LIB]: Error on sending parameter: DA exceed max num (0xc0070005)
Any input will be greatly appreciated.