Database Users

Unlocking Vibrant

Hi there,
I am pretty new with this stuff, as I just got this phone today. It came with Froyo2.2 so I unrooted it back to the original JFK.
It did not come with a sim card, so I do not have a sim inside the phone as of now. But I do have a bell sim that I will use after to put the unlock key in... Is that okay?
I Connected the vibrant through Mini Kies and the MTP application says its connected.
I just re rooted from J16 back to the original.
I have the 64 bit drivers installed.
When I try to run Generate Unlock Windows Script I get the following error message saying...
Copy nv_data.bin
*daemon not running. Starting it now *
*daemon started succesfully *
error: device not found
error unable to find file <.\nv_data.bin>
could not find C:\documents and settings\1\desktop\key\generateunlockwindows\nv_data.bin
Anyone know what this means?
Or know what to do in this situation?
I am not sure if I should try installing the 32bit drivers or what.

how did you downgrade the phone from android 2.2?
I just bought the phone through ebay with the OS already at 2.2, and the phone is locked to t-mobile. I've heard it is not possible to unlock it with the 2.2 update. Is that true?

molson24 said:
Hi there,
I am pretty new with this stuff, as I just got this phone today. It came with Froyo2.2 so I unrooted it back to the original JFK.
It did not come with a sim card, so I do not have a sim inside the phone as of now. But I do have a bell sim that I will use after to put the unlock key in... Is that okay?
I Connected the vibrant through Mini Kies and the MTP application says its connected.
I just re rooted from J16 back to the original.
I have the 64 bit drivers installed.
When I try to run Generate Unlock Windows Script I get the following error message saying...
Copy nv_data.bin
*daemon not running. Starting it now *
*daemon started succesfully *
error: device not found
error unable to find file <.\nv_data.bin>
could not find C:\documents and settings\1\desktop\key\generateunlockwindows\nv_data.bin
Anyone know what this means?
Or know what to do in this situation?
I am not sure if I should try installing the 32bit drivers or what.
Click to expand...
Click to collapse
Yup, having exact same problem. If you find a fix let me know.

Make sure your usb setting is on debug and you have all of the files for the unlock on your pc. You also need java installed.
That method worked for me from stock.

can someone answer my question?

mbison83 said:
how did you downgrade the phone from android 2.2?
I just bought the phone through ebay with the OS already at 2.2, and the phone is locked to t-mobile. I've heard it is not possible to unlock it with the 2.2 update. Is that true?
Click to expand...
Click to collapse
I don't know whether the unlock methods work with Froyo but you can download a 2.1 stock Odin in the forum.

pvspencer22 said:
I don't know whether the unlock methods work with Froyo but you can download a 2.1 stock Odin in the forum.
Click to expand...
Click to collapse
where can i get it at and how do i do the rollback?

mbison83 said:
can someone answer my question?
Click to expand...
Click to collapse
...... please?

koooba said:
...... please?
Click to expand...
Click to collapse
very funny.

mbison83 said:
very funny.
Click to expand...
Click to collapse
Wasn't meant to be. Usually please and thanks goes a long way when asking for something. Shows appreciation.

^ Hence the THANKS button.

koooba said:
Wasn't meant to be. Usually please and thanks goes a long way when asking for something. Shows appreciation.
Click to expand...
Click to collapse
it also shows sarcasm and in this case thats what is seems like.

Read the stickies in the forum. If you can't figure it out ill grab the links tonight.

For the unlock this worked for me.
pvspencer22 said:
The windows tool worked for me from stock.
It doesn't generate a code though you input one.
Edit: link
http://forum.xda-developers.com/showthread.php?t=822008&page=11
Scroll down for instructions.
Click to expand...
Click to collapse
For going to stock. (From the general stickie)
draikz said:
Fixing so-called "Bricks"/Odin Errors
This guide is open to contribution/editing/correcting
-----------------------------------------------------------------------------------------------------
BOOT CYCLE
This is where you get the annoying Samsung Screen/Galaxy S screen.
DOWNLOAD REQUIRED (CREDITS TO JUSTANOTHERCROWD):
1. Get into Download Mode (WITH THE PHONE PLUGGED IN) by following the steps below
*Turn off the phone until you get to the charging battery screen (keep in mind, your phone is currently PLUGGED IN)
*Press volume up and down, and power all at once.
*As soon as the screen turns black, release your power button.
2. Unplug phone from USB
3. Open Odin (in Administrator if you're running W7 or Vista), try one of the ones I attached to this post, at least one of them is bound to work, some don't work for me, but works for others, some doesn't work for others, but works for me, whatever floats your boat
4. Load in the files into Odin that you have downloaded from above Just load in the files corresponding to the text field.
DO NOT CHECK REPARTITION.
5. Plug in your phone with the DL mode
6. Click start and wait for the magic
-----------------------------------------------------------------------------------------------------
NO-BOOT PHONES
This is where your phone does NOT turn on, no combo of buttons works and power button does nothing.
DO THIS ONLY WHEN YOU PLUG IN YOUR PHONE AND NOTHING SHOWS UP ON THE SCREEN!!! If else, follow the steps from above.
This method is basically same as above, EXCEPT the way you get into Download Mode as your phone is HARD BROKEN.
1. Download all the files required in the "BOOT CYCLE" section of this post.
2. Remove everything from your phone (SD card, sim, battery).
3. Plug your phone into your computer WITHOUT the battery, as you have already taken it out in the last step.
4. Press and HOLD vol. up and vol. down.
5. As you are HOLDING these buttons, reattach your battery.
6. You should be in Download Mode.
7. Unplug phone from USB
8. Follow steps 4-8 from the "BOOT CYCLE" section.
Troubleshooting:
-Odin stuck at some random process?
*Switch to another odin
*Make sure you did NOT check repartition, if you did, just repeat all the steps over again, except for the downloading parts, obviously.
-Phone not responsive?
*Try "NO-BOOT PHONES"section of this guide
-Phone stuck at Galaxy S logo screen?
*Put it in to DL mode, and run Odin again, it's just a bad install.
-All three ODIN is nonfunctional, stuck or giving "FAILED" errors?
*DO NOT CLOSE ODIN ONCE IT HAS FAILED!
*Unplug your phone
*Replug in your phone, get it into DL mode
* Unplug once it is in DL mode
*Replug and ODIN should recognize your phone
*Leave all the settings the same, then click "Start" again.
-Cannot get into download mode using the method I listed? Use the method(s) below:
Soldering Method
More methods coming soon
-----------------------------------------------------------------------------------------------------
I know how much of a pain posting in the Q/A section can be and the wait time is pretty bad, so if you need help regarding UNBRICKING and ONLY UNBRICKING feel free to post in here.[/S​
Click to expand...
Click to collapse

I unlocked my phone w Galaxy_S unlock 2 days ago. It's in the market and I was running Bionix V when I did it.

draikz said:
^ Hence the THANKS button.
Click to expand...
Click to collapse
Pretty soon we'll have apps that'll say hi and thanks and apps in general will replace everything we say, so much for what our parents taught us huh?

koooba said:
Pretty soon we'll have apps that'll say hi and thanks and apps in general will replace everything we say, so much for what our parents taught us huh?
Click to expand...
Click to collapse
Technology > your parents.
Anyday.

Do you know any other way i could unlock my samsung vibriant .nothing on this site has worked for me,,,who do i pay get files to work on this site please help poor black boy

franjess said:
Do you know any other way i could unlock my samsung vibriant .nothing on this site has worked for me,,,who do i pay get files to work on this site please help poor black boy
Click to expand...
Click to collapse
Poor with a few hundred dollars worth of phone. Lol
Did you try the PRO SGS app?

franjess said:
Do you know any other way i could unlock my samsung vibriant .nothing on this site has worked for me,,,who do i pay get files to work on this site please help poor black boy
Click to expand...
Click to collapse
If you want help you are going to have to be a lot more specific. What have you actually tried?
Just a tip, people will not help you on these forums if you ask for help without showing you've tried to solve the problem and know how to search.
There are loads of unlock threads. Almost everyone get one method to work eventually.

I've tried everything - someone please help

The Core Prime will not boot into recovery, or safe mode, or to the home screen. The only way to sometimes get it into download mode is leave it plugged into the wall charger for a couple minutes, then it will SOMETIMES go into download mode to charge. Holding down every combination of keys does not work, please don't suggest holding down keys.
All I ever see is a mmc confirmation fail movinand checksum confirmation fail error no matter what I try. I never see the Samsung intro, boot intro, or tracfone intro anymore, just a black screen that leads to that error message in red letters.
Regardless of which computer or cable I use, Windows never sees the phone. Doesn't try to install the drivers, doesn't make a sound that something was plugged in, nothing shows up in device manager, nothing (even in download mode)
I called 800 Samsung (4 times asking the same thing to different people to make sure I didn't just get helped by a noob over the phone). I went and talked to the Samsung guys inside worst buy (didn't do anything except informing me there is a Samsung store in LA). I called the Samsung store in LA and talked to a technician and the technician supervisor (I could drive there if their answer wasn't factory reset)
But EVERYONE from Samsung is saying all that can be done is factory reset.
I do not need a factory reset. I need my data.
I have posted numerous threads, and even though there was good advice given, none of it worked.
All I did before this error was try to update Google maps. The phone has never been backed up/rooted/nothing its stock.
At this point, I'm willing to negotiate paying someone to get my data back.
Someone please help.

Sorry To Hear that this is really a big problem but every thing has a solution ..
As you say the windows doesn't read the device and so as Odin try http://tinyurl.com/Heimdall-oa on Linux (don't use virtual machine )
OK if Heimdall read the device flash stock firmware (same version) if the device open congratulations
else flash custom recovery (you can find one in cyanogen discussion) and launch aroma file manager pull out your data so you're safe to reset ?? hope to be helped you .

The x man said:
Sorry To Hear that this is really a big problem but every thing has a solution ..
As you say the windows doesn't read the device and so as Odin try http://tinyurl.com/Heimdall-oa on Linux (don't use virtual machine )
OK if Heimdall read the device flash stock firmware (same version) if the device open congratulations
else flash custom recovery (you can find one in cyanogen discussion) and launch aroma file manager pull out your data so you're safe to reset ���� hope to be helped you .
Click to expand...
Click to collapse
Thank you for trying to help me. I do not yet have a Linux box set up. Can you recommend a distro, version, or live cd of Linux to use?

You can use Ubuntu 14.04

The x man said:
You can use Ubuntu 14.04
Click to expand...
Click to collapse
I will post my results here as soon as I try

If your phone is still stuck, flash TWRP (google it if you don't know it) for s820l. After TWRP is installed backup your data to your Internal or External Storage. Once the backup is complete factory reset (I highly suggest bakcking up to an SD card) if it still only boots to this screen try flashing the Stock ROM.
If your phone is messed up after the factory reset, i suggest SD card for files and everything if your computer has an SD adapter and reader you won't need to turn the device on. Hopefully this fixes it for you.
P.S. By no means do I know exactly what I'm doing, I flashed the wrong TWRP for mine and only got a download screen. This is the method i used to fix it. Also i am not allowed to post links or I would. so google sm-s820l custom recovery and to get a Stock ROM. Above the page for it should be a bunch of tabs that look like this " Android Area 51 > Forum > Straight Talk/Net10 > Samsung Phones > Samsung Galaxy Core Prime > Recovery Releases" Click on Samsung GCP and then your all set. Hope this helps.

AJOKER21 said:
If your phone is still stuck, flash TWRP (google it if you don't know it) for s820l. After TWRP is installed backup your data to your Internal or External Storage. Once the backup is complete factory reset (I highly suggest bakcking up to an SD card) if it still only boots to this screen try flashing the Stock ROM.
If your phone is messed up after the factory reset, i suggest SD card for files and everything if your computer has an SD adapter and reader you won't need to turn the device on. Hopefully this fixes it for you.
P.S. By no means do I know exactly what I'm doing, I flashed the wrong TWRP for mine and only got a download screen. This is the method i used to fix it. Also i am not allowed to post links or I would. so google sm-s820l custom recovery and to get a Stock ROM. Above the page for it should be a bunch of tabs that look like this " Android Area 51 > Forum > Straight Talk/Net10 > Samsung Phones > Samsung Galaxy Core Prime > Recovery Releases" Click on Samsung GCP and then your all set. Hope this helps.
Click to expand...
Click to collapse
Core prime model is also G-360* (main number) not just SM-820L .

The x man said:
Core prime model is also G-360* (main number) not just SM-820L .
Click to expand...
Click to collapse
True so if it's not the SM-S820L just input your model number instead of the one I posted that was my bad I assumed TracFone. Also don't think just because the phone is the same they will all work if you do use the wrong TWRP or ROM because the model is different it will brick your device. Again it was my mistake but overall I hope this helps.

AJOKER21 said:
True so if it's not the SM-S820L just input your model number instead of the one I posted that was my bad I assumed TracFone. Also don't think just because the phone is the same they will all work if you do use the wrong TWRP or ROM because the model is different it will brick your device. Again it was my mistake but overall I hope this helps.
Click to expand...
Click to collapse
Never mind i just wanted to share info. + mine reply was before twrp or cwm being ported to core prime ,and at this time no custom roms for 360* Models

Is TWRP ported to other versions of this phone? It seems like it is atleast the VE one has it and my TracFone version does I'm sure most of the others ones do and you also do not need a Custom ROM just a stock one which is probably floating around out there somewhere. For the OPs phone which if the model was posted this would be a billion times easier. So Mr. OP please post your model for us to help if your issue is still happening.

G360 Rom
AJOKER21 said:
True so if it's not the SM-S820L just input your model number instead of the one I posted that was my bad I assumed TracFone. Also don't think just because the phone is the same they will all work if you do use the wrong TWRP or ROM because the model is different it will brick your device. Again it was my mistake but overall I hope this helps.
Click to expand...
Click to collapse
I have a SM-S820L that i flashed with a 360 and now its bricked

Hii @android_n this is also happen with me on My core 2 G355H I also try to flash Offical frimware but it only boot for few second and shut down
I replace battery with new one and it booted
Problem is in battery it only boot when charger is connect or you can charge your phone battery by booster charger hit thanks if I help

I tried that what i need is a new OS. It keeps telling me No OS is installed but Havent been able to get it installed

noxqes said:
I tried that what i need is a new OS. It keeps telling me No OS is installed but Havent been able to get it installed
Click to expand...
Click to collapse
Check out this thread here http://forum.xda-developers.com/gal...stock-rom-deodex-busybox-root-t3378999/page1. Hope this helps
Sent from my SM-G360T1 using XDA Labs

"joying" radio stops after sleep

Hello!
I am a total noob at this so please forgive me if I don't give the correct information.
I have searched for this.
I appear to have successfully rooted my ebay head unit with this firmware. It is a Sofia 3GR, 2GB ram, Android 6.0.1.
https://forum.xda-developers.com/an.../rom-gtx-joying-stock-rom-2018-01-29-t3742482
Works Great!
When I remove the key from the ignition and leave it for 2 minuets the radio will not play/resume at all.
I have to go to go settings/apps/ radio and force stop it every time I want the radio to work.
The radio just started doing this BEFORE the firmware update. I thought it would fix it.

So looks like another one of those noob posts that no one can answer.
I have done more searching and found a few options.
There seems to be a "kill app" system on standby?
But I don't know if this is possible to change.
Replace radio app with another one?
I don't know which one will work
I am also struggling to put the Joying firmware back on.
Or buy another head unit. I have done this but still want to fix this one.
But also have to wait 2 months.

Icarusza said:
When I remove the key from the ignition and leave it for 2 minuets the radio will not play/resume at all.
I have to go to go settings/apps/ radio and force stop it every time I want the radio to work.
Click to expand...
Click to collapse
2 minutes? or longer?
The Sofia takes 4 minutes to fully close down to deep sleep. So yes, if you do this within 2 minutes you might have that behavior.
If you do that after approximately 4 minutes it should behave correct.
That is on the default ROM.
The gtxaspec ROM has Xposed. Check if Xposed is active.
As far as I can remember it comes standard with the XSofia Xposed module which I wrote for the most part. If not it might have the stand-alone nokill mod.

surfer63 said:
2 minutes? or longer?
The Sofia takes 4 minutes to fully close down to deep sleep. So yes, if you do this within 2 minutes you might have that behavior.
If you do that after approximately 4 minutes it should behave correct.
That is on the default ROM.
The gtxaspec ROM has Xposed. Check if Xposed is active.
As far as I can remember it comes standard with the XSofia Xposed module which I wrote for the most part. If not it might have the stand-alone nokill mod.
Click to expand...
Click to collapse
Oh my my! The famous surfer63 has responded to my silly little post!
I can confirm defiantly longer then 4 minuets as well and the radio ill not play after that.
Apologies but there is where I am more of a noob.
I do have an Xposed app on the head unit but am unsure of how to use it.
(Took me a year to find out where the RDS TXT was hiding) (so this is how slow I am)

Icarusza said:
I can confirm defiantly longer then 4 minuets as well and the radio ill not play after that.
Apologies but there is where I am more of a noob.
I do have an Xposed app on the head unit but am unsure of how to use it.
Click to expand...
Click to collapse
Do not underestimate your skills or overestimate mine.
By default all apps are killed, apart from a few very important ones. The radio app is not one of them and will be killed upon ignition off.
I really don't have a clue why it doesn't work for you.
You should be able to reflash the Joying firmware. The gtxaspec software uses a modified twrp recovery image, but after flashing the default Joying recovery is flashed back. Simply to make it possible to always go back to the Joying one.
- You did use the Custom.apk to prepare the unit for flashing the gtxaspec unit. Use this same app to check if you have the default Joying recovery in place. If not, use the Custom.apk to reinstall/reflash the standard Joying recovery.
- Which firmware version do you try to flash back?
- If the standard Joying recovery is in place and you have the correct Joying firmware, then please use a needle (or so) to reset the unit (RST pinhole). When the boot logo appears, reset it again. Do this 3 times. Then the leds will flash purple and your unit MUST start to reflash from usb-stick/SD-card.

surfer63 said:
Do not underestimate your skills or overestimate mine.
By default all apps are killed, apart from a few very important ones. The radio app is not one of them and will be killed upon ignition off.
I really don't have a clue why it doesn't work for you.
You should be able to reflash the Joying firmware. The gtxaspec software uses a modified twrp recovery image, but after flashing the default Joying recovery is flashed back. Simply to make it possible to always go back to the Joying one.
- You did use the Custom.apk to prepare the unit for flashing the gtxaspec unit. Use this same app to check if you have the default Joying recovery in place. If not, use the Custom.apk to reinstall/reflash the standard Joying recovery. Yes! as you described. (unless i messed something up I followed the instructions)
- Which firmware version do you try to flash back? This has always been my "safe firmware" as I don't have an original Joying https://drive.google.com/file/d/1b-b0sYd32DtzJ-WVYvd28dP80Ry52Ipm/view
- If the standard Joying recovery is in place and you have the correct Joying firmware, then please use a needle (or so) to reset the unit (RST pinhole). When the boot logo appears, reset it again. Do this 3 times. Then the leds will flash purple and your unit MUST start to reflash from usb-stick/SD-card.
Click to expand...
Click to collapse
I think my re flash procedure is incorrect.
Run Custom
RESTORE STOCK
VERIFY RECOVERY
Reboot to twrp?
INSTALL CUSTOM ROM?
Thought i would give Reboot to twrp a go which have an "Error wait here..." message and I have read that on another post. I will go read there...
https://forum.xda-developers.com/an...ange-problems-joying-2gb-intel-sofia-t3800556
Thanks for your assistance. The head unit is sitting with a black screen. I will wait and see what happens.

Icarusza said:
I think my re flash procedure is incorrect.
Run Custom
RESTORE STOCK
VERIFY RECOVERY
Reboot to twrp?
INSTALL CUSTOM ROM?
Thought i would give Reboot to twrp a go which have an "Error wait here..." message and I have read that on another post. I will go read there...
https://forum.xda-developers.com/an...ange-problems-joying-2gb-intel-sofia-t3800556
Thanks for your assistance. The head unit is sitting with a black screen. I will wait and see what happens.
Click to expand...
Click to collapse
For Joying firmware:
RESTORE STOCK
VERIFY RECOVERY
REBOOT (Just simple reboot to Android)
Insert Joying firmware
And if the screen stays black or you stay in a boot loop: Use the triple reset option.

surfer63 said:
For Joying firmware:
RESTORE STOCK
VERIFY RECOVERY
REBOOT (Just simple reboot to Android)
Insert Joying firmware
And if the screen stays black or you stay in a boot loop: Use the triple reset option.
Click to expand...
Click to collapse
This works up to the booting and remains in a boot loop even after trying the tipple reset.

Icarusza said:
This works up to the booting and remains in a boot loop even after trying the tipple reset.
Click to expand...
Click to collapse
Do you have the stock recovery on your system?
Did you get the purple leds? Note that the purple leds means "3 times unsuccesful boot. forced flash". It will not nicely reboot afterwards.
Did you put in the USB-stick/SD-card before reset? If there's nothing in the slots, it can't flash of course.

surfer63 said:
Do you have the stock recovery on your system?
Did you get the purple leds? Note that the purple leds means "3 times unsuccesful boot. forced flash". It will not nicely reboot afterwards.
Did you put in the USB-stick/SD-card before reset? If there's nothing in the slots, it can't flash of course.
Click to expand...
Click to collapse
1. Do you mean using
RESTORE STOCK
VERIFY RECOVERY
to get it on my system? If so then yes.
Your steps helped me get further this time.
2. No purple led's installed in this head unit.
3. Yes.
Should I used another firmware?
Should I try reinstall the GTX firmware?

Icarusza said:
2. No purple led's installed in this head unit.
3. Yes.
Click to expand...
Click to collapse
2. Sorry. I meant hardware buttons. They have leds which are normally set to a color, but turn purple after 3 incorrect boots. But if you do not have hardware buttons ....
Which firmware are you trying to flash? Have a link?

surfer63 said:
2. Sorry. I meant hardware buttons. They have leds which are normally set to a color, but turn purple after 3 incorrect boots. But if you do not have hardware buttons ....
Which firmware are you trying to flash? Have a link?
Click to expand...
Click to collapse
Oh no I have those touch buttons.
https://www.joyingauto.com/blog/post/joying-intel-sofia-android-car-stereo-software-update/
Updated files for HD resolution 1024*600 :
MCU version is 9.20 or more later please click Here
MCU version is 5.25 or more earlier please click Here
https://drive.google.com/file/d/1b-b0sYd32DtzJ-WVYvd28dP80Ry52Ipm/view <--this one

Icarusza said:
Oh no I have those touch buttons.
https://www.joyingauto.com/blog/post/joying-intel-sofia-android-car-stereo-software-update/
Updated files for HD resolution 1024*600 :
MCU version is 9.20 or more later please click Here
MCU version is 5.25 or more earlier please click Here
https://drive.google.com/file/d/1b-b0sYd32DtzJ-WVYvd28dP80Ry52Ipm/view <--this one
Click to expand...
Click to collapse
First of all: The first post in the gtxaspec thread mentions "you must be running Joying 6.0 firmware dated 2017_12_15 or later to install this ROM".
Were you doing that? And if so, why is your MCU version still 5.25?
If you have applied that firmware version for MCU version < 5.25, it will update your MCU version to >9.20.
I guess you can't check right now on the MCU version, but the next time you flash you need to take the "MCU version is 9.20 or more later" firmware and try that one.

surfer63 said:
First of all: The first post in the gtxaspec thread mentions "you must be running Joying 6.0 firmware dated 2017_12_15 or later to install this ROM".
Were you doing that? And if so, why is your MCU version still 5.25?
If you have applied that firmware version for MCU version < 5.25, it will update your MCU version to >9.20.
I guess you can't check right now on the MCU version, but the next time you flash you need to take the "MCU version is 9.20 or more later" firmware and try that one.
Click to expand...
Click to collapse
Yes you're right. It was 9.20
Before that, back when. I couldn't figure out the MCU versions and what I should use. So I closed my eyes and tried both and both worked and both solved issues.
So I did upgrade to the GTX from 9.20
OK let me try 9.20.

9.20 boot loop solved!
:laugh:

Jy firmware installed!
Will currently running in inside on a test rig. Will install in the car tomorrow.

Update!
The head unit has been in my car on standby for 2 hours and the radio still works! I will test it longer and over night.
This issue happened before the GTX so I might try go back to that.
I was dumb and put 12V on the right amp channel blowing it up so looking at a replacement amp.
Thank for putting up with this one @ surfer63!!
Much appreciated!

So another update.
If I install the GTX firmware then I get the radio issue which started this post.
However the radido issue did start on the Joying Firmware.... So Cant explain that.
Not on topic.
After blowing up the YD7388 I ordered a TDA7388. This have been fitted and running well!
I then added an extra heatsink to so will perform a bit better which has helped.
I still hope for the GTX to work but waiting on another head unit so I don't have to keep ripping my dash apart.

Need to root my Car Android head unit - 8227l (YT9218C_00005_V004_20190821 _HIFI)

Device specifications:
YT9218C_00005_V004_20190821 _HIFI
Android os: Android 9.1(It's actually 8.1 ) XY Auto: 3.1 (8227L)
Can bus:- 3.0(8227L)
DDR - 2G Flash: 32G
cpu: A7 1.3GHz x 4
Radio: NXP6851
Amplifier: AC7315 45W x 4
Display: 1024*600
MCU: 3.1 (8227L)
Purpose:
1. I want to take a full backup of my device.
2. I want to root
3. I want to upgrade firmware if possible
Tried below:
1. I started with taking a full backup. Hence tried to create a scatter file using MTK droid tools but i got error as "Error : TotalBytesPerChunk Not Found. Set default Page/Spare=2048/64 !!!" . Screenshot attached.
2. Tried to read back in SP tools but it does not detect. It shows blue DOT image which means it's not rooted.
I think I would need to root first but not sure what would be the safest way. firstly take the backup without root I was thinking about if that's possible. Else a concrete method which is safe to proceed with.

amit_coolcampus said:
Device specifications:
YT9218C_00005_V004_20190821 _HIFI
Android os: Android 9.1(It's actually 8.1 ) XY Auto: 3.1 (8227L)
Can bus:- 3.0(8227L)
DDR - 2G Flash: 32G
cpu: A7 1.3GHz x 4
Radio: NXP6851
Amplifier: AC7315 45W x 4
Display: 1024*600
MCU: 3.1 (8227L)
Purpose:
1. I want to take a full backup of my device.
2. I want to root
3. I want to upgrade firmware if possible
Tried below:
1. I started with taking a full backup. Hence tried to create a scatter file using MTK droid tools but i got error as "Error : TotalBytesPerChunk Not Found. Set default Page/Spare=2048/64 !!!" . Screenshot attached.
2. Tried to read back in SP tools but it does not detect. It shows blue DOT image which means it's not rooted.
I think I would need to root first but not sure what would be the safest way. firstly take the backup without root I was thinking about if that's possible. Else a concrete method which is safe to proceed with.
Click to expand...
Click to collapse
Hey bro tell me the procedure. I will try.

Smarty_009 said:
Hey bro tell me the procedure. I will try.
Click to expand...
Click to collapse
If you're asking about scatter file
Follow the link:

amit_coolcampus said:
If you're asking about scatter file
Follow the link:
Click to expand...
Click to collapse
No I am asking how to get it detected in the first place. My stereo is not detected by my laptop. Mtk and vcom drivers are installed.

Smarty_009 said:
No I am asking how to get it detected in the first place. My stereo is not detected by my laptop. Mtk and vcom drivers are installed.
Click to expand...
Click to collapse
For that I tried a lot of things. I had lost a hope because there was no option to play around with. But all of a sudden I restarted my PC when it was connected with radio. And when radio was restarting, it appeared for 2 seconds in my PC which gave me a hope that something is wrong with the radio OS so it doesn't appear when it's ON. Finally something worked after changing a lot of stuff in the settings, you can also try the same :
Go to car settings --> factory settings --> USB settings --> change it to Host/device (alternatively) --> it appeared for me

amit_coolcampus said:
For that I tried a lot of things. I had lost a hope because there was no option to play around with. But all of a sudden I restarted my PC when it was connected with radio. And when radio was restarting, it appeared for 2 seconds in my PC which gave me a hope that something is wrong with the radio OS so it doesn't appear when it's ON. Finally something worked after changing a lot of stuff in the settings, you can also try the same :
Go to car settings --> factory settings --> USB settings --> change it to Host/device (alternatively) --> it appeared for me
Click to expand...
Click to collapse
In have tried your way. It got detected fir a very short time when I changed from host to device and then it's shown as android adb. But I can't root from MTK droid tool and sp flash tool cannot see it

Smarty_009 said:
In have tried your way. It got detected fir a very short time when I changed from host to device and then it's shown as android adb. But I can't root from MTK droid tool and sp flash tool cannot see it
Click to expand...
Click to collapse
Same here. I am still trying to figure out how to root it. Please let me know if you come across something.

amit_coolcampus said:
Same here. I am still trying to figure out how to root it. Please let me know if you come across something.
Click to expand...
Click to collapse
Sure... Hey buddy am there on 4pda.ru
Give me the link of you get it.

Smarty_009 said:
Sure... Hey buddy am there on 4pda.ru
Give me the link of you get it.
Click to expand...
Click to collapse
Which link?

amit_coolcampus said:
Which link?
Click to expand...
Click to collapse
Have you tried this...
https://4pda.ru/forum/index.php?showtopic=936535&view=findpost&p=89215913

Smarty_009 said:
Have you tried this...
https://4pda.ru/forum/index.php?showtopic=936535&view=findpost&p=89215913
Click to expand...
Click to collapse
I had thought about doing it. Registered to the portal a couple of days back but then had some other commitments so didn't get plenty of time.
Questions I had:
Before proceeding to do anything, I wanted to take Backup. But when our device is not getting detected in sp tools how to flash recovery.

Smarty_009 said:
Have you tried this...
https://4pda.ru/forum/index.php?showtopic=936535&view=findpost&p=89215913
Click to expand...
Click to collapse
Did you try or Are you planning to try this?

amit_coolcampus said:
I had thought about doing it. Registered to the portal a couple of days back but then had some other commitments so didn't get plenty of time.
Questions I had:
Before proceeding to do anything, I wanted to take Backup. But when our device is not getting detected in sp tools how to flash recovery.
Click to expand...
Click to collapse
Exactly this is stopping me too. If I am able to take full backup with sp flash tool then I can play around.
I have rooted my Lenovo p1a42 and Asus zenfone max pro m1 straight out of the box. Never seen there stock ROM. :silly:
For this also I would have done but now not going to do it anymore.

H did you solve it

Smarty_009 said:
Hey bro tell me the procedure. I will try.
Click to expand...
Click to collapse

Touch screen and buttons stopped working help!

My touch screen isn’t working tried everything reset, power unplug, battery unplug. Only works with mouse and dongle,
I want to try to reflash original firmware does anyone have?
This is the same exact model
Double din
Android 8.1
7 inch
Ac8227L
firmware zxdz_2019.18.15
mcu version cvd1810_wj_19.08.02_011

Hi, I think you have wrong PSA / canbus settings in factory menu. Do you have wheel commands and are they working ?

Anton TNT said:
Hi, I think you have wrong PSA / canbus settings in factory menu. Do you have wheel commands and are they working ?
Click to expand...
Click to collapse
No wheel commands only the mouse works with Donghee plugged into usb. GPS keeps rerouting. No touch or buttons working. It’s the same exact unit in the YouTube video. Tried commenting to user but no reply.
System platform Ac8227L
firmware android 8.1 7 inch double din. zxdz_2019.18.15
mcu version cvd1810_wj_19.08.02_011

zxdz_2019.18.15 is the base for software search here, but I see it uses 8227L chipset, so in fact it can use any 8227L based firmware upgrade.
I have firmwares with android 10 , 8 I don't have. But will search for you on net.

This is your device : https://romprovider.com/stock-firmware-head-unit-zxdz-01/
Firmware and flash tools are inside ! READ CAREFULLY and proceed with update.
Try first update firmware - if it isn't working contact someone who will flash ROM, DO NOT DO IT YOURSELF as you can brick your device if you are not sure what you are doing!
(NOTE: before downloading files in most cases you must ask for permission to download firmware as it is connected to some personal account on Google drive, if not asked anything just proceed with download)
Wish you happy installing and keep me informed if you succeed.

Anton TNT said:
This is your device : https://romprovider.com/stock-firmware-head-unit-zxdz-01/
Firmware and flash tools are inside ! READ CAREFULLY and proceed with update.
Try first update firmware - if it isn't working contact someone who will flash ROM, DO NOT DO IT YOURSELF as you can brick your device if you are not sure what you are doing!
(NOTE: before downloading files in most cases you must ask for permission to download firmware as it is connected to some personal account on Google drive, if not asked anything just proceed with download)
Wish you happy installing and keep me informed if you succeed.
Click to expand...
Click to collapse
You are the best! I will try and let you know thank you sir!

Hi
Any possible solution?

djdinger said:
You are the best! I will try and let you know thank you sir!
Click to expand...
Click to collapse
Can u share ur experience please?