Related
Hello,
I've got a bricked Leo. I've bought it with the description that has fallen down, and doesn't work any more.
Actually the display and the digitizer is fine, but the flex board is cut and it doesn't boot any more. Via USB it is recognized as "Qualcomm CDMA...". I guess it's flashed with a wrong radio as it is the US version.
Can someone tell me what I've to do via JTAG to restore it? Just delete an part of the ROM? Or load the bootloader to a specific address in RAM and start it from there to flash a valid ROM?
I've got the knowledge to solder such fine pitch parts and also have a JTAG adapter that works with open OCD, but don't know what to do in that case.
Maybe someone from Germany is reading this, who has the knowledge and the technique, who I can send the mainboard to flash it.
I would be very glad if someone could help me with this!
It seems to be possible to access the device with QPST. QPST finds a Phone in download mode and it might be possible to download a boot image, OS image and so on.
But it doesn't accept .nbh files. Boot image must be a .hex file. So I tried to extract the spl from a stock rom and build an intel hex file, but the QPST downloader doesn't accept this format: "could not open flash programming file".
Any idea how this hex file has to look?
Have you made any progress?
same thang just happend to me!
i flashed
RUU_Leo_1_5_TMOUS_2.10.531.0_Radio_Signed_15.34.50.07U_2.08.50.08_2_Ship.exe
and all was well but i realy didnt like tmoble logos so i tryed
RUU_Leo_HTC_WWE_1.48.405.2_Radio_Signed_15.28.50.07U_2.05.51.05_2_Ship.exe
and aperently it bricked my phone because it wont turn on now!
i hit the yellow button next to teh battery with no luck the phone is now dead!
it was instantly recognised buy my pc as a cdma phone when it was bricked!
now what?
please someone help us!
You did indeed brick your precious HD2 by not reading this forum. It was stated over and over again that flashing a TMOUS HD2 with a .51 ROM will brick your phone. Flashing is not for the faint of heart. You thought you were in the right league, but alas. Back to the minors with a nice Nokia. Good luck!
First of all, ALL THE CREDITS go to CellZealot from TeamBlackHat !
This was only possible with the files that he provided!
I was just a simple "guinea pig" that killed a Razr testing theories about downgrading it back to Gingerbread ! :angel:
So lets, f.... do it.
<Warning> By continuing to read and deciding to start this procedure, YOU ARE ON YOUR OWN! I, CellZealot, TeamBlackHat & XDA-Developers WILL NOT be held responsible for any personal or material damage that might incur from the actions described here! That's your decision to go on, so deal with it! YOU ARE WARNED! <Warning>
Requirements:
- Stock ICS SBF fastboot firmware package. Google is your friend.
- a PC x86 computer with a usb port
- Linux operating system. (Ubuntu, Arch, Gentoo, Slackware, Debian, whatever distro you choose...)
- Linux O.S. knowledge. You must be familiar with the command prompt (Bash Shell) and the commands! That's up to you.
- This software package -> http://www.multiupload.nl/VL33M4I4A3
- The "fastboot" program from the Android SDK (latest version that you can find.)
- a software bricked Razr, that only shows itself as a "OMAP4430" device, under Win. "Device Manager", when plugged. Give it a try under a Windows computer, just to make sure.
- MicroUSB to USB cable. The one that came with your Razr.
- The Razr must be charge to the minimum required the bootloader to enable the flashing process. There are other ways to charge your phone without the stock charger. You can search here on XDA for it.
PS: The factory service cable, allows you to bypass the battery check, by allowing the Razr to receive 5v straight from the usb port. As per CellZealot explanation on third post.
Optional but HIGHLY RECOMMENDED !
- a Motorola Factory/Service Cable. You can build your own or buy one! I recommend buying from "TeamBlackHat" as they make high quality cables and adapters! If you prefer, you can just buy the adapter and use your own MicroUSB cable with it.
About the expected end result: your Razr in FastBoot mode, ready to be flashed with a stock firmware.
<Procedure>
- download the package "spyder_bl.7z" and unpack to a empty directory to avoid any confusion.
- you will end up with 3 files - "omapflash-lnx", "pbrdl.bin" & "brdl.bin"
- make the "omapflash-lnx" file executable
- plug the phone to pc and press the power button for 2 seconds, till it apears as a "Texas Instruments" device under the usb list (lsusb) or in the kernel log.
Now you must be quick and start typing in this order:
sudo ./omapflash-lnx pbrdl.bin
sudo ./fastboot flash brdl brdl.bin
You should get a "Okay" status on both of them.
Check your Razr screen and it shall be on "FastBoot AP Mode". From here, you can keep flashing on Linux or boot up Windows and use RSD, wich is more user friendly besides being GUI-Oriented.
Some facts about the 3 files: they are all "signed files" by Motorola, that's why it is safe to use. The OMAP4430 cpu on the Razr is factory programmed to only execute signed code, that's why we needed to find an exploit to execute unsigned code. Examples are the KExec, Boot Manager & Safestrat. All of them available here on XDA in their respective threads.
Peace.
:good:
PS: Do not thank me or my posts. This guide was only possible due to CellZealot support. You must thank him, if for some reason it helped you recover your phone. Copy that?
PS: Thanks also XDA-Developers for this amazing community!
EDIT: Corrected the part about the Factory Service Cable. It does not allow you to charge the Razr but rather supply the necessary juice for the phone to work without a minimum charge. Thanks again, CellZealot!!!
I've tried & failed to brick my phone~ It's now nearly impossible to brick this phone :good:
Just some notes from my journey,
pbrdl.bin only accept few commands... so no oem unlock
pbrdl.bin is 1st-loader for USB boot (mbmloader.bin is for NAND boot)
brdl.bin is just mbm.bin (motorola boot manager)
Thank you for the excellent writeup and for the recommendations for TBH Factory Cable/Adapters!
You are very welcome and congratulations on fixing your phone and being in a very exclusive club of users who have brought their devices back from the brink of the abyss...the truly bricked phone. Also big kudos for going to great lengths to research and attempt many complex means to fix a device you had broken yourself rather than returning it to your carrier under warranty. Your ultimate success is richly deserved.
A couple of points I wanted to clarify.
The Factory Cable/Adapter does not charge the device at all, but bypasses the battery and smart charging circuit altogether and powers the device directly by supplying +5v on pins 1 and 4. It will always power on the device no matter what state the battery is in or without a battery at all.
The other thing is that depending what the circumstances are that lead to the corrupt boot loader, restoring the device can be even easier and not require flashing the firmware.
In my case, I had specifically overwritten the mbmloader and as soon as I repaired that successfully the phone booted up perfectly fine and fully rooted with everything exactly as I had left it the night I hosed it!
cellzealot said:
Thank you for the excellent writeup and for the recommendations for TBH Factory Cable/Adapters!
You are very welcome and congratulations on fixing your phone and being in a very exclusive club of users who have brought their devices back from the brink of the abyss...the truly bricked phone. Also big kudos for going to great lengths to research and attempt many complex means to fix a device you had broken yourself rather than returning it to your carrier under warranty. Your ultimate success is richly deserved.
A couple of points I wanted to clarify.
The Factory Cable/Adapter does not charge the device at all, but bypasses the battery and smart charging circuit altogether and powers the device directly by supplying +5v on pins 1 and 4. It will always power on the device no matter what state the battery is in or without a battery at all.
The other thing is that depending what the circumstances are that lead to the corrupt boot loader, restoring the device can be even easier and not require flashing the firmware.
In my case, I had specifically overwritten the mbmloader and as soon as I repaired that successfully the phone booted up perfectly fine and fully rooted with everything exactly as I had left it the night I hosed it!
Click to expand...
Click to collapse
Thanks once again, my friend. Corrected as per your definition, the section about the FS Cable.
Peace.
:good:
Thank you for this valuable guide, it is a true unbricking solution for the RAZR. Some mirrors of the spyder_bl.7z file. Just in case
http://www.mediafire.com/?z5gp1ztvwj81qr4
http://www.4shared.com/archive/BtfH6ML8/spyder_bl.html
Sorry my english so bad
My droid razr can't to flash brdl.bin
Just show waiting device
How to fix it?
I'm has do all procedure...
Tq b4...
prue said:
Sorry my english so bad
My droid razr can't to flash brdl.bin
Just show waiting device
How to fix it?
I'm has do all procedure...
Tq b4...
Click to expand...
Click to collapse
Ehm...Why did you try this??? Have you read careful enough what this is about?? I'm pretty sure your problem can be solved much easier than this way. Depending on your problem you have with your device I suggest you to open up a new thread in general section (or Q&A Section) and ask for help. BUT:
Don't flash anything to your phone if you don't know exactly what you're doing!.
dtrail1 said:
Ehm...Why did you try this??? Have you read careful enough what this is about?? I'm pretty sure your problem can be solved much easier than this way. Depending on your problem you have with your device I suggest you to open up a new thread in general section (or Q&A Section) and ask for help. BUT:
Don't flash anything to your phone if you don't know exactly what you're doing!.
Click to expand...
Click to collapse
problem solved master
i'm forget to use latest version of fastboot
now mw droid razr has startup normaly
tq all...
but now get new problem device always on fastboot n show "recipe failed"
maybe you can help me 4 this case...
Have same problem with other omap device Huawei U9500 (OMAP4440), but your advice not working unfortunately.
After the message about sending a file, nothing happens, the phone to mode fastboot not pass.
Any advice?
Hi all! XT926 is here)
Tell me please can I restore bootloader on my xt926 through this method? Right now when i connect common usb cable to moto and type "lsusb" i see:
ID: 05c6:f006 Qualcomm, Inc.
But when I connect the cable on Windows, the device appears and disappears in the system (I can hear the sound) infinite time, until I remove the cable.
Hi fellow xda'rs,
I recently bought a Android TV Stick from Geek(app) from china.
I thought I had found a bargain as its specs were:-
2GB RAM
Quad Core CPU
16GB Storage
I managed to snap this up for £24 which I thought was a bargain but when I got the device delivered and was using it I thought it was a little on the slow side so I began to think it was a clone as its default OS theme was not the same as the usual CX919's aswell.
So I wanted to flash the device with a new ROM specifically the Finless 1.6b ROM.
So after following the instructions to installing the ROM using the software provided with the ROM download I managed to install the drivers and get the software to recognize the device. I then wiped the NAND and attempted to install the ROM but it failed .
Now the device does not boot at all and is not recognized by the PC. Windows just states the device is not recognized and has malfunctioned
So I cannot flash any other or what I believer I have found to be the original ROM for the clone device.
The board states its a GXT_D16_LP_V1.8 150310
I have seen that there are tutorials on putting the device into Mask Flash mode by shorting pins but as this is for the genuine CX919 my board is totally different and does not have the pins available to short I think.
In short could anyone help me to put this device into Mask Flash mode and tell me what id need to do and what pins to short please?
I have attached a couple of pictures of the device and board.
lowery91 said:
hi fellow xda'rs,
i recently bought a android tv stick from geek(app) from china.
I thought i had found a bargain as its specs were:-
2gb ram
quad core cpu
16gb storage
i managed to snap this up for £24 which i thought was a bargain but when i got the device delivered and was using it i thought it was a little on the slow side so i began to think it was a clone as its default os theme was not the same as the usual cx919's aswell.
So i wanted to flash the device with a new rom specifically the finless 1.6b rom.
So after following the instructions to installing the rom using the software provided with the rom download i managed to install the drivers and get the software to recognize the device. I then wiped the nand and attempted to install the rom but it failed .
Now the device does not boot at all and is not recognized by the pc. Windows just states the device is not recognized and has malfunctioned
so i cannot flash any other or what i believer i have found to be the original rom for the clone device.
The board states its a gxt_d16_lp_v1.8 150310
i have seen that there are tutorials on putting the device into mask flash mode by shorting pins but as this is for the genuine cx919 my board is totally different and does not have the pins available to short i think.
In short could anyone help me to put this device into mask flash mode and tell me what id need to do and what pins to short please?
I have attached a couple of pictures of the device and board.
Click to expand...
Click to collapse
problem solved! :d
i found the mask flash mode pins to short by trial and error and luckily enough after 1 hour i solved it and got the pc to flash it back to its original rom. If anyone has the same device or issues and would like to know how to solve this i will be happy to help
I would be interested. I have a very similar clone (was supposed to be mk809iv). I have the same board although possibly different chipset.
I haven't bricked it (yet) but will probably do so if I can't find a way to root it. I think it may have come pre-rooted as super su was preinstalled but it has never worked (possibly because the app updated but not the binary?). I have since tried to update the binary and killed the root access completely.
Questions:
Is the ROM you used pre-rooted or rootable (if you've tried)?
Which pins need shorting? I have a button on the side that may be doing the same thing.
OT. How do I upload images or can I not as a new member?
Thanks in advance
any guide? i have the same device or where to download rom?
If your still looking, i might be able to help with a rom, root, and guide.
Thank you but managed to get root the same day you posted. I may still give it a go when my new tv box turns up though if you dont mind posting the info?
For anyone else interested in how I gained root:
1. Search for, download and install kingroot 4.6.5 (this is the version I used, only the latest version is available from official site and cannot be sure next steps will work with it)
2. Run kingroot and follow steps to gain root (dongle may reboot)
3. BUY super sume from play store.
4. Run super sume and follow steps to replace kingroot with super su.
what pins did you short
I am having problems flashing my hdmi stick . I can't get it to flash mode. which pins did you shorted?
can you email me a picture of it? [email protected] thanks
Lowery91 said:
problem solved! :d
i found the mask flash mode pins to short by trial and error and luckily enough after 1 hour i solved it and got the pc to flash it back to its original rom. If anyone has the same device or issues and would like to know how to solve this i will be happy to help
Click to expand...
Click to collapse
Hello,
Having some problems with this stick .Messed up trying to flash a non rooted rom and now I only get a blue icon in rkbatch tool ( after short pin 5-6 ) and nothing happens. Download boot fail errors for a year...
Can someone help me please?
Is it the same model? What version of rkflash tool are you using. And what version are you trying to flash. In my case I didn't need to short any pins.
spade2be said:
Is it the same model? What version of rkflash tool are you using. And what version are you trying to flash. In my case I didn't need to short any pins.
Click to expand...
Click to collapse
I've used several batchtools from 1.5 ( doesn't see my device at all ) to 1.8, different roms ( neomod, finless, stock cx919 roms )hoping one would give me something. All different bootloaders 1.24, 2.08, 2.13,...
I'm going to check mine out. It's been a minute since I used it. But I got the rock chip tool and the img file. I'll zip it up and pm you the link asap.
spade2be said:
I'm going to check mine out. It's been a minute since I used it. But I got the rock chip tool and the img file. I'll zip it up and pm you the link asap.
Click to expand...
Click to collapse
Thnx a million for your help. I've gone bonkers over this hahaha
Lowery91 said:
problem solved! :d
i found the mask flash mode pins to short by trial and error and luckily enough after 1 hour i solved it and got the pc to flash it back to its original rom. If anyone has the same device or issues and would like to know how to solve this i will be happy to help
Click to expand...
Click to collapse
what pins did you short
I am having problems flashing my hdmi stick . I can't get it to flash mode. which pins did you shorted?
can you email me a picture of it? [email protected] thanks
I have a chinese TVpad2 mini-pc running on custom linux (factory OS) with busybox.
I want to install Android or anything other than the factory OS but there's a lot of problems with this device:
-Filesystem is CRAMFS
-Can only access as root through telnet
-Can't access bootloader or put into FWDN (no info how this is done for this device)
What I have:
-Firmware update that contains the kernel
-Telnet root access
-Physical access to device (USB flashdrive only)
There is a forum dedicated to TVpad but they are also having trouble installing an OS on tvpad2...
What do I need to know that will help me accomplish this?
thanks
TVpad3
Hi,
I actually have TVpad3 which is very similar to your TVpad2, and Im very keen on having Android developed for these TVpads.
Theres probably thousands of these wasted devices around the world after the TVpad pirate network got shutdown.
Ive searched high and low, and so far have Not found any trace of any custom Android development anywhere.
So hopefully we can kick start something here !
This is what I know so far ....
Since the devices run on highly stripped-down Android OS, we know these devices can run android and should be a potential for custom Android development.
Unfortunately theres little hardware or development info out there for these devices.
But as far as I know, the hardware platform for these models are all based on Telechip TCC89xx chips.
https://www.telechips.com/eng/Product/consumer_pro13.asp
I have a TVpad3 personally, which I believe is based on a Telechips TCC8925.
Ive found that there are a few similar devices out there based on this platform, including the Pandawill CX-01 TV sticks which have very similar specs to TVpad3 (512mb RAM, 4gb Flash).
So we definitely know that the TVpad's hardware is capable of running full blown Android !
http://www.cnx-software.com/2012/06...v-box-powered-by-telechips-tcc8923-cortex-a5/
http://www.slatedroid.com/topic/36988-cx-01-cortex-a5/
Telechips has released platform sources here, with the latest being Android KitKat... its a bit old but could have potential for a starting point...
https://www.telechips.com/technical_support/kor/opensource/opensource_list.asp
I havent found anything about booting these devices into Recovery or ADB.
But there seems to be some mention of a "FWDN" mode here:
http://freaktab.com/forum/tv-player-support/other-tv-players/4695-cx-01-information-by-tatubias
http://tvpadtalk.ca/discussion/506/how-to-unbrick-your-tvpad1
http://androtab.info/arm/telechips/how-to-update/
http://auswitch.xyz/2012/08/16/how-to-upgrade-firmware-for-cx-01-mini-pc/
From what I can gather, FWDN works in conjunction with a Windows-based utility used to flash firmware over a USB cable.
And this poses the biggest problem for TVpads, they DONT have any peripheral USB port !
I've pulled my TVpad3 apart, and found what appears to be provision for a USB header, but im not sure if these are functional even if a USB socket was soldered in ?
If we can get a functional USB peripheral port working, then that would lead us to the Second problem, that is, HOW to activate FWDN mode on the TVpad ?
From what I can gather, different Telechip TCC89xx based devices seem to have different ways to enter FWDN mode.
Some devices require a certain key combo to be pressed during power up, while others need a hidden button pressed or certain pins on the circuit board to be shorted.
So before we can even think about developing Android, we need to figure out those two issues...
1 - USB connectivity, so that we can flash it with FWDN tool.
2 - How to enter FWDN mode, so that the FWDN tool can talk to the TVpad.
If we can overcome these two issues, then we can start building sources.
Or even flash ROMs from similar Telechip TCC89xx based devices.
Anyway, I hope this helps anyone out there.
And I hope we can really make some progress here
.
Unfortunately I've hard-bricked my TVpad2 playing around with fdisk command in telnet. I found out that if you repartition and then copied all the data back, changes will be persistent so you can store whatever onto the NAND flash. Just don't delete the partition containing linux which I idiotically did... oh well.
Anyway there's a command utility "tccbox" with various tools one of them having the ability to update firmware. Hopefully TVpad3 has it as well?
Sorry to hear you bricked your TVpad !
I guess your only way back is to FWDN flash it.
I wasnt even aware the TVpads had telnet enabled.
But that "tccbox" utility sounds very interesting.
I wonder if we can use it to flash firmwares from other TeleChips based devices ???
.... such as the Pandawill CX-01 TV sticks.
wildchill said:
Sorry to hear you bricked your TVpad !
I guess your only way back is to FWDN flash it.
I wasnt even aware the TVpads had telnet enabled.
But that "tccbox" utility sounds very interesting.
I wonder if we can use it to flash firmwares from other TeleChips based devices ???
.... such as the Pandawill CX-01 TV sticks.
Click to expand...
Click to collapse
Hi i have found my old TVpad3 but no working now, i want flash it for use to android device, you have any tutorial for this PLS
TY
Hi
I just got a third LMX210 today to add to my collection. Lol really im just trying to solve a problem. I bought a ulma to replace cm and i came across a ulm model and decided to just replace my cm today. The problem is that all three of these phone which normally have easily unlockable bootloaders will not boot into fastboot. The fortune 2 will not even boot into recovery. They all will boot into a blank screen with the android robot and will boot into download mode.
The natural solution would be to install an older or even plain stock firmware. But say you dont have a windows 10 or Mac computer. I havent found a way to flash lg firmware using a linux distribution yet.
On the other phones i tried removing the laff partition to force the phone into fastboot by plugging into pc while holding the volume up button. This did nothing but repeat the logo until the button released.
Yes usb debugging was enabled and adb was used to try these procedures. The drones at lg know nothing and ask to send the phones in for repair.
Short of re-installing the stock firmware there has to be way to get past this. And to tell you the truth i dont have a way to flash the stock firmware so i dont even know if that will work.
Ok guys got any ideas?
Update.
Ok spent 4 hours on a windows pc today trying to flash firmware and install qcom drivers thinking the download errors were due to the drivers. Then at the last moments went to Tecknights page and downloaded and installed the lgup dual mode program.
So the bastitches of higher android office decided to screw everyone out of bootloader unlocking. The ARB numbers have recently (like in the past 3 months) been changed to 003. Meaning you cannot flash firmware with an ARB number lower than 003.
But that doesnt stop us completely. Two ideas initially popped into my head. Hex edit the .kdz so that the ARB number matches the phone. Or lol split the .kdz into its seperate partition images then wipe the partitions and use qdl or lgup to repair the now bricked phone. No device data no ARB no problem.
Im hoping the former works over the latter but ill keep you informed.
But really guys thats extreme and i cant see too many folks going through the wipe process to enable fastboot. So we have to find an easier way.
Is there any way to know what partition the ARB protection resides in? If those parts could be wiped im thinking it might fool the flashtool into thinking that there isnt any protection.
one of your devices is MTK isn't it? can't you use SP Flash Tool like for other Mediatek devices? you should be able to flash images to emmc_user with locked bootloader, for example boot, recovery, system, ... all you need is a correct scatter file (which you could create with WwR MTK)
So your saying finish porting my recovery and use sp flash tools to install it. See i have been curious about that procedure and how not having an unlocked bootloader would effect flAshing from recovery. I was thinking brick. But its worth a try if it wont brick and i get full Root with magisk. Ty
Btw when i was porting my recovery i ran into a rather large well too large problem. When i went repack using abdroid image studio which i have used in the past with out problem, it would not shrink the image back down even though i was only trading a few files. How do i fix that
start with readback boot / recovery. then try to unpack, so you will know the scatter is right (at least, for this partitions) or compare files with your already existing backup files
no problems here with unpacking/ repacking with AIK
IDEA:::: ok so for the Qcom boards i have a solution possibly. I know that the older software versions have working fastboot and recovery going and can be boot loader unlocked. That tells me that a fota uodate is screwing things up.
PROBLEM:::: ARB my fortune 2 will not let me install at all anything before ARB3.
ARB_location:::: bootloader
Solution:::: download and extract the stock .kdz for device with working features. Wipe parts bootloader and laf using qpst and reinstall. Solves two problems in one go. Allows fastboot and and bootloader unlock and future re-install of stock firmware
may work but remember your bootloader is locked and you need to by-pass this via testpoint (or at least previously enabled oem unlocking and don't lost these setting) otherwise sahara will fail
well it was an idea. I just did some fact checking and also looked at the files dumped from the .dz dump of the fortune 2 stock rom. PBL or primary bootloader cannot be removed or flashed according to a thread it is a pernanent installation.
But upon more reading i can flash my recovery and boot.img using qfil in qpst along witn every thing else. But i need to know wether qfil reads ARB info and if so where i can find it in the firmware so i dont flash that img but instead pull it from phone as is.
i would really like to know what the twitterpating deal is with these LMX210 phones. ok when i firsr got my fortune 2 i bought it for two reasons the rootability of the device and the fact that tje msm8937 board came pre-installed with otg software by default which in my eyes meant no more freaking computer to use adb.
Well it is all there the drivers the software. but guess what. it doesnt work. i have no idea whats stopping it all from working but even lsusb doesnt bring a twitch or hint of reading any thing over the usb.
does any one know how to fix this
Yo. There is definitely ways to flash on linux using virtual machines, wine etc to run windows apps but you got ahold of a windows box to use. IF it is in EDL mode (Qualcomm mode with a driver saying 9008 in it..) then there is still faith you can revive it. You will need the firmware dumped from someone then youll need to run a program creating XML files for the phones firmware parition files. Youll next need a firehose which is what they call the programmers for EDL that send through the commands and firmware in a low low level that these programs like LGUP just do not do yet (don't know why..... Im waiting for someone to program the LGUP dev version with an EDL mode using emmcdl along with a way to create XML files too. Who knows maybe it will happen if we bring it up enough. The hardest problem youll have is getting a proper emmc programmer for the phone. I can source a lot so if teknight doesnt have something to help with EDL just get ahold of me and ill see what I have and send you some stuff.
Man i have been trying to unbrick the LMX-210 CV1 devices since last year. Tek has nothing but supports the work in hope of finding a solution. I have a ton of fire hoses and saharas all of which have cost me nothing but frustration. I have almost every qpst made and have tried them all with my firehose and saharas. Thr only thing i havent done is pull the mbns off my phones and try them. Trust me system dumps are crap.
The only sign of life i came by was flashing an sd card with the gpt and then flashing each partition manually using ubuntu. In return i got the battery logo but thats it.
Would love to figure it out though
By the way I have been compiling kernels. I call it the jokerfish kernel. Its packed full of drivers and debugging features plus gpu idlers boosters and all those crazy fishy thIngs. Its got governors and wire guard. Otg support. Io schedulars and overclocks. Cpu hotplugging and fast charge.
Now i cant figure out how to get fast charge to work but its set up for msm-otg phy-msm-otg qpnp-smbcharger and smb135x.
All that and not a single panic to reboot in over a week and 1/2 which is how long its been compiled. I used tweaks from the dragonheart kernel source and ported them over and did a lil c++ magic.
It has kcal too but n0 app supports it. All kinds of media and sound codecs as well. You think it would be slow but my compiling and coding skills are as mad as me. Hahahaha.'
But dont Take my word for as the gentle over there on your couch. See that smile? Hes as happy as fish in a pond.
Just remember Duhjoker is in no way responsible for bricked devices so try it at the risk to yourself.
This particular fishy thingy works for msm8917 cv1 devices like aristo 2 and k8+ which have been tested by the madman himself.
If you like you could thank me but the permanent smiles on your faces will be just as loved.
lol so fast_charge is working on the kernel but you have to add a custom tunable to a kernel app to get it going. Just add the path
/sys/class/power_supply/usb/uevent
Then you will get a choice of values to manipulate