Related
Introduction
Some of you will, remember lets save some bricks? Well, it's taken a long time to perfect this on the i9000, which is ironic because this is where it started, but we finally have a way! You can perform this mod on a bricked device and resurrect it, or you can apply it as a protective measure.
The way this works is we change the OM value in the processor by modifying an individual electronic binary signal. The signal we are interested in is xOM5. This line is normally grounded, causing the overall OM value to equal 0x9. When we bring this line high, the OM value becomes 0x29. This reverses the booting order and ensures you will always have boot from USB available before the device starts.
This is a better option than JTAG for resurrecting a device. How could it possibly be better then JTAG? Let's count the ways....
1. The only part required is a wire.
2. No shipping time.
3. No cost for a box to interface the computer.
4. Permanent.
5. Can be done as a preventive measure.
6. Gives the ability to test new Bootloaders temporarily.
7. Allows development of the entire system.
8. Removes worry about flashing and acts as a backup.
After performing this mod:
Remove the battery, replace the battery, plug in USB, your phone will connect to the computer via USB and await commands for 2 seconds. Otherwise it will pretty much act like a i9000. See the Special Instructions section.
Part 1: Hardware Modification
You will need:
1. Get someone who knows what they're doing with a soldering iron. If they don't know what flux is, then they don't know what they're doing.
2. soldering iron - make sure it's sharp, if it's not sharp, then sharpen it, flux it and retin it.
3. flux
4. solder
5. tweezers
6. A relay (for the wire contained within)
getting started:
You will need a very small peice of wire. Tear apart the relay unravel the coil within and grab about 5cm~ of wire. The fact that it comes from a relay is important because relays generally have very small wire which are individually treated with a non-conductive coating.
Take the 5cm~ wire from the relay and tin the very edge of it. No more then 1/32". If you tin more then 1mm, cut off the excess. It is desirable to have a slight bit of excess solder on the tip of this wire.
1. Tear apart your device. Remove battery cover, battery, 6 screws, the back case and 4 connectors from the board.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. remove the EM shield from the board to expose the resistors
3. Replace the xOM5 resistor from the top to the bottom or remove the xOM5 resistor and connect either xOM5 center pad to either xOM3's or xOM0's center pads.
4. Reassemble the device
Special Instructions
This replaces the battery charging sequence for the first few seconds of being plugged in.
To turn on the device, and operate in normal mode, you must hold the power button for 5 seconds.
3 button Download mode works as usual, however you must not have the S5PC110 drivers installed on the computer. You can use your custom rom menu option, adb reboot download, or use a terminal to "reboot download". 301Kohm Factory Mode JIGs work as well, but you must press power to bypass the S5PC110 mode.
Part 2: Software Based Resurrection
Connexion2005 (Mobiltechvideos) perfomed the very first resurrection on this device based on a Google+ post I made with a picture of the xOM pins. Usually I post two separate posts, but since the software resurrection was already ready already, I decided to include it in this post. The tools used are the same as every other GalaxyS device. The resurrector must be run within 2 seconds of plugging in the USB cable. Thanks Connexion2005!
You Must have UnBrickable Mod applied to your device. If you're not sure, run this tool under Linux: http://forum.xda-developers.com/showthread.php?t=1257434
This currently only works for Linux based computers or Windows based computers with proper drivers installed, with a Linux Virtual Machine, Get Ubuntu here: http://www.ubuntu.com , Get Virtualbox Here: http://www.virtualbox.org/wiki/Downloads
You must have Java installed on your computer: http://www.java.com/en/download/
Unbricking:
1. Apply UnBrickable Mod to your device: see Hardware Modification section
2. Run ModeDetect and plug in your i9000. (Not a requirment, but helpful)
When you see this image you are in S5PC110 SEC SoC mode. When you see this mode you must proceed to step 3.
If it will only show this image, then you have not performed the modification correctly, or you have a hardware problem.
If it shows this, regardless of what's on your screen, you're in download mode:
3. Run UnBrickable Resurrector: Get it from the SVN repository here: http://code.google.com/p/hummingbird-hibl/downloads/list This will only work on linux. Install Linux or dual boot if you have windows.
On this device the resurrector must be run within 2 seconds of plugging in the device. So you must be quick. I find it's easiest to click Download Mode, type a password, plug in the device, then press enter.
4. Run Heimdall One-Click to flash firmware on your device. http://files.teamkomin.com/i9000SGS/i9000-XXJVT-One-Click.jar
5. repeat steps 2, 3 and 4 with bootloader flashing enabled (Heimdall One-Click has a safety mechanism which requires you to flash once before flashing bootloaders).
Conclusion
Congratulations. You now have a device which works like a KIT-S5PC110 with an OM Value of 29. Now get to developing some serious custom software.
reading material
Creating your own Samsung Bootloaders: http://forum.xda-developers.com/showthread.php?t=1233273
KIT-S5PC110 manual: http://www.mediafire.com/?94krzvvxksvmuxh
how to use DNW: http://tinyurl.com/dnw-how-to
Flash using openOCD and DNW: http://www.arm9board.net/wiki/index.php?title=Flash_using_OpenOCD_and_DNW
another DNW example: http://www.boardset.com/products/mv6410.php
ODroid dev center: http://dev.odroid.com/projects/uboot/wiki/#s-7.2
drivers and utilities
This will be an ever expanding list
Windows Drivers http://forum.xda-developers.com/attachment.php?attachmentid=678937&d=1312590673
Windows Download Tool DNW: http://forum.xda-developers.com/attachment.php?attachmentid=678938&d=1312590673
Windows Command Line tool: http://forum.xda-developers.com/showpost.php?p=17202523&postcount=27
Linux DNW Utility: http://dev.odroid.com/projects/uboot/wiki/#s-7.2
Linux ModeDetect tool: http://code.google.com/p/hummingbird-hibl/downloads/list
Linux Automated UnBricker:http://code.google.com/p/hummingbird-hibl/downloads/list
firmware
Bootloader Hello World by Rebellos http://forum.xda-developers.com/attachment.php?attachmentid=698077&d=1314105521
UnBrick tool http://forum.xda-developers.com/showthread.php?t=1242466
Such an important piece of information we have here!
Congrats Adam and all the team, will write about this!!
That's seems to be our alma mater of UB Mods. The first of whole family finally got UnBrickable.
Okay, so, what is Hummingbird Interceptor Boot Loader (HIBL)?
Basically: It allows to load any amount of data (limited by size of RAM block, the biggest one single block available is 256MB) through USB connection with PC under any specified address into memory and then execute it.
Technically: It does consist of 2 pieces fused together - BL1_stage1 and BL1_stage2.
Each stage starts from 16bytes (4 ARM WORDs) of secure boot header. In stage1 these are mandatory, in stage2 they can be random (nulled them in my code), so EntryPoint of each stage does start at its 0x10 offset.
BL1_stage1, loaded under 0xD0020000 address, is short code, digitally signed by Samsung. It has been released to break "Chain of Trust" and alter Secure Boot into Non-Secure Boot process. Literally stage1 just do some compare operations and then jumpout to BL1_stage2. (Yes, I also see no point of releasing hardware secured CPU version together with software which is bypassing it's security)
BL1_stage2, must be placed at 0xD0022000 address (it's fused together with stage1 into HIBL, so it's at 0x2000 offset of HIBL.bin) it is unsigned because Secure Boot Context, prepared by iROM (BL0) has been already ignored by stage1.
Its FASM_ARM sourcecode:
http://code.google.com/p/hummingbir...unk/HummingBirdInterceptorBootloader/HIBL.ASM
This is where the code start real work, it does begin with standard ARM core jump vector table (just to keep stick to standard, these aren't used anyway).
1. It does use I9000 BL1_stage2 functions (init_system) which I linked to it, these are used to init DMC controllers, as to this point code is executing in and working with very tiny, 96KB iRAM space, after calling this function it turns all 512MB of RAM available.
2. Make sure DMC is configured properly (write some value to address 0x40~~ memory space, then read it and compare with previously written)
3. Reinit iRAM heap to the BL0 initial state (to convince it USB dload mode haven't been called yet), by storing and restoring UART pointer only (to keep debug output flowing properly)
4. Call iROM usb_downloader function.
5. Read the address where downloaded data has been placed.
6. Jump into this address.
This, properly used provides similiar debug output (similiar, because its outdated testlog)
������������������������������������������������������������������������
Uart negotiation Error
----------------------------------------
Hummingbird Interceptor Boot Loader (HIBL) v1.0
Copyright (C) Rebellos 2011
----------------------------------------
Calling IBL Stage2
DONE!
Testing BL3 area
DONE!
iRAM reinit
DONE!
Please prepare USB dltool with BL3
Starting download...
0x00000000
Desired BL3 EP: 0x40244000
Download complete, hold download mode key combination.
Starting BL3...
//OUTPUT BELOW IS COMING FROM SBL
Set cpu clk. from 400MHz to 800MHz.
IROM e-fused - Non Secure Boot Version.
Click to expand...
Click to collapse
It opens infinite capabilities. Instead of SBL to unbrick, Uboot can be loaded, or any armlinux kernel. It's all up to you - XDA Developers.
is the start of porting another SO's to our i9000, like bada or wp?
Yeeee! Thank u very much Adam!
I hope i can get soon again another SGS!!
Inviato dal mio GT-I9100 usando Tapatalk
lpalvaro said:
is the start of porting another SO's to our i9000, like bada or wp?
Click to expand...
Click to collapse
I hope so, WP7.5 would be really fast running in a SGS!
Enviado desde mi GT-I9000 usando Tapatalk
lpalvaro said:
is the start of porting another SO's to our i9000, like bada or wp?
Click to expand...
Click to collapse
Noone will spend hundreds or even thousands of hours to port closed source system. So no. This is not start, this just opens such possibility.
Very impressive work, thanks a lot for this !
Rebellos said:
Noone will spend hundreds or even thousands of hours to port closed source system. So no. This is not start, this just opens such possibility.
Click to expand...
Click to collapse
That's true...but porting full Debian with LXDE and Kernel 3.1 would be good
Is one of my first project as soon as i get an unbrickable device...
Inviato dal mio GT-I9100 usando Tapatalk
The big brother has UBM! Yay
Sent from my SGH-I897 using xda premium
It's a Good mod, but I don't think I'll play with my phones hardware. It's unbrickable only when we don't play with bootloader and I don't.
Sent from my GT-I9000 using xda premium
simone201 said:
That's true...but porting full Debian with LXDE and Kernel 3.1 would be good
Is one of my first project as soon as i get an unbrickable device...
Inviato dal mio GT-I9100 usando Tapatalk
Click to expand...
Click to collapse
I sent you a PM yesterday. You never responded. You came in second in the Fascinate contest. Send me a PM and I'll do UBM for your device.
AdamOutler said:
I sent you a PM yesterday. You never responded. You came in second in the Fascinate contest. Send me a PM and I'll do UBM for your device.
Click to expand...
Click to collapse
Yeah sorry Adam, i haven't replied cuz i haven't got an SGS now (i have sold mine a month ago) so i cannot use your great offer now....
I am trying to search a bricked sgs to give it to you asap!
Thanks for all Adam!
Inviato dal mio GT-I9100 usando Tapatalk
Anyway, any idea if you can try to port the same mod to the SGS2 but it should be a completely different work....
It would be really good, as the work on I9100 is a lot!!
Inviato dal mio GT-I9100 usando Tapatalk
simone201 said:
Anyway, any idea if you can try to port the same mod to the SGS2 but it should be a completely different work....
It would be really good, as the work on I9100 is a lot!!
Inviato dal mio GT-I9100 usando Tapatalk
Click to expand...
Click to collapse
It would be a completely different task. Exynos Is a different processor. However, I know what needs to be done. I have the datasheets. Its a matter of locating the xOM pins, figuring out how they work, then rebellos can develop firmware and I can package a resurrector.
OMAP based devices like the Galaxy Nexus will be even easier.
There is no hope in sight for Qualcom devices like T-Mobile SGS2. All other SGS2 devices are ready. I just need one to work with.
AdamOutler said:
It would be a completely different task. Exynos Is a different processor. However, I know what needs to be done. I have the datasheets. Its a matter of locating the xOM pins, figuring out how they work, then rebellos can develop firmware and I can package a resurrector.
OMAP based devices like the Galaxy Nexus will be even easier.
There is no hope in sight for Qualcom devices like T-Mobile SGS2. All other SGS2 devices are ready. I just need one to work with.
Click to expand...
Click to collapse
Good to know!
I hope u can work on an I9100 soon as it would be much better to develop for a newer platform...
As soon as i brick my sgs2 i will give it to you! XD
As always, i really love your work Adam, i hope u can teach me something of ur knowledge! XD
Inviato dal mio GT-I9100 usando Tapatalk
thank you
This is one post i was waiting for for long time now,
thx Adam love your work
Wow... Great information! thank you!
Finally !
Adam, can this mod be performed by connecting the xOM pins only once and then flashing the HIBL ? I think we need to now develop something like MAGLDR for the SGS series. this will help greatly IMO. What do you think ??
Is it too difficult ? i wish i knew linux etc
EDIT: sorry my mistake I don't think it can be done
I go search a bricked sgs, this is just AWESOME FOR KERNEL developers.
Sent from my GT-I9100
Android 4.4 Reversing Camera Mirror With A10,A23,A33 CPU
These mirrors come in many different flavours now. At time of edit post A33 x5 quadcore is the latest with 16GB. This newer unit can be rooted with kingroot apk version. I find I lose root after reboot for some reason. I haven't found a firmware for this mirror version as of yet. For some reason my mirror does not have a wifi antenna attached so poor signal unless 4 meters line of sight. Please becareful as from experience from buying 3 mirrors now, there can be huge differences to build quality even thou they look the same.
I'm not updating this thread with RT01 firmware anymore. Please check Baidu link below
Also need this to load firmware to TF/microsd
PhoenixCard_V310_20130618.rar
To load new firm run Phoenixcard - Select image - Insert TF card/ Microsd - Choose burn (Try until magic) - Insert Tf Card into mirror and shutdown - After mirror firmware loaded you must format to normal or Tfcard will flash mirror again on reset
You may also find your firmware here. Let me know if you can't download it(use iPad to view)
http://pan.baidu.com/wap/share/home?uk=4026862827&third=0
Yfgo.apk - Radar program (you need mirror with radar function)
Yfgo.apk
Thx to nyinyiwale
How to get root access:
Download this settings.apk and run it! Thanks to Nick Nick
Setup.apk (A23)
Now you should have developer options - Enable usb debugging
Now install on windows machine http://pdanet.co/ for android
Then install kingo root http://www.kingoapp.com/android-root/download.htm
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Specifications
Processor - Allwinner A13 Cortex A8 1.2GHz Dual Core
Smart systems - Android 4.4 OS
Screen - 5.0 inch HD 5 point touch screen
Diplay resolution - 800X480 pixels
DDR - Built in 512MB DDR 3
Nand Flash - Built in 8GB (systems will occupy 1.72GB )
External storage - Support Maximum 64GB TF card(not included)
Image Sensor - 5.0 million pixel HD camera, 350 degree rotate front lens
Lens angle view - Front 140 degree +back 120 degree
Video Resolution - Front: 1920*1080(30f/s)/HD1280x720(30f/s) - Rear: 640X480 30f/s
Video format - MP4
Picture format - JPEG
Compression - H.264
Speaker - Built in
MIC - Built in
External I/O port
1*USB 2.0
1*TF card port:
1* GPS port
1*AV IN (support auto reverse function)
Dimensions - Main product size: 310x90x20mm (L x W x D)
Just got this item off eBay. Url removed
Screen looks great. Touch screen works a treat. Nice and bright and good angle also.
There are a few things different listed that the seller on eBay has not listed correct.
It comes with android 4.4.2 And not 4.0
Has a A23 dual core and not A10
Kernel version 3.4.39
And it has a battery which would last a couple of days with no use - make sure you turn off wifi when not on power
This is a true android with some very basic functions missing. Starting it has no google services. So no google play store, no where to login to google account in settings. The launcher looks good(you can't change it) expect there is no access to app list. You can click on navi button - which holds no navigation software funny enough. Once inside the navi button you can hold on the screen and then it brings you up a app selection screen giving you option to add icons(still no gps map softwares)
Once connected to Internet apps start updating when you open them which is pretty cool.. There is an update option under andriod version screen which fails to find any update with an error(searches Internet for update or you can local upload file).
Overall I'm pretty impressed with this device and its speed. I was able to install google maps by browser. But once I closed it I could not open it again cause no icon to click on. Google maps ran a little bit sluggish but was acceptable. I'm now chasing the seller for a solution to google play store as the play store ask won't open after installing.
I was able to side load apps quite easily with the browser. Seems most work if the don't depend on play store or accounts being setup in google settings.
Synic gps software won't work as it wants to use playstore to download more files.
Es explorer works fine.
I don't think I will be able to get root access as there is no developer menu, but after clicking on firmware build number says you are already a developer
i have this one and have Google playstore, i have installed nova launcher without problem, all is fine
Hi, is it model rt01?
Do you have the same firmware 4.4.2 and specs?
Does it have an option to add google account inside android OS?
As mentioned above no google account in my OS which means no history in google maps. Very frustrating.
Could I also grab the seller as I my have to purchase a new one
Thank you if you can help
hello, i bought mine to this seller from Aliexpress, received in 8 days via DHL
http://fr.aliexpress.com/item/5-inch-Android-Mirror-Monitor-GPS-1080P-Digital-Video-Recorder-Rear-view-Camera/2021095296.html
The item has exactly the spécifications as described from top of topic and is a rt01 model, else allwinner A23 Inside, android 4.4.2 KitKat Inside
i have in native Google playstore and i have created my account without problem as soon as i powered up for the firs time the mirror
best regards
Thanks for your help appreciated.
Need to try a scab a firmware update as my seller refuses to speak with me now.
Might just buy what you got I think.
you can try to communicate via aliexpress with the store, seller is Mr wilson cao and ask him for a firmware, it's a pleasant person who respond to me very fast, also after my purchase for details. Try to say you're a friend of me (Superboost) and have same miror and you want the same OS, give a try, good luck.
---------- Post added at 06:38 PM ---------- Previous post was at 06:32 PM ----------
at this time i'm trying to root for install some progs. Framaroot = KO, kingroot not able to connect at his cloud for exploit. At this time not result. If i can, also put a twrp or other and save firmware and tranfer to you? Have an idea of rooting ?
I have seen a update.zip file for root on the net. I was thinking doing it that way.
I'll give it another go as I was more focused on gapps.zip before.
Do you have development option to activate usb debugging? I don't have this option, so it makes it hard for me.
That's why I suggested an update.zip method.
If you have usb debugging (lucky you) then try http://www.shuame.com/en/root/
Also sent a msg to your seller. I think he would have to be very nice to give time for nothing being a business man
I have not the "usb debugging option" and no more the menu security for the possibility to "accept unknown sources" option. I think it will be impossible to root the item.....
tell me if you have a response from seller, have a good day
I was going to try to enable usb debugging by a terminal command but gave up after I couldn't install gapps
Try this maybe
http://forum.xda-developers.com/showthread.php?t=893434
hello, i have installed usb drivers of the mirror (hold down volume button and plug USB) and found an unknown device, i downloaded livesuit pack V1.9 and in the usb directory, it found the driver.
Now i can lauch livesuit but it wait for an .img image file for flash.... that's all for this time.... perhaps a way for future rooting?, have a good day
Your seller is very nice.
Thank you also.. Now have to work out how to install
This is a link I found on google
http://pan.baidu.com/wap/link?uk=4026862827&shareid=3212962299&third=0
Link from your seller
http://en.mail.qq.com/cgi-bin/ftnEx...1e4459433274&t=exs_ftn_download&code=231c0681
hello, happy for you, i expect you can flash this firmware and having opérationnal Google on it.
This seller is very nice, i put it a 5+++++ stars on aliexpress
have a good day
It's a puzzle..
You have an img file.. And Phoenixcard..
Putting in sdcard and selecting startup it puts the android OS on the sdcard and you boot from that so you can test the image I suppose.
Could not see any google account. Also I have alarm next to the radio icon. When I put this one on I got the browser instead.
Can I ask under settings about tablet is your build number 20150410 ?
in the info i have : rt01-eng 4.2.2 KVT49L 20150410 test-keys
It's seem that is the same build than downloaded
perhaps puting applications in "download" folder of the program will put them on the image for flashing ?
Thank you so much. You are a legend.
Its as I figured.
running the phoniexcard program you select Startup to run off sdcard.. which is way slow.
So I took the plunge and hit production and it setup my sdcard which in turn updated my unit.
Now its usable and I cant thank you enough!
have you all you want in ? Google account possible? the next challenge : rooting...
---------- Post added at 01:24 PM ---------- Previous post was at 12:45 PM ----------
Because it's difficult to find this firmware, i put it on a Mega download
https://mega.co.nz/#!ZEwxzAyJ!HzowmA3-bVbcCdZpY7tHsQ5sV2kLQ8d6lwX6Y4Q0IXY
It include the program Phoenixcard for generate the bootable SD card for update firmware
for someone else who search
Yes rooting is on the cards now...
Just enjoying play store for the moment..
Plus I've noticed a huge increase in speed.
Large improvement in firmware need to keep eye open for future releases
For those looking to use BCDEDIT on their phone, it seems that the restrictions preventing us from doing so exist in the SSH server implementation. If you install the Telnet server and execute BCDEDIT from there, it appears we can at least read the BCD store and enumerate parameters. I have not yet tried to make changes, I am not ready to do so yet. If anyone wants to give it a shot and report back go for it. Careful though, this could result in a brick.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://forum.xda-developers.com/windows-10-mobile/enable-bootshsvc-windows10mobile-t3455357
Thanks to naiple for uploading the files and method to get telnet running at boot
Thanks for sharing but do we have to copy every file in the zip? There are 20 files and it is hard to type.
Op says copy the exe and mui but there are a lot of them and he didn't mention which one we need.
BlueTR said:
Thanks for sharing but do we have to copy every file in the zip? There are 20 files and it is hard to type.
Op says copy the exe and mui but there are a lot of them and he didn't mention which one we need.
Click to expand...
Click to collapse
You will want the bootsh files (dll, mui), enable.bat, enable_bootsh.reg, ftpd.exe, gwptcp.exe,mwstartnet.exe,startup.bsc,telnetd.exe, and telnetlogon.exe to get JUST telnet and ftp working at boot. Follow naiples instructions to get this running.
You could optionally not use the files to run telnet and ftp at startup and just run them as needed, and this may be prudent since telnet does not require credentials to access. Once telnet and ftp are running, you'll have a much easier time copying files across over ftp, like telnet it does not have the same restrictions sftp does.
yochu20 said:
You will want the bootsh files (dll, mui), enable.bat, enable_bootsh.reg, ftpd.exe, gwptcp.exe,mwstartnet.exe,startup.bsc,telnetd.exe, and telnetlogon.exe to get JUST telnet and ftp working at boot. Follow naiples instructions to get this running.
You could optionally not use the files to run telnet and ftp at startup and just run them as needed, and this may be prudent since telnet does not require credentials to access. Once telnet and ftp are running, you'll have a much easier time copying files across over ftp, like telnet it does not have the same restrictions sftp does.
Click to expand...
Click to collapse
All of them are needed, just tried and got error.
I got it working but I'm afraid of trying to write
---------- Post added at 12:16 AM ---------- Previous post was at 12:01 AM ----------
Nope.
BlueTR said:
All of them are needed, just tried and got error.
I got it working but I'm afraid of trying to write
---------- Post added at 12:16 AM ---------- Previous post was at 12:01 AM ----------
Nope.
Click to expand...
Click to collapse
Yeah, I am nervous about writing to the store as well. If anyone decides to YOLO this, please post your results
I decided since I posted, I should give it a try. Seems some values can be edited, notice my bootmenupolicy changed in the new screen. Other values are protected by Secure Boot, which is expected. Good luck!
yochu20 said:
Yeah, I am nervous about writing to the store as well. If anyone decides to YOLO this, please post your results
Click to expand...
Click to collapse
I updated my post and added a screen shot. It says "The process cannot access the file because it is being used by another process"
BlueTR said:
I updated my post and added a screen shot. It says "The process cannot access the file because it is being used by another process"
Click to expand...
Click to collapse
I managed to get a value to update after I saw your updated post, posted the screen after the change. Try it again with the active store, that could be the difference.
I followed the directions by copying the files you said we'll need to their spots but when calling enable.dat I get reg is not recognized as an internal or external command
Edit:
I got it to work but now I get a 10048 error when trying to run ftpd.exe or telnet one
yochu20 said:
I managed to get a value to update after I saw your updated post, posted the screen after the change. Try it again with the active store, that could be the difference.
Click to expand...
Click to collapse
You are right. I did and it worked but there is a problem. I enabled boot menu but I don't have a camera button
If I press the volume up key, phone goes into ffu mode. If I press the volume down key, exclamation mark appears. If I press power key it selects windows loader and disables countdown then just waits.
BlueTR said:
You are right. I did and it worked but there is a problem. I enabled boot menu but I don't have a camera button
If I press the volume up key, phone goes into ffu mode. If I press the volume down key, exclamation mark appears. If I press power key it selects windows loader and disables countdown then just waits.
Click to expand...
Click to collapse
What did you change?
Edit:
Finally got a telnet app to work on my android so here are all the commands for bcdedit :
http://imgur.com/RVQ4HJ2
http://imgur.com/d4ecch0
http://imgur.com/CaS6I6o
http://imgur.com/LosxJ6d
http://imgur.com/GScAoFg
http://imgur.com/Lz6JVby
Warning
Before you do something stupid with these commands I recommend you use a backup windows phone to test these out!! I'm not at fault if anything happens to your main phone
Hmm, @svaethier, what are you talking about (and who cares about your damn android screenshot here?!!)
BCDEdit is a very well documented program. If you not banned on google.com, try to search by yourself!
P.S. The very first link: https://technet.microsoft.com/en-us/library/cc709667(v=ws.10).aspx
P.P.S. Please don't tell me "you are rude and impolite"! Noobs some times are extremely annoying What I suppose to say? "Thank you for the unique info!" ?
sensboston said:
Hmm, @svaethier, what are you talking about (and who cares about your damn android screenshot here?!!)
BCDEdit is a very well documented program. If you not banned on google.com, try to search by yourself!
P.S. The very first link: https://technet.microsoft.com/en-us/library/cc709667(v=ws.10).aspx
P.P.S. Please don't tell me "you are rude and impolite"! Noobs some times are extremely annoying What I suppose to say? "Thank you for the unique info!" ?
Click to expand...
Click to collapse
Well excuse me for providing info to those who may want it without having to google stuff up. Yes you are actually being quite rude, if you have nothing nice to say then just keep your opinions to yourself thanks.
ninjaofbacon said:
What did you change?
Click to expand...
Click to collapse
bcdedit /set {bootmgr} displaybootmenu yes
bcdedit /timeout 15
What if we extract 8.1 ffu on a sd card, and add it to the bootloader menu?
Can we dualboot W10 and 8.1?
I don't think it's as simple as adding another ffu.
svaethier said:
I don't think it's as simple as adding another ffu.
Click to expand...
Click to collapse
I made a vhd file from ffu. It contains the whole WP8.1 system for RM-976 but I need an 8gb sd card since I don't have it I couldn't try.
I would help but I don't want to mess with boot options just yet.
svaethier said:
I would help but I don't want to mess with boot options just yet.
Click to expand...
Click to collapse
I want but I can't. I don't have a camera button so I can't make os selection.
Couldn't we just make the power button os selection somehow?
Is there a way to use this locally, or do I need to use telnet over ssh?
I thought i would start this thread, separate to the Jeep one as the Jeep thread is for the 8.4" uConnect and uses some different files to the 6.5" version.
The aim of the thread is to be able to gain some sort of 'root' access to the file system to be able to update the maps on the system. So far I know cm0002 and Leighm0 have done some great work with the 8.4" - Most of which we can use on the 6.5".....once we have access to the file system.
The problem we seem to be facing is finding a swdl.iso that is old enough to be modified for our 6.5" units.
Mission Accomplished.... mostly
Disclaimer: I can not be held responsible for any damages to your uConnect, Car or your hair falling out from running this modification.
That being said, if you do have a problem please contact me and I will see if I can help you fix it.
For all those people still on v17.07.46 or older uConnect 6.5 firmware I offer you a “jailbreak”, you can now update your maps to the latest versions (currently offering EU 2018Q3 / NA 2018Q1 in my pack). I have to warn you though, the process can take a lot of time!
For those of you who have updated your 6.5 uConnect to v17.35.41 or v18, I am still working on how to update those, FCA / Alfa changed the locks with that update!
For a Full EU / NA update, if you follow my instructions fully, it will take approx. 4hours during which time your uConnect must remain powered on. This time can be greatly reduced by only updating the country or countries you need, or if you are feeling brave, skipping Step 1.
Files / Items needed:
uConnect 6.5 running v17 or older firmware -Supporting Alfa, Fiat and Jeeps too!
At least 8gb USB Drive ***preferably with a flashing led light so you can see file access***
Files from
https://mega.nz/#F!kURhTCbJ!uJhKPMyGiESbvQSDb33CvQ
Stage 1 – Backup your files
Download:
1 Magic -Alfa pre UPD.zip -For Alfa
1 Magic -Fiat & Jeep pre UPD.zip -For Fiat / Jeep
2 Backup.zip
Process:
1. Download and expand “1 Magic -XXX.zip” and “2 Backup.zip”
2. Copy the content onto the root of the USB drive
3. Start car and let uConnect boot up (wait approx 5min for full boot up)
4. Plug in and WAIT, the uConnect will not appear to be doing anything but if you are using a USB with a light you should be able to see it flashing with file activity
5. After some time, in my case it took 1h25 to complete this stage, it should popup a window about there is a update that you MUST answer NO to
6. Pull USB, and power cycle the uConnect*
After that you now have a backup of all the system and map files we are going to change on your uConnect.
KEEP THEM SAFE!
Either use a second USB for stage 2, save the backup folder to your computer or if your like me and use a 16gb USB stick you can leave it where it is.
I have now uploaded copies of the official EU Map Packs from (A) 2013, 2015 and 2017, NA Map Packs (B) 2013, and ROW Map Packs (C) WIP that will function as a backup or official upgrade for anybody needing them, restoring your uConnect back to stock.
***If you have a newer set of Original Map files please contact me, and I can add them to the drive for all to benefit from***
Stage 2 – Modify your uConnect
Download:
1 Magic.zip --You should already have this if you completed Stage 1
D EU Custom 2018 HNEU2018Q3v2.zip --Full EU
E NA Custom 2018 HNNA2018Q1.zip --Full North America
Or
D UK Custom 2018 HNUK2018Q3.zip --UK Only
D FR Custom 2018 HNFR2018Q3.zip --France Only
D DE Custom 2018 HNDE2018Q3.zip --Germany Only
D IT Custom 2018 HNIT2018Q3.zip --Italy Only
***There will be other country / State only update packs soon***
Or
A EU 2013 Original NQEU2012Q4.zip --Stock 2013 Maps, Original EU Release
A EU Update 2017 HMEU2015Q4.zip --Newest Original Map files released 2017
B NA 2013 Original NQNA2013Q4.zip --Stock 2013 Maps, Original NA Release
Process:
1. Download and expand “1 Magic.zip” and “D XX Custom 2018 HN….zip”
2. Copy the content onto the root of the USB drive
3. Start car and let uConnect boot up (wait approx. 5min for full boot up)
4. Plug in and WAIT, the uConnect will not appear to be doing anything but if you are using a USB with a light you should be able to see it flashing with file activity
5. After some time, depending on file used - If country / State only pack approx. 15min if full EU then approx. 2h, it should popup a window about there is a update that you MUST answer NO
6. Pull USB, and power cycle the uConnect*
If all gone well you will now have a uConnect 6.5 with updated maps!
As I am sure you can understand, there are still some little bugs to work out;
Problems:
UK postcodes > Only 5 digit search
Speedcams > Not working at all
Anything else… you tell me
Fixed:
UK TMC now working
France TMC working again
Italy TMC (paid version) working
There may be other little problems, but I am unable to test them, please let me know and I will look into them and try to fix!
*To Power cycle:
Either remove key, lock car, wait 10min, unlock and restart)
Or use engineers menu to reset the uConnect (Press Radio, More and Browse until menu pops up, scroll down to Reset Radio, answer YES)
I have uploaded some of the files, more to come.
The URL:
https://mega.nz/#F!kMYjlSKB!MCC6U1jclb0_aHc-NdocrA
If you have anything else to share please message me.
So I have found a uConnect 6.5 update file with version no 15.18.xx. Uploaded to the mega share - now to figure out how to modify it!
Jeep Renegade
Hi.
It is possible in jeep?
SquithyX said:
So I have found a uConnect 6.5 update file with version no 15.18.xx. Uploaded to the mega share - now to figure out how to modify it!
Click to expand...
Click to collapse
any news?
Update....
The 15.18.xx file is ROW and after modifying it to work for any model, I get a authentication error on inserting the USB!!!!
Hi SquithyX,
Any chance to get the link for "Updated EU Maps (2018q1) formatted for the 6.5"??
Many Thanks in advance!
Hi,
I have a working Alfa 6.5" headunit with 14.X.X sw still installed on it. Does anyone know if it is possible to extract fw directly through JTAG? What kind of harware is needed to do such operation?
Icaro03 said:
Hi SquithyX,
Any chance to get the link for "Updated EU Maps (2018q1) formatted for the 6.5"??
Many Thanks in advance!
Click to expand...
Click to collapse
I can upload for you if you want, however until I hack has been found to be able to modify the system, they will not work!
Sent from my CLT-L09 using Tapatalk
andri98 said:
Hi,
I have a working Alfa 6.5" headunit with 14.X.X sw still installed on it. Does anyone know if it is possible to extract fw directly through JTAG? What kind of harware is needed to do such operation?
Click to expand...
Click to collapse
Not sure on JTAG, but if it is a early uConnect (Alfa 940 unit with More button) then the NAND chip is on a separate daughter board, that can be removed from the system. If a interface could be made for that then full disk access could be got.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my CLT-L09 using Tapatalk
it would be great to see some development on this system
SquithyX said:
Not sure on JTAG, but if it is a early uConnect (Alfa 940 unit with More button) then the NAND chip is on a separate daughter board, that can be removed from the system. If a interface could be made for that then full disk access could be got. View attachment 4611300
Click to expand...
Click to collapse
I found a datasheet searching JY455
It seems to be an eMMC Memory from Micron (MTFC??GLGDM) with a build in MMC-Interface
Maybe it works like an MMC-Card.
If someone build an adapter for the white connector and USB, maybe we can read and write the flash like an MMC-Card on an USB reader.
for you may this works for really? have a look for "Alfa Romeo Giulietta UConnect Apple CarPlay & Android Auto retrofit Kit" in a search engine. it's very expensive but they say you can use touch screen as well to interaction when usually all the video interface i have found say not possbile, only video signal. what do you think about this?
So close, but broken lol
Success......kind of, I have managed to modify a swdl.iso to enable loading of different / modified files, on my Alfa 6.5 uConnect running 17.07.55.
The problem now is I seem to have completely broken navigation!!!!!!
I used the idea from post #216 in the Rooted Jeep Cherokee thread and modified the manifest.lua file in the swdl.iso (17.07.55) to load a script from usb before running the update.
Process goes power on uConnect > wait for it to boot up and display "Hands free ...." > insert USB and wait...it seems like its not doing anything but the script is running in the background > after some time the do you want to update question and answer No.
The fact that is has asked if you want to update is confirmation that the script has finished, however unfortunately there is no indication that the script is being run or how long it will take unless you have a usb with a flashing light, then it will show you something is happening at least! **my usb does not have a flashing light
I tested it with a splash screen update.... that worked perfectly, so no more boring Alfa Romeo logo on silver background for me at start up, I then pushed the modified NaviServer2, nav.sh and navRestart.sh files and rebooted.... new splash screen working perfectly but on pressing Nav button I just end up on a screen saying "Activating Navigation"
I am in the process of uploading the modified files to the mega share if anybody whats to have a look or are feeling brave
Navigation now fixed! working on making a 2018q2 map pack for it now.
SquithyX said:
Navigation now fixed! working on making a 2018q2 map pack for it now.
Click to expand...
Click to collapse
Really????' you are the MAN! could you please share everything you have used and step by step? do you think even with firmware 18 installed is possible updating maps?
thanks
Ok, here is a test image (working with v17 and earlier.... unknown for v18).
https://mega.nz/#!IUZDQATI!o1OBd8qbA...mQ5lunDb0opDvs
For anybody wanting to try it, and let me know the outcome.
The script I have included will:
Backup your MAPS license files to the USB
Backup your original Alfa Splash Screen to the USB
Copy a dbver file to the USB, that should contain information about your version of MAPS installed
Push the modified Splash screen and set its properties on the uConnect
Steps:
1. Download and expand
2. Copy onto USB drive (at least 4gb) ***preferably with a flashing led light so you can see file access***
3. Start car and let uConnect boot up (wait approx 5min for full boot up)
4. Plug in and hope
5. After some time it should popup a window about there is a update (with v17) that you answer NO to. With v18 i dont know what it will do, it may popup a window saying newer version installed, Error or maybe not do anything at all.
If that is the case use the led on the usb to make sure no file access is going on and then maybe wait 5 min extra, just to make sure.
6. Pull usb, and power cycle the uConnect - either power off the car (lock car, wait 5min, unlock and restart) or use engineers menu to reset the uConnect
7. Watch it boot....the boot image will be different if success!!!!! (there will also be some new files on the usb)
It is very important NOT to let it run the update, if it offers
I am in the process of uploading my work to my mega share,
I am currently running 2018Q3 UK maps in my Alfa with WORKING tmc. Still trying to sort the speedcams and full postcode search though - they dont work....yet!
SquithyX said:
I am in the process of uploading my work to my mega share,
I am currently running 2018Q3 UK maps in my Alfa with WORKING tmc. Still trying to sort the speedcams and full postcode search though - they dont work....yet!
Click to expand...
Click to collapse
did you modify the swdl.iso? or just the script.lua?
sofro1988 said:
did you modify the swdl.iso? or just the script.lua?
Click to expand...
Click to collapse
I have used a modified 17.07.55 swdl.iso with a script.lua - if you download the test above it contains some of the modified files. The rest are currently being uploaded / are already available online.
I have done a very quick video of progress with the uConnect here:
https://youtu.be/ed0O-xXNHdg
Just learned about GIS. Still using a Galaxy S4 w/Lineage, but am a huge fan of eink everything and impulse pre-ordered this new black and white phone from new and unknown Chinese vendor. Alleged to ship in August.
Assumed I was just going to use it off line as an ebook reader (to replace my kobo mini), but GIS has given me hope that there is a chance for a (relatively) safe/unbloated life for this device beyond that.
I’m sure there will be some eink optimization in the official ROM, but am less concerned about that than I am mysterious Chinese software.
Would love to hear anyone’s thoughts. I am more than happy to contribute to the cost of a Getting a test device in capable hands if necessary.
As a privacy enthusiast would also appreciate thoughts on hardware security on random Chinese phone as well. This is the first time I’ve ever gone out on such a limb.
Kingrow K1 Specs
5.17-inch E Ink Carta display (1280 x 720 with 283 ppi).
Frontlight.
2.0GHz MediaTek Helio P23 (MT6763) octa-core processor.
16GB of storage space.
2GB of RAM.
MicroSD card slot with support up to 64GB.
3100 mAh battery.
8MP rear camera with LED flash and auto-focus.
Android 8.1 Oreo operating system.
Dual SIM.
USB-C port.
Dual speakers.
138 x 72 x 8.5mm.
Thanks in advance.
Just realized one particular hardware issue may be the front light (since screen is not backlit like an LCD) and the controls may not be identical to backlight controls. I hope it treats the screen brightness identically and that it won’t be an issue.
Bump. For this type of preocessor I’ve only seen one example of getting stock android running relatively easily, anybody have any insight on what I can expect in the attempt?
I waited with backing this project on Indiegogo, because of the lack of GMS. I hope that could be fixed through another rom. But I doubt there will be a big developer crowd for this device. Nevertheless its nice to see it here on XDA. Followed!
Hi, I just got my Kingrow K1 in the mail today. I've always wanted an e-ink smartphone for longer battery life + less distraction, so I'm pretty excited about this. Unfortunately, the preinstalled software looks rather clunky and, as you mention, it might include random Chinese bloat/spyware. I'm hoping somebody can root this thing and we can get a developer scene going for it.
Some of the work done for Barnes & Noble Nook devices might be relevant, as those are also e-ink devices running Android.
For future reference, here's a list of everything installed on the stock ROM. I'm still trying to sort out what it all is, I think all the MTK* stuff are alternatives to missing Google packages provided by MediaTek.
$ pm list packages -f
package:/system/priv-app/FMRadio/FMRadio.apk=com.android.fmradio
package:/system/app/Gba/Gba.apk=com.mediatek.gba
package:/system/priv-app/ImsService/ImsService.apk=com.mediatek.ims
package:/system/plugin/PrivacyProtectionLock/PrivacyProtectionLock.apk=com.mediatek.ppl
package:/system/priv-app/CtsShimPrivPrebuilt/CtsShimPrivPrebuilt.apk=com.android.cts.priv.ctsshim
package:/system/app/Uicc2Terminal/Uicc2Terminal.apk=org.simalliance.openmobileapi.uicc2terminal
package:/system/priv-app/MtkTelephonyProvider/MtkTelephonyProvider.apk=com.android.providers.telephony
package:/system/app/Camera/Camera.apk=com.mediatek.camera
package:/system/priv-app/MtkCalendarProvider/MtkCalendarProvider.apk=com.android.providers.calendar
package:/system/priv-app/MtkMediaProvider/MtkMediaProvider.apk=com.android.providers.media
package:/vendor/app/LPPeService/LPPeService.apk=com.mediatek.location.lppe.main
package:/system/priv-app/WallpaperCropper/WallpaperCropper.apk=com.android.wallpapercropper
package:/vendor/app/SchedulePowerOnOff/SchedulePowerOnOff.apk=com.mediatek.schpwronoff
package:/system/app/Protips/Protips.apk=com.android.protips
package:/system/app/SmartcardService/SmartcardService.apk=org.simalliance.openmobileapi.service
package:/system/priv-app/MtkDocumentsUI/MtkDocumentsUI.apk=com.android.documentsui
package:/vendor/overlay/framework-res__auto_generated_rro.apk=android.auto_generated_rro__
package:/system/priv-app/ExternalStorageProvider/ExternalStorageProvider.apk=com.android.externalstorage
package:/system/app/YGPS/YGPS.apk=com.mediatek.ygps
package:/system/priv-app/MtkSimProcessor/MtkSimProcessor.apk=com.mediatek.simprocessor
package:/system/app/HTMLViewer/HTMLViewer.apk=com.android.htmlviewer
package:/system/app/CompanionDeviceManager/CompanionDeviceManager.apk=com.android.companiondevicemanager
package:/system/app/QuickSearchBox/QuickSearchBox.apk=com.android.quicksearchbox
package:/system/priv-app/MtkMmsService/MtkMmsService.apk=com.android.mms.service
package:/system/priv-app/MtkDownloadProvider/MtkDownloadProvider.apk=com.android.providers.downloads
package:/system/app/EngineerMode/EngineerMode.apk=com.mediatek.engineermode
package:/system/priv-app/xxLauncher/xxLauncher.apk=com.android.xx.launcherink
package:/system/app/Omacp/Omacp.apk=com.mediatek.omacp
package:/system/app/MtkBrowser/MtkBrowser.apk=com.android.browser
package:/system/app/OP01SoundRecorder/OP01SoundRecorder.apk=com.android.soundrecorder
package:/system/priv-app/WfoService/WfoService.apk=com.mediatek.wfo.impl
package:/system/priv-app/DefaultContainerService/DefaultContainerService.apk=com.android.defcontainer
package:/system/app/RedStoneOta/RedStoneOta.apk=com.redstone.ota.ui
package:/system/app/MtkDownloadProviderUi/MtkDownloadProviderUi.apk=com.android.providers.downloads.ui
package:/system/app/PacProcessor/PacProcessor.apk=com.android.pacprocessor
package:/system/app/CertInstaller/CertInstaller.apk=com.android.certinstaller
package:/system/priv-app/MtkCarrierConfig/MtkCarrierConfig.apk=com.android.carrierconfig
package:/system/framework/framework-res.apk=android
package:/system/priv-app/MtkContacts/MtkContacts.apk=com.android.contacts
package:/vendor/app/EmCamera/EmCamera.apk=com.mediatek.emcamera
package:/system/app/EasterEgg/EasterEgg.apk=com.android.egg
package:/system/priv-app/MtkMms/MtkMms.apk=com.android.mms
package:/system/priv-app/MtpDocumentsProvider/MtpDocumentsProvider.apk=com.android.mtp
package:/system/app/NfcNci/NfcNci.apk=com.android.nfc
package:/system/priv-app/Stk1/Stk1.apk=com.android.stk
package:/system/priv-app/BackupRestoreConfirmation/BackupRestoreConfirmation.apk=com.android.backupconfirm
package:/system/plugin/PermissionControl/PermissionControl.apk=com.mediatek.security
package:/system/app/BtTool/BtTool.apk=com.mediatek.bluetooth.dtt
package:/system/priv-app/Provision/Provision.apk=com.android.provision
package:/system/priv-app/StatementService/StatementService.apk=com.android.statementservice
package:/system/app/MDMLSample/MDMLSample.apk=com.mediatek.mdmlsample
package:/system/app/MtkCalendar/MtkCalendar.apk=com.android.calendar
package:/system/app/DrmProvider/DrmProvider.apk=com.mediatek.providers.drm
package:/vendor/overlay/SysuiDarkTheme/SysuiDarkThemeOverlay.apk=com.android.systemui.theme.dark
package:/system/priv-app/MtkSettingsProvider/MtkSettingsProvider.apk=com.android.providers.settings
package:/system/priv-app/SharedStorageBackup/SharedStorageBackup.apk=com.android.sharedstoragebackup
package:/system/app/PrintSpooler/PrintSpooler.apk=com.android.printspooler
package:/system/app/Uicc1Terminal/Uicc1Terminal.apk=org.simalliance.openmobileapi.uicc1terminal
package:/system/app/BasicDreams/BasicDreams.apk=com.android.dreams.basic
package:/system/app/webview/webview.apk=com.android.webview
package:/system/priv-app/InputDevices/InputDevices.apk=com.android.inputdevices
package:/system/app/BuiltInPrintService/BuiltInPrintService.apk=com.android.bips
package:/system/framework/mediatek-res/mediatek-res.apk=com.mediatek
package:/vendor/app/AutoDialer/AutoDialer.apk=com.example
package:/system/priv-app/DuraSpeed/DuraSpeed.apk=com.mediatek.duraspeed
package:/system/priv-app/MusicFX/MusicFX.apk=com.android.musicfx
package:/system/app/ExtShared/ExtShared.apk=android.ext.shared
package:/system/priv-app/OneTimeInitializer/OneTimeInitializer.apk=com.android.onetimeinitializer
package:/vendor/app/NlpService/NlpService.apk=com.mediatek.nlpservice
package:/system/priv-app/MtkTelecom/MtkTelecom.apk=com.android.server.telecom
package:/system/app/KeyChain/KeyChain.apk=com.android.keychain
package:/system/app/PrintRecommendationService/PrintRecommendationService.apk=com.android.printservice.recommendation
package:/system/priv-app/MtkDialer/MtkDialer.apk=com.android.dialer
package:/system/app/MtkGallery2/MtkGallery2.apk=com.android.gallery3d
package:/system/app/GoogleTTS/GoogleTTS.apk=com.google.android.tts
package:/system/priv-app/ExtServices/ExtServices.apk=android.ext.services
package:/system/priv-app/CallLogBackup/CallLogBackup.apk=com.android.calllogbackup
package:/system/priv-app/MtkPackageInstaller/MtkPackageInstaller.apk=com.android.packageinstaller
package:/system/priv-app/ProxyHandler/ProxyHandler.apk=com.android.proxyhandler
package:/system/app/MtkLatinIME/MtkLatinIME.apk=com.android.inputmethod.latin
package:/system/priv-app/ManagedProvisioning/ManagedProvisioning.apk=com.android.managedprovisioning
package:/system/app/CalendarImporter/CalendarImporter.apk=com.mediatek.calendarimporter
package:/vendor/app/MTKThermalManager/MTKThermalManager.apk=com.mediatek.thermalmanager
package:/system/priv-app/CallRecorderService/CallRecorderService.apk=com.mediatek.callrecorder
package:/system/app/MtkWebView/MtkWebView.apk=com.mediatek.webview
package:/system/app/WAPPushManager/WAPPushManager.apk=com.android.smspush
package:/vendor/app/SimRecoveryTestTool/SimRecoveryTestTool.apk=com.mtk.telephony
package:/system/priv-app/Baidu_Location/Baidu_Location.apk=com.baidu.map.location
package:/system/priv-app/StorageManager/StorageManager.apk=com.android.storagemanager
package:/system/app/OpenWnn/OpenWnn.apk=jp.co.omronsoft.openwnn
package:/system/app/BookmarkProvider/BookmarkProvider.apk=com.android.bookmarkprovider
package:/system/priv-app/MtkSettings/MtkSettings.apk=com.android.settings
package:/system/app/MDMConfig/MDMConfig.apk=com.mediatek.mdmconfig
package:/system/app/ExactCalculator/ExactCalculator.apk=com.android.calculator2
package:/vendor/app/LocationEM2/LocationEM2.apk=com.mediatek.lbs.em2.ui
package:/system/app/CtsShimPrebuilt/CtsShimPrebuilt.apk=com.android.cts.ctsshim
package:/system/priv-app/VpnDialogs/VpnDialogs.apk=com.android.vpndialogs
package:/system/app/MtkEmail/MtkEmail.apk=com.android.email
package:/vendor/app/MusicBspPlus/MusicBspPlus.apk=com.android.music
package:/system/priv-app/MtkTeleService/MtkTeleService.apk=com.android.phone
package:/system/priv-app/Shell/Shell.apk=com.android.shell
package:/system/app/WallpaperBackup/WallpaperBackup.apk=com.android.wallpaperbackup
package:/system/priv-app/BlockedNumberProvider/BlockedNumberProvider.apk=com.android.providers.blockednumber
package:/system/app/UserDictionaryProvider/UserDictionaryProvider.apk=com.android.providers.userdictionary
package:/system/priv-app/MtkEmergencyInfo/MtkEmergencyInfo.apk=com.android.emergency
package:/system/priv-app/FusedLocation/FusedLocation.apk=com.android.location.fused
package:/system/app/FactoryTest/FactoryTest.apk=com.xthink.factorytest
package:/system/app/MtkDeskClock/MtkDeskClock.apk=com.android.deskclock
package:/system/priv-app/MtkSystemUI/MtkSystemUI.apk=com.android.systemui
package:/system/app/Exchange2/Exchange2.apk=com.android.exchange
package:/system/app/BluetoothMidiService/BluetoothMidiService.apk=com.android.bluetoothmidiservice
package:/system/app/MtkNlp/MtkNlp.apk=com.mediatek.location.mtknlp
package:/system/app/FileManager/FileManager.apk=com.mediatek.filemanager
package:/system/app/MTKLogger/MTKLogger.apk=com.mediatek.mtklogger
package:/system/app/SensorHub/SensorHub.apk=com.mediatek.sensorhub.ui
package:/system/app/MtkBluetooth/MtkBluetooth.apk=com.android.bluetooth
package:/system/app/MtkWallpaperPicker/MtkWallpaperPicker.apk=com.android.wallpaperpicker
package:/system/priv-app/MtkContactsProvider/MtkContactsProvider.apk=com.android.providers.contacts
package:/system/app/CaptivePortalLogin/CaptivePortalLogin.apk=com.android.captiveportallogin
package:/system/plugin/DataProtection/DataProtection.apk=com.mediatek.dataprotection
package:/vendor/app/WapiCertManager/WapiCertManager.apk=com.wapi.wapicertmanager
package:/system/app/kindlefc/kindlefc.apk=com.amazon.kindle
Click to expand...
Click to collapse
I've managed to get the device into fastboot mode. I'd like to flash a custom recovery like TWRP, but I don't know which one is compatible with this device. Any suggestions?
Bunyip123 said:
I've managed to get the device into fastboot mode. I'd like to flash a custom recovery like TWRP, but I don't know which one is compatible with this device. Any suggestions?
Click to expand...
Click to collapse
do you happen to have the stock firmware with the boot.IMG. i want to look at it and see if its similar to my device. i have a umidigi one max and it has the same chipset and it looks like alot of the same apps
th3d3ck3r said:
do you happen to have the stock firmware with the boot.IMG.
Click to expand...
Click to collapse
No, I don't have the stock firmware. If you can point me to some instructions, I'm happy to try to extract a copy of it and post it here.
Kingrow K1 doesn't let me log in to google services
Hi,
I'm not a developer, sorry for my lack of knowledgle, however I'm desparate to find a sollution, maybe you can help me here.
I've bought the Kingrow K1 only to find there's no way of signing in to google accounts, contacts, callendar etc. $%^&*()!~
I hope it's just a question of installing and configuring the missing pieces.
Can you please help me out?
Tom
Maybe flashing Gapps like on AOSP? ?
You could try flashing a gapps package like https://opengapps.org/ but I don't know if it will work without root.
Bunyip123 said:
You could try flashing a gapps package but I don't know if it will work without root.
Click to expand...
Click to collapse
Without TWRP
We even have no stock firmware. I see it's a first step to acquire it.
sandworm88 said:
Without TWRP
We even have no stock firmware. I see it's a first step to acquire it.
Click to expand...
Click to collapse
is it of any help the url that get called when a k1 fails to find a new OTA firmware?
It's using a server called
fota.redstone.net.cn
on the port 6100
and it's asking for service/request
_jet said:
is it of any help the url that get called when a k1 fails to find a new OTA firmware?
It's using a server called
fota.redstone.net.cn
on the port 6100
and it's asking for service/request
Click to expand...
Click to collapse
...i'm just asking, i don't know anything about how to retrieve (and keep) a firmware copy
Any updates on this? someone in Kingrow K1 eReader/Phone User Group on FB claims they got root:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello, I've worked on a MT6763 device before. You may be in luck because MTK devices have built-in flash mode you can access. This would mean you can dump partitions provided you locate their offsets (if you can get hands on a scatter file, that would help a lot). The flash mode also allows you to bypass any locked bootloader (though, you don't seem to face such issue, but nice to know it's possible) restrictions. You may also be able to dd the blocks and create a stock firmware dump for backup. A good chance TWRP can be ported without kernel sources by using a very similar device's port as a base and dropping your current recovery image's kernel and fstab values in it.
I do not own this device myself, but I am interested in any findings regarding this topic. Good luck.
EDIT:
_jet said:
...i'm just asking, i don't know anything about how to retrieve (and keep) a firmware copy
Click to expand...
Click to collapse
Can you tell me how your /dev/block structure looks like, (use ls). If you navigate deep enough, you will see "by-name" folder, you can then dd the "boot" partition as a boot.img file.
EDIT2:
Actually, I suggest just dd'ing your system partition to your PC. You can also flash GSIs using fastboot. By dd'ing your system partition, you essentially make a fallback in case the image fails.
Cernodile said:
Hello, I've worked on a MT6763 device before. You may be in luck because MTK devices have built-in flash mode you can access. This would mean you can dump partitions provided you locate their offsets (if you can get hands on a scatter file, that would help a lot). The flash mode also allows you to bypass any locked bootloader (though, you don't seem to face such issue, but nice to know it's possible) restrictions. You may also be able to dd the blocks and create a stock firmware dump for backup. A good chance TWRP can be ported without kernel sources by using a very similar device's port as a base and dropping your current recovery image's kernel and fstab values in it.
I do not own this device myself, but I am interested in any findings regarding this topic. Good luck.
EDIT:
Can you tell me how your /dev/block structure looks like, (use ls). If you navigate deep enough, you will see "by-name" folder, you can then dd the "boot" partition as a boot.img file.
EDIT2:
Actually, I suggest just dd'ing your system partition to your PC. You can also flash GSIs using fastboot. By dd'ing your system partition, you essentially make a fallback in case the image fails.
Click to expand...
Click to collapse
Thanks for you answer @Cernodile. I'm the guy Ti He who posted in the FB group.
I'm currently trying to port a TWRP to our device. First I did a full read with Miracle Box, so in case something goes wrong I can restore my device. I used a TWRP from Cubot King Kong 3 because it has the same SoC and GPU. I unpacked my stock recovery and the Cubot recovery and replaced files like recovery.img-kernel
recovery.img-kernel_offset
ramdisk/prop.default
ramdisk/init files
ramdisk/ueventd.rc
ramdisk/ect/recovery.fstab
I flashed the repacked recovery through fastboot and booted into TWRP. I assume that TWRP would have been booted, because I can do adb devices and see my phone in recovery. But the display only shows some black lines, so there must be something wrong. Do you have any idea where to look at? See attached the log from /cache/recovery/.
Regards - Timo
helnorsksvartmetall said:
Thanks for you answer @Cernodile
I'm currently trying to port a TWRP to our device. First I did a full read with Miracle Box, so in case something goes wrong I can restore my device. I used a TWRP from Cubot King Kong 3 because it has the same SoC and GPU. I unpacked my stock recovery and the Cubot recovery and replaced files like recovery.img-kernel
recovery.img-kernel_offset
ramdisk/prop.default
ramdisk/init files
ramdisk/ueventd.rc
ramdisk/ect/recovery.fstab
I flashed to repacked recovery through fastboot and booted into TWRP. I assume that TWRP would have been booted, because I can do adb devices and see my phone in recovery. But the display only shows some black lines, so there must be something wrong. Do you have any idea where to look at? See attached to log from /cache/recovery/.
Regards - Timo
Click to expand...
Click to collapse
That seems already quite promising! It seems like your device is trying to render some TWRP elements, perhaps you have wrong resolution set as suggested by "framebuffer: 3 (344 x 725)". What would assist me here greatly would be .prop files from stock and your TWRP port such as default.prop.
I also attached the Scatter file from my device on my last post.
See below the prop files from stock and port (Cubot King Row 3).
(I also tried with port TWRP from Umidigi One Max but with the same result)
helnorsksvartmetall said:
I also attached the Scatter file from my device on my last post.
See below the prop files from stock and port (Cubot King Row 3).
(I also tried with port TWRP from Umidigi One May but with the same result)
Click to expand...
Click to collapse
First inconsistencies I see:
This is in your stock, but not port.
Code:
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
dalvik.vm.isa.arm64.variant=cortex-a53
dalvik.vm.isa.arm64.features=default
dalvik.vm.isa.arm.variant=cortex-a53
Although, I don't think that is the cause. I'd keep looking for a device that has e ink patches for TWRP, you can use that as base, rebuild the similar device's TWRP and then do same port method.