Related
The lack of custom roms for our device is depressing, there aren't enough developers for the M4 aqua and while some have moved on to other devices, others don't share their REAL sources and fixes. So what i propose is that we all join forces and do it ourselves, the more people the better it brings different points of view and consequently faster fixes, so for those that are interested here are the prerequisites:
1. A computer
2. A linux distro (most guides will advice you to go for ubuntu or a buntu based distro personally its not my cup of tea, i use gentoo but linux is about choice you choose what suits you. Also if you want to keep your windows you can either dual boot(recommended) or just use a virtual machine which depending on specs it can be slloooww).
3. A starting point (most people don't even try to compile android because they wont even know where to start from, thankfully sony isn't as bad as others and even provides detailed information on how to compile android for their devices, so i suggest to start here http://developer.sonymobile.com/kno...aosp-marshmallow-for-unlocked-xperia-devices/ )
4. Time (compiling times can take very looonnnggg)
5. Patience ( yeah a hell lotta of it)
Still interested?
We can use this thread to post compiling errors , bugs, errors and any android developing related questions, if instead of aosp you want to jump straight to cyanogenmod the instructions are very similar just replace "repo init -u https://android.googlesource.com/platform/manifest -b android-6.0.1_r10" with "repo init -u git://github.com/CyanogenMod/android.git -b cm-13.0" xda also has some very useful threads we can use here are a few:
1. Compiling roms:
CM - http://forum.xda-developers.com/showthread.php?t=2060017
PAC - http://forum.xda-developers.com/showthread.php?t=2662325
2. Debug
Create logs - http://forum.xda-developers.com/showthread.php?t=2185929
Understand them - http://forum.xda-developers.com/showthread.php?t=2274119
Every great dev had to start at some point this might be start of some great devs (we need them), so lets start compiling and bring the marshmallow to the tulip!!!
We have a few custom roms that just need bug fixes. We will get better as time goes on. And would we see a rom of yours anytime soon?
I don't find the m4 binaries in this page http://developer.sonymobile.com/knowledge-base/open-source/open-devices/list-of-devices-and-resources/
Hello guys, as much of you know, I tried so many times to compile roms for our device, but never had success. My device for now enter in a "bricked fastboot" mode, and in flashmode Flashtool say that the device have debugging off. Totally bricked. But, I will never give up with my work for this device. I will make roms for you guys and for my experience, also if I cannot test. So, I installed Ubuntu in my PC, I am syncing the sources and this time I will try very hard! Thanks CarDGee for your post, it will be helpful for errors.
So, what would be our requirements knowledge wise? What programming language base, etc?
Any kind of knowledge of programming language can be useful, but is not needed.
alby_var said:
Hello guys, as much of you know, I tried so many times to compile roms for our device, but never had success. My device for now enter in a "bricked fastboot" mode, and in flashmode Flashtool say that the device have debugging off. Totally bricked. But, I will never give up with my work for this device. I will make roms for you guys and for my experience, also if I cannot test. So, I installed Ubuntu in my PC, I am syncing the sources and this time I will try very hard! Thanks CarDGee for your post, it will be helpful for errors.
Click to expand...
Click to collapse
I think at this point it would be smart to collaborate on a custom rom (probably CM 12.1 because it is closest to stable) so we have a base to develop more roms.
For now I'm working to build AOSP 5.0
I followed the instructions to build AOSP at developer.sonymobile.com
At point 4. it say
Find the software binaries for the device you want to use on Sony’s AOSP for Xperia devices
Click to expand...
Click to collapse
Now i have downloaded the binaries for the M2. It have the Kanuti and Tulip folder inside.
Can i use it for build or do i have to extract the files from the device?
Second question is. I can remove other devices from local_manifests.xml right?
You can also use GitHub sources and put them into android sources with git clone, with this method also if you edit files, you'll not have problems with repo sync.
@dani020110 download the Z5 ones inside the zip you will have kanuti and tulip folders as well.
@alby_var what do you mean "bricked fastboot" is it constantly with blue led on? have you tried holding powerbutton + vol up until it vibrates 3 times?
@jefins although its a plus to know C java etc.. its not a requirement i am a strong believer that you learn by doing it.
@jtg01 yes use the ones from the zip also take a look at this repo https://github.com/SonyAosp you can find the binaries there under platform_vendor_sony and platform_vendor_qcom.
Now i regret not having done one of those "Reserved" on the second post.....
@alby_var what do you mean "bricked fastboot" is it constantly with blue led on? have you tried holding powerbutton + vol up until it vibrates 3 times?
..
Click to expand...
Click to collapse
The device , on a pc without drivers is recognized as qhsusb_bulk. It is recoverable, but any tool doesn't recognize the smartphone.
On a pc with all drivers it is recognized sometimes as SOMC FLASH DEVICE, other times in SEMC FLASH DEVICE. Also this is recoverable, but Flashtool says that the device have debugging mode off. (I cannot boot to the rom to activate it.)
And the only led that the device show is red, it bright up 3 times only when the battery is at 0%
alby_var said:
The device , on a pc without drivers is recognized as qhsusb_bulk. It is recoverable, but any tool doesn't recognize the smartphone.
On a pc with all drivers it is recognized sometimes as SOMC FLASH DEVICE, other times in SEMC FLASH DEVICE. Also this is recoverable, but Flashtool says that the device have debugging mode off. (I cannot boot to the rom to activate it.)
And the only led that the device show is red, it bright up 3 times only when the battery is at 0%
Click to expand...
Click to collapse
Do you have the correct flash and adb drivers on your pc? My second phone is a xperia E4.i had the same problem with SEMC and SOMC.i thought that it was bricked but the problem solved when i installed adb and flash drivers from the flashtool drivers file.
I installed all drivers that is on the Flashtool Folder trought the exe, but Flashtool not start flashing...
So i compiled the sources and got a system.img and a userdata.img in out/target/product/generic ?
I think there have to be a boot.img. Do i have to compile the kernel as well? Cause instructions on sony developer say the repos contain a precompiled kernel.
@alby_var: which version of flashtool do you use? Had also problems to flash firmware on newest version. So i installed Flashtool Version 0.9.19.7. With that it worked fine.
@alby_var try the linux version of flashtool
@jtg01 there must be something wrong because it should be out/target/product/e2303 or out/target/product/tulip did you choose our device after source build/envsetup.sh && lunch? because i believe you just compiled generic android.
Compiled android 6 for 2303, attached the Make log Below. (Pure Sony AOSP)
yet to flash the images and check.
made a small change, the userdata.img is for 16GB as i have a M4 Aqua Dual (E2363) the device should be able to boot up, will add logcat when i have it.
Lots of warnings but was able to make successfully
open the log in notepad++
Edit: First attempt to boot, loops at Sony logo.
will make fresh and check again
@jtg01 there must be something wrong because it should be out/target/product/e2303 or out/target/product/tulip did you choose our device after source build/envsetup.sh && lunch? because i believe you just compiled generic android.
Click to expand...
Click to collapse
Yeah there was a problem. Now it compiled all img's . But userdata.img has only 70 Mb. System is 900 Mb.
Should i flash this?
Edit:
Flashed it got bootloop. Can't take a logcat cause it restart at Sony logo.
But i get a kernel_boot_log. There are multible errors. Maybe someone can help me with that.
Guys I not know how to adapt device sources to the rom for that I am building.. Can anyone please help me?
@RohitBopnna and @jtg01 for some strange reason newest firmware doesnt allow you to flash custom firmware you will have to downgrade to .128 and then flash your roms i am sure it will boot, follow the instructions on Jeffreyvh aosp thread http://forum.xda-developers.com/m4-aqua/development/aosp-6-0-e2303-t3271380
@alby_var I think you should start by compiling something we already have the sources see how it goes, and then move on
Phone bricked stuck on Android screen,access to adb & fastboot logs provided [Solved]
Hello,
I recently messed up my phone. Long story short, I snatched an OTA, modified it and tried to force it on my phone. The vanilla OTA always failed in the check process because I modified some /system files on my phone. In result of that, a couple of files has been wrongly patched ( /system/app/OpenWnn/OpenWnn.apk ; /system/bin/debuggerd ; /system/bin/install-recovery.sh ; /system/priv-app/ApeCloudFileManager/ApeCloudFileManager.apk ; and maybe others indirectly ). I can provide more informations about my slip up if you wish.
Since then when I start my phone I'm stuck at the "Wiko, powered by Android" screen. I can access the stock recovery menu, and the factory mode. I also have access to my phone throught adb, adbd, and fastboot.
My phone is a Wiko Rainbow Lite 4G ( http://world.wikomobile.com/m745-rainbow-lite-4g ), the actual manfacturer is Tinno so the phone is probably sold under different names around the world, Wiko being only a "middle-man".
With that said, I can't flash the ROM using the utility given to me by Wiko. They do not provide "stock rom" with scatter file, but instead use their own software, a sole .exe file ready-to-use, you hook your phone to your pc, restart the phone by pressing random combination of buttons, and voila. However, I managed to extract the system.img, boot.img, etc files from the .exe . So I figured out I could try to use "fastboot flash system system.img" command to restore whatever files are messed up. Might as well not touch /recovery and /boot because I can access the recovery the phone seems to boot correctly ( from what I understand /boot is just a bootloader, so me being a pc-guy I wouldn't see the point of reinstalling GRUB if windows was missing a dll or something like that ) .
But the phone is locked .... Here's the "fastboot oem device-info" result
Code:
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.005s]
And I when I try to "fastboot oem unblock" :
Code:
FAILED (remote: oem unlock is not allowed)
So yeah .... I'm stuck there. If anyone got an idea, even a vague one of what I could try next to unbrick my phone that would be very kind of you. There's no wrong answers. So please if you got a couple minutes to spare (you already made it through my laïus which is already something ) I would be very grateful.
I'm thinking about extracting files from system.img and copy them on my /system partitions throught adbd with a script .... But I'm not sure if that would help or make it worse.
If you need informations here's the logcat I got under "factory mode" ; part1 : http://pastebin.com/nx7BC8K5 , part2 : http://pastebin.com/eU94B9VE
the pstree (because come on, if a phone can launch all of that, certainly there's something we can do to repair it) : http://pastebin.com/ZWd6vC9q
dmesg : http://pastebin.com/RYfbF0ub
prop : http://pastebin.com/k6T4bYnu
cpuinfo : http://pastebin.com/a6eMQTmd
PS : Yes I'm still a noob when it comes to Android, but please if you have any questions, need more informations, ask and I shall provide.
PPS : @moderators, I apologize if I posted in the wrong section, please redirect me
Since you extracted them, they now have a different signature and can therefore not be flashed onto the device because your bootloader only allows ROMs with their signature to be flashed successfully. Also, to clear things out, boot == kernel, boot =/ bootloader. Also, why exactly can't you flash it using their provided tools? If you are going to flash stock ROM you might as well reflash recovery and boot.
Thanks for answering.
I can't flash using their provided tool because the tools fails at 1% progression with a generic message error "oops something wrong happened, good luck with that kido, kisses".
Why do I don't want to flash recovery and boot ? Because these seems to work now, and I'm scared that if I break those I won't even be able to access my phone through adb,fastboot or get to recovery.
About the signature, I've seen plenty of topic/tool/stuff around the internet about how to unpack RUU images (is that what they're called or is RUU specific to htc ?) to update.zip files (eg: http://blog.coralic.nl/2010/01/25/how-to-create-update-zip-using-your-build-aka-system-img/ ; http://lazydroid.com/2011/03/howto-repack-and-sign-rom-image-update-zip-files/) . Problem being they're always wayyy outdated and approximative.
Honestly it would help me a lot in my research if I know what is even wrong with my phone.... I can't make sense of the logcat.
EDIT :
Ok I finally managed to reflash it using a more generic flashtool (designed for qualcomm based phone) named QFIL.exe, found it in this archive http://www.mediafire.com/download/4rgr02wi542n4sw/Qualcomm_tools_and_guidance.rar . Then I simply used the file found in the .exe files to populate the form and yabadabadou !
However my flash screen is now completly black .... I do not even have a prompt when selecting between recovery ("Power"+"vol-" then "vol+") and factory mode ("Power"+"vol-" then "vol-")...
Anyway, now that I know how to safely unbrick it. I can mess with it even more. But I probably should port CWM to it and do a backup pretty quick.....
Aramir said:
Thanks for answering.
I can't flash using their provided tool because the tools fails at 1% progression with a generic message error "oops something wrong happened, good luck with that kido, kisses".
Why do I don't want to flash recovery and boot ? Because these seems to work now, and I'm scared that if I break those I won't even be able to access my phone through adb,fastboot or get to recovery.
About the signature, I've seen plenty of topic/tool/stuff around the internet about how to unpack RUU images (is that what they're called or is RUU specific to htc ?) to update.zip files (eg: http://blog.coralic.nl/2010/01/25/how-to-create-update-zip-using-your-build-aka-system-img/ ; http://lazydroid.com/2011/03/howto-repack-and-sign-rom-image-update-zip-files/) . Problem being they're always wayyy outdated and approximative.
Honestly it would help me a lot in my research if I know what is even wrong with my phone.... I can't make sense of the logcat.
EDIT :
Ok I finally managed to reflash it using a more generic flashtool (designed for qualcomm based phone) named QFIL.exe, found it in this archive http://www.mediafire.com/download/4rgr02wi542n4sw/Qualcomm_tools_and_guidance.rar . Then I simply used the file found in the .exe files to populate the form and yabadabadou !
However my flash screen is now completly black .... I do not even have a prompt when selecting between recovery ("Power"+"vol-" then "vol+") and factory mode ("Power"+"vol-" then "vol-")...
Anyway, now that I know how to safely unbrick it. I can mess with it even more. But I probably should port CWM to it and do a backup pretty quick.....
Click to expand...
Click to collapse
YaY, you can now put [SOLVED] in the title to help other in the same issue you had!
Is this the right forum area? I posted over in CF-Auto root with no response, figured I would try here.
http://www.randmcnally.com/product/tnd-tablet
It supposedly has a custom proprietary build Rand McNally uses. It has a built in recovery of which I'll post a screen.
The "reboot to bootloader" option simply hangs on the boot screen.
I've tried kingroot/kingoroot, towelroot, and googled my life away trying to root this GPS/tablet.
There doesn't seem to be a way to flash a custom recovery without bricking it(unsupported device), and there's no way to pull the recovery.img without root!
Can anyone help? The rooting of these devices would open up a world of possibilities.
How is it possible to root this thing if its not recognized by fastboot? Any attempt of rebooting into bootloader even through external tools is stuck on bootscreen.
It allows the Delevoper option of unlocking bootloader, but how if I can't even send the command? Not only is bootloader locked, it seems completely off limits.
Some possibly relevant details from bugreport, and the logcat file???
========================================================
== dumpstate: 2017-08-30 20:23:15
========================================================
Build: LVY48E.20170428-091903
Build fingerprint: 'TNDT80B/tulip_p1/tulip-p1:5.1.1/LVY48E/20170428-091903:user/'
Bootloader: unknown
Radio: unknown
Network: (unknown)
Kernel: Linux version 3.10.65 ([email protected]) (gcc version 4.9.3 20150113 (prerelease) (Linaro GCC 4.9-2015.01-3) ) #3 SMP PREEMPT Fri Apr 28 09:03:37 CST 2017
Command line: enforcing=1 earlyprintk=sunxi-uart,0x01c28000 initcall_debug=0 console=ttyS0,115200 loglevel=0 root=/dev/system init=/init [email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected][email protected]:[email protected]:[email protected]:[email protected] cma=256M androidboot.serialno=74005034440c1c05088e androidboot.hardware=sun50iw1p1
------ MMC PERF (/sys/block/mmcblk0/stat) ------
*** /sys/block/mmcblk0/stat: No such file or directory
Ok, it is now recognized by my system by fastboot, but no fastboot commands will work! Stuck on the boot animation even though recognized.
Any checks for OEM Device info, Locked bootloader, or Tamper flags just hangs...
Down another rabbit hole after finding out this thing is an "AllWinner" brand Android tablet...
Hey, any chance you could upload the Launcher APK and lib s? I'm also investigating root on a TND740 (which is also Android based), so maybe I can help if I find anything out. The launcher would be awesome though. Thanks!
I'd love to put that software on my Asus Tablet <3 hook us up
tnd t80b bootloop no adb permissions
Hey guys, I have a bootloop on this tablet. And I managed to wipe adb certificates off it so I cant even adb in anymore. TND T80B Anyone have a stock Firmware or any clue how to use this tablet again.
Thanks for any help!
How did u get into fastboot mode from engineering menu? I cant seem too, it just reboots too system after about 1 min.
I assume, like to enter recovery menu, there is a key press combo i need too use after choosing fastboot mode, but i dont know what it is
I think you adb reboot ....
it could be .. bootloader.. fastboot..RUU...RRU..recovery..
I cant remember exactly. I had to get root first I think. this device has an Allwinner A64 chipset on a tulip board. Allwinner has everything available on github and a wiki site for building roms for this device and others.
Felmode... look it up... these are unbrickable...
if you find a rom or a Stockrom let me know please
---------- Post added at 12:30 AM ---------- Previous post was at 12:26 AM ----------
if I could ever get a copy of the api or a compiler to work correctly on linux... I'd have my own to flash on.
Also I've never tried but there is another USB port on the back of this thing where the 2nd GPS hooks on. you might be able to boot or access some un secured path through that.
Lostwon said:
I think you adb reboot ....
it could be .. bootloader.. fastboot..RUU...RRU..recovery..
I cant remember exactly. I had to get root first I think. this device has an Allwinner A64 chipset on a tulip board. Allwinner has everything available on github and a wiki site for building roms for this device and others.
Felmode... look it up... these are unbrickable...
if you find a rom or a Stockrom let me know please
---------- Post added at 12:30 AM ---------- Previous post was at 12:26 AM ----------
if I could ever get a copy of the api or a compiler to work correctly on linux... I'd have my own to flash on.
Also I've never tried but there is another USB port on the back of this thing where the 2nd GPS hooks on. you might be able to boot or access some un secured path through that.
Click to expand...
Click to collapse
I guess i should have been more careful when i posted here, i actually have an Rand McNally OveryDryve 8 not a TND series tablet, and thats the one i cant get into fastboot too get the bootloader unlocked and then root and stuff....
If i cant get fastboot commands too works i cant do anything else...
I would use dr.Phone like others have, but it does not install seemless root apparently, it modifies files that break updates, and i dont want that, id prefer Magisk with seemless so i can then install safteynet and gapps properly
How can I get a copy of the truck gps app to load on another tablet?
AllenScott said:
How can I get a copy of the truck gps app to load on another tablet?
Click to expand...
Click to collapse
Short answer.... You cant.... I tried with a previously rooted model too send the apk file, even if it installs on your new device, it wont work without ALL of the RM Services apps as well, and all have too be system apps and setup just right or its not going too work... I gave up and never ened up getting it too work because i couldnt get half of the apks too istall let alone run without crashing constantly...
I've spoken to rand and they seem to think their GPS hardware is better than that found in today's phones like they are Holy as ####. Their systems are junk but the 2.0 navigation is far worse, I want to pull the old software and install it to a newer or different device like y'all. I'm willing to put some money towards the goal, I know some of my friends would do the same, anyone up for starting a fund, or someone have the skills to make it happen? Let's get this rolling!
Side notes, if you look at the older devices specifically the tndt80 that has Google play on it, (newer ones don't!) I at one time had the installation files and installed them onto a cell phone. I was able to run a route comparison before the software realized my Samsung galaxy wasn't a tnd tablet, once it realized it wasn't one of their devices it had a message saying that and closed down.
I'm pretty sure that's on one of my old phones with a busted screen, I'll get some screens ordered and see if I'm right (hopefully!)
So besides the installation files that would be the next hurdle, maybe an emulator to bypass the device name/serial etc to allow it to run?
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
Hisense just released a new device called the A9. Since this phone has Snapdragon 662 I was wondering how easy it would be to root this device. I know there is an EDL for this CPU. The Hisense A5 series was also rootable. Not sure what method was used.
The Onyx Boox Note Air 2 (a 10.3" tablet), which I have, also runs on the same Snapdragon 662 and can be rooted via Magisk. I used the EDL to dump the boot.img on the Note Air 2 to root it via Magisk.
Disclaimer: I'm not a developer or super technical guy, but have rooted a few devices by following guides.
Does anyone know how easy or fast a root would be available? I'm assuming they didn't lock the bootloader on this device as most Chinese devices.
Hello, could you share with us how to root boox device please?
It would be great if GAPPS could be used.
Replying to bump this thread. I have the Hisense A9 and would love to be able to root. It has an option to unlock the bootloader in the developer options if that is helpful.
formeriphoneuser said:
Does anyone know how easy or fast a root would be available? I'm assuming they didn't lock the bootloader on this device as most Chinese devices.
Click to expand...
Click to collapse
Hello and good morning, @formeriphoneuser
I hope you'll always find and get the support you require.
However, prior to your next posting please read the guidances that are stuck on top of every forum like
[Read Before Posting]QUESTIONS DO NOT BELONG IN GENERAL
Hello Everybody, In order to attempt to keep this forum neat and tidy the moderation team is asking you to post your questions into the Questions and Answers (Q&A) forum and not into the General section. You can find the Q&A forum by clicking...
forum.xda-developers.com
and the others. I've moved the thread to Android Q&A.
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
I recently good a Hisense A9, and I've been trying to extract the boot.img and / or recovery.img from it (since I can't find either of those online yet). So far I've been trying to get boot.img from EDL mode using this EDL tool. I can boot into EDL mode fine, but when I try to run an EDL command there are lots of errors. It's possible I'm using the wrong Firehose file, but I think it's right. (I'll post a link to the logs below). I've been following this guide mainly. Is anyone else working on this?
*Edit* the firehose file I'm using is 0014d0e100000000_d40eee56f3194665_FHPRG.bin.
Anyway, OP - hopefully I, or someone, can get the boot image or recovery image soon, then we should be able to patch it with Magisk fairly easily and install Google Services etc.
A word of warning to anyone who wants to try working on this - every time I restart after being in EDL mode, the phone goes into a boot loop of sorts. I enter the 6-digit pin at boot-up, and the phone says something in Chinese (which Google translates as something like "optimising the system, please wait", from memory), and then keeps showing the desktop screen for a second, then looping back to the pin code input, then showing the message, and then repeat. If you hold down volume down, it'll go into safe mode, but then the same thing happens when you restart. I've always managed to get out of it, but I'm not 100% sure how! Something like holding the power key down for about 10 seconds while it's looping... The phone vibrates, but doesn't turn off, and then the loop stops and you can enter your 6-digit pin again and it's back to normal. If that doesn't work, then try turning the phone off, then back on again, but holding the power key down so it keeps restarting without fully booting. Last time I made it restart ~5 times, and then it was back to normal. Maybe it cleared some kind of system cache...?
These are the errors I get from the EDL tool when I try to extract the boot image.
https://pastebin.com/ejXfCJs9
https://pastebin.com/5CqUPB0a
https://pastebin.com/LMmEmm6v
RunnyYolk said:
I recently good a Hisense A9, and I've been trying to extract the boot.img and / or recovery.img from it (since I can't find either of those online yet). So far I've been trying to get boot.img from EDL mode using this EDL tool. I can boot into EDL mode fine, but when I try to run an EDL command there are lots of errors. It's possible I'm using the wrong Firehose file, but I think it's right. (I'll post a link to the logs below). I've been following this guide mainly. Is anyone else working on this?
Anyway, OP - hopefully I, or someone, can get the boot image or recovery image soon, then we should be able to patch it with Magisk fairly easily and install Google Services etc.
A word of warning to anyone who wants to try working on this - every time I restart after being in EDL mode, the phone goes into a boot loop of sorts. I enter the 6-digit pin at boot-up, and the phone says something in Chinese (which Google translates as something like "optimising the system, please wait", from memory), and then keeps showing the desktop screen for a second, then looping back to the pin code input, then showing the message, and then repeat. If you hold down volume down, it'll go into safe mode, but then the same thing happens when you restart. I've always managed to get out of it, but I'm not 100% sure how! Something like holding the power key down for about 10 seconds while it's looping... The phone vibrates, but doesn't turn off, and then the loop stops and you can enter your 6-digit pin again and it's back to normal. If that doesn't work, then try turning the phone off, then back on again, but holding the power key down so it keeps restarting without fully booting. Last time I made it restart ~5 times, and then it was back to normal. Maybe it cleared some kind of system cache...?
These are the errors I get from the EDL tool when I try to extract the boot image.
https://pastebin.com/ejXfCJs9
https://pastebin.com/5CqUPB0a
https://pastebin.com/LMmEmm6v
Click to expand...
Click to collapse
Maybe try this loader. This is for sure the one I used for my NA2. Otherwise, you have quite some errors that relate to python. Not sure what the issue is there.
formeriphoneuser said:
Maybe try this loader. This is for sure the one I used for my NA2. Otherwise, you have quite some errors that relate to python. Not sure what the issue is there.
Click to expand...
Click to collapse
Awesome, thanks! I should have mentioned which loader I was using (different to the one you linked). I'll edit my post to say what I used before.
I tried the loader that @formeriphoneuser suggested, but with a similar result. (https://pastebin.com/ucMkEkeW). I also tried with the flag --memory="ufs" in case the device has UFS memory, but similar result.
But the good new is, I've just discovered a reliable way to avoid the boot loop after leaving EDL mode. So to leave EDL mode, make sure any running commands have ended, unplug the device from the computer, and press and hold the eink button (on the left of the phone), volume-up, and power button. Keep them all pressed until the first vibration (after about 15 seconds or so, then release the power button only). Keep the other two pressed while the phone boots, and even while you're entering your 6 digit pin code. When you see the main screen you can release the buttons and your phone shouldn't enter the boot loop. I have no idea how much of that is necessary, but something in there works for me.
I've added an Issue to the github repo for the EDL tool I'm using. Other than that, I think I've hit a brick wall and won't be able to do any more for now. Unless anyone knows how to check that the firehose file is correct for my device, and update it if it's not. Hopefully Hisense will release the stock firmware, or send us an OTA update or something.
Does this work? if the Bootloader could be unlocked.
Arthurliao said:
Does this work? if the Bootloader could be unlocked.
Click to expand...
Click to collapse
The problem with a GSI is that Android doesn't have partial refresh support for the eInk display, which means a driver has to be written from scratch, otherwise the display will be verrrrrry slow.
RunnyYolk said:
I tried the loader that @formeriphoneuser suggested, but with a similar result. (https://pastebin.com/ucMkEkeW). I also tried with the flag --memory="ufs" in case the device has UFS memory, but similar result.
But the good new is, I've just discovered a reliable way to avoid the boot loop after leaving EDL mode. So to leave EDL mode, make sure any running commands have ended, unplug the device from the computer, and press and hold the eink button (on the left of the phone), volume-up, and power button. Keep them all pressed until the first vibration (after about 15 seconds or so, then release the power button only). Keep the other two pressed while the phone boots, and even while you're entering your 6 digit pin code. When you see the main screen you can release the buttons and your phone shouldn't enter the boot loop. I have no idea how much of that is necessary, but something in there works for me.
I've added an Issue to the github repo for the EDL tool I'm using. Other than that, I think I've hit a brick wall and won't be able to do any more for now. Unless anyone knows how to check that the firehose file is correct for my device, and update it if it's not. Hopefully Hisense will release the stock firmware, or send us an OTA update or something.
Click to expand...
Click to collapse
Bit of a long shot here, but I vaguely remember having trouble with EDL on my Oneplus 6T and I think the solution was to use a USB2 port instead of USB3.
RunnyYolk said:
I tried the loader that @formeriphoneuser suggested, but with a similar result. (https://pastebin.com/ucMkEkeW). I also tried with the flag --memory="ufs" in case the device has UFS memory, but similar result.
But the good new is, I've just discovered a reliable way to avoid the boot loop after leaving EDL mode. So to leave EDL mode, make sure any running commands have ended, unplug the device from the computer, and press and hold the eink button (on the left of the phone), volume-up, and power button. Keep them all pressed until the first vibration (after about 15 seconds or so, then release the power button only). Keep the other two pressed while the phone boots, and even while you're entering your 6 digit pin code. When you see the main screen you can release the buttons and your phone shouldn't enter the boot loop. I have no idea how much of that is necessary, but something in there works for me.
I've added an Issue to the github repo for the EDL tool I'm using. Other than that, I think I've hit a brick wall and won't be able to do any more for now. Unless anyone knows how to check that the firehose file is correct for my device, and update it if it's not. Hopefully Hisense will release the stock firmware, or send us an OTA update or something.
Click to expand...
Click to collapse
Also, looking at your pastebins, It seems you are running Ubuntu via a Parallels Virtual Machine. I would suggest using the LiveDVD from the EDL github repo and running it on bare metal to rule out any system related issues. Given that the pastebins show errors relating to libusb1.py, there is a good chance your issues are due to the emulated USB controller provided by Parallels.
matteqa said:
Also, looking at your pastebins, It seems you are running Ubuntu via a Parallels Virtual Machine. I would suggest using the LiveDVD from the EDL github repo and running it on bare metal to rule out any system related issues. Given that the pastebins show errors relating to libusb1.py, there is a good chance your issues are due to the emulated USB controller provided by Parallels.
Click to expand...
Click to collapse
I tried booting the liveDVD from the repo in Parallels, but it wouldn't boot, saying something like Ubuntu was missing. But I'll try it as a bootable USD drive. I won't be able to do it until next weekend at the earliest, but I'll report back when I've tried that method. Thanks for your suggestions!
So I bought a USB drive and flashed the liveDVD from the repo to it, but my only computers are Macs and will recognise the USB drive as bootable - I've tried Fat32 / HFS+ file systems, made sure it's a GUID partition table, and used both Etcher GUI and terminal's `dd` to burn the image to the drive, but still the USB never shows up in the startup utility. Anyway, I've hit a roadblock on this for now - I think my next options are to either pick up a cheap Windows laptop, or put a bounty out for boot.img (or preferably full root! )
RunnyYolk said:
So I bought a USB drive and flashed the liveDVD from the repo to it, but my only computers are Macs and will recognise the USB drive as bootable - I've tried Fat32 / HFS+ file systems, made sure it's a GUID partition table, and used both Etcher GUI and terminal's `dd` to burn the image to the drive, but still the USB never shows up in the startup utility. Anyway, I've hit a roadblock on this for now - I think my next options are to either pick up a cheap Windows laptop, or put a bounty out for boot.img (or preferably full root! )
Click to expand...
Click to collapse
Just checking, have you tried the macOS version of the EDL tool? All of your pastebins are from ubuntu parallels, however there is also a native macOS version in the github repo.
matteqa said:
Just checking, have you tried the macOS version of the EDL tool? All of your pastebins are from ubuntu parallels, however there is also a native macOS version in the github repo.
Click to expand...
Click to collapse
Ah, that's a good call! I did try the native Mac version on one machine, but it wasn't able to find libusb library, so I started using parallels / ubuntu, and then basically forgot that the native mac version existed! So thanks for the reminder - I tried it yesterday on an older Mac, and the native EDL client seems to be working properly. Unfortunately I think the firehose / loader files I have aren't correct. When I ran it with a loader I get sahara - [LIB]: Unexpected error on uploading, maybe signature of loader wasn't accepted ?
type object 'req' has no attribute 'image_id', and then I tried running it without any loader and got sahara - [LIB]: Couldn't find a loader for given hwid and pkhash (0014d0e100430000_56d3f3c74a52172b_[FHPRG/ENPRG].bin) :(.
So I guess we need the correct loader for the A9. I'm pretty clueless about how these files come to exist in the first place (do they have to come from the manufacturer, or can we build them ourselves?), but anyway I'll open a new issue on Github and see if the developer of the client can help.
For completeness' sake, here are logs from each attempt at reading boot_a (I tried three different loaders, each one with and without --skipresponse, and then once with no loader).
https://pastebin.com/AA9d5Tdh
https://pastebin.com/gXHS9pYN
https://pastebin.com/6e5FeWDc
https://pastebin.com/8dGWFNau
https://pastebin.com/iTd8ZsVH
https://pastebin.com/2esPvxyX
https://pastebin.com/Pvz9YxfE
https://pastebin.com/D47mPKt6
*edit* This is the issue on Github: https://github.com/bkerler/edl/issues/303
RunnyYolk said:
Ah, that's a good call! I did try the native Mac version on one machine, but it wasn't able to find libusb library, so I started using parallels / ubuntu, and then basically forgot that the native mac version existed! So thanks for the reminder - I tried it yesterday on an older Mac, and the native EDL client seems to be working properly. Unfortunately I think the firehose / loader files I have aren't correct. When I ran it with a loader I get sahara - [LIB]: Unexpected error on uploading, maybe signature of loader wasn't accepted ?
type object 'req' has no attribute 'image_id', and then I tried running it without any loader and got sahara - [LIB]: Couldn't find a loader for given hwid and pkhash (0014d0e100430000_56d3f3c74a52172b_[FHPRG/ENPRG].bin) :(.
So I guess we need the correct loader for the A9. I'm pretty clueless about how these files come to exist in the first place (do they have to come from the manufacturer, or can we build them ourselves?), but anyway I'll open a new issue on Github and see if the developer of the client can help.
For completeness' sake, here are logs from each attempt at reading boot_a (I tried three different loaders, each one with and without --skipresponse, and then once with no loader).
https://pastebin.com/AA9d5Tdh
https://pastebin.com/gXHS9pYN
https://pastebin.com/6e5FeWDc
https://pastebin.com/8dGWFNau
https://pastebin.com/iTd8ZsVH
https://pastebin.com/2esPvxyX
https://pastebin.com/Pvz9YxfE
https://pastebin.com/D47mPKt6
*edit* This is the issue on Github: https://github.com/bkerler/edl/issues/303
Click to expand...
Click to collapse
Have you tried to read from "boot" instead of "boot_a". Maybe hisense isn't using A/B partitions since they don't care about google play certification. Also, have you tried using --memory=ufs.
Otherwise, it may be that the loader has a custom signature. As far as I know, the loader is proprietary and you have to get it from the manufacturer.
@RunnyYolk
I've also just found a patched version of a SDM662 loader on another forum that might work.
I've reuploaded it here: https://cloud.matteqa.com/index.php/s/M6MxgPFDsYwaKP6
matteqa said:
@RunnyYolk
I've also just found a patched version of a SDM662 loader on another forum that might work.
I've reuploaded it here: https://cloud.matteqa.com/index.php/s/M6MxgPFDsYwaKP6
Click to expand...
Click to collapse
Thanks! I tried this loader, and also the --memory=ufs flag / "boot" alternatives as you suggested, but had the same errors as before. I'm pretty sure I saw boot_a and boot_b directories somewhere when I was exploring the filesystem in adb shell, but I'll double check again when I have time.
Are there any other avenues I could try to root this device? I wonder if there's any point trying to boot TWRP from an A7? Am I right in thinking I can `fastboot boot recover.img` without risk of bricking the phone? (Ie just booting rather than flashing.)... Maybe I'm clutching at straws...