Related
I am in SO much trouble with the Wife....
Bought the Wife an S5, and pulled her SD card from the S4, and was going to backup files and contacts but entered the WRONG swipe pattern 3 times (I was using mine), and now it's asking for a PIN.
She hasn't set one that she recalls. We log into Google and do the LOCK, reset PIN to 1234 and the phone STILL sez it's the wrong PIN.
The only info I can give is it appears to be on 4.4.2 I think, recovery mode reports
Android System Recovery <3e>
KOT49H.I545VRUFNG6
I tried Aroma 1.8 and 1.9x to no avail, fails E-Signature. Is there any help to be had without destroying user data on the phone?
I don't mind donating either to whoever helps me!
Shaun
sgoeckner said:
I am in SO much trouble with the Wife....
Bought the Wife an S5, and pulled her SD card from the S4, and was going to backup files and contacts but entered the WRONG swipe pattern 3 times (I was using mine), and now it's asking for a PIN.
She hasn't set one that she recalls. We log into Google and do the LOCK, reset PIN to 1234 and the phone STILL sez it's the wrong PIN.
The only info I can give is it appears to be on 4.4.2 I think, recovery mode reports
Android System Recovery <3e>
KOT49H.I545VRUFNG6
I tried Aroma 1.8 and 1.9x to no avail, fails E-Signature. Is there any help to be had without destroying user data on the phone?
I don't mind donating either to whoever helps me!
Shaun
Click to expand...
Click to collapse
Install ADB on your PC, just Google how to, then plug into PC and use the command "ADB Pull /sdcard" to take a backup of the internal storage.
npjohnson said:
Install ADB on your PC, just Google how to, then plug into PC and use the command "ADB Pull /sdcard" to take a backup of the internal storage.
Click to expand...
Click to collapse
OK I have ADB & Fastboot installed. When I plug the phone into the pc though it comes up as a drive in my tree, but no files, there isn't any real tree on it. When I run your command from CMD Prompt it says ERROR: Device not found
What now?
sgoeckner said:
OK I have ADB & Fastboot installed. When I plug the phone into the pc though it comes up as a drive in my tree, but no files, there isn't any real tree on it. When I run your command from CMD Prompt it says ERROR: Device not found
What now?
Click to expand...
Click to collapse
Try "Adb devices" if nothing shows up, that is unfortunate....
This next way /SHOULD/ work, no promises though , I used this method to get from VRUFNG6 to VRUFNC5 after accidentally deleting some system files, your ideal solution is an NG6 No-Wipe TAR, because it would restore your /system, partition (and passcode) but keep user data, but no such TAR exists... so the easiest way would be to use the No-Wipe NC5 tar, then re-upgrade to NG6 via the settings app (OTA)
Download the No-Wipe, MAKE SURE ITS THE NO WIPE NC5 tar in this thread: http://forum.xda-developers.com/showthread.php?t=2735172 , and follow the instructions to flash it. (i.e. load the .tar.md5 file into ODIN's AP Slot)
When you reboot, you may be greeted by some apps force closing... all you have to do is uninstall them and reinstall those apps from the Play store. After you reinstall those, reboot again and take the NG6 update through settings. Then you will be at NG6 w/o a passcode and your user data will be preserved.
Good Luck man. Hope your wife doesn't kill you.
- Nolen Johnson
If what I did helped out, and your feeling generous, click on my "Donate to Me" button and shoot me something on PayPal
npjohnson said:
Try "Adb devices" if nothing shows up, that is unfortunate....
This next way /SHOULD/ work, no promises though , I used this method to get from VRUFNG6 to VRUFNC5 after accidentally deleting some system files, your ideal solution is an NG6 No-Wipe TAR, because it would restore your /system, partition (and passcode) but keep user data, but no such TAR exists... so the easiest way would be to use the No-Wipe NC5 tar, then re-upgrade to NG6 via the settings app (OTA)
Download the No-Wipe, MAKE SURE ITS THE NO WIPE NC5 tar in this thread: http://forum.xda-developers.com/showthread.php?t=2735172 , and follow the instructions to flash it. (i.e. load the .tar.md5 file into ODIN's AP Slot)
When you reboot, you may be greeted by some apps force closing... all you have to do is uninstall them and reinstall those apps from the Play store. After you reinstall those, reboot again and take the NG6 update through settings. Then you will be at NG6 w/o a passcode and your user data will be preserved.
Good Luck man. Hope your wife doesn't kill you.
- Nolen Johnson
If what I did helped out, and your feeling generous, click on my "Donate to Me" button and shoot me something on PayPal
Click to expand...
Click to collapse
NOLEN-
It's WORSE THAN DEATH brother. She broke out the River of Tears on me dude.
Having said that, when I took Programming Pascal was the hip thing and C was the new kid on the block. However I have spent a lifetime building DWDM optical networks, so I'm at least a technoid. I'll read up on the ODIN...
EDIT:
1- Do I have to reinstall the APPS that may need to be? All I'm after are the pics and msg downloads and then I can toss it!
2- Once this procedure/upload is complete and reboot takes place, the is then on it's original release with no security?
DOUBLE EDIT:
What a schmuck....I found the flash instructions....
Heres a cookie for your help too...
S~
sgoeckner said:
NOLEN-
It's WORSE THAN DEATH brother. She broke out the River of Tears on me dude.
Having said that, when I took Programming Pascal was the hip thing and C was the new kid on the block. However I have spent a lifetime building DWDM optical networks, so I'm at least a technoid. I'll read up on the ODIN...
EDIT:
1- I didn't see instructions, and there are several radio buttons to select before (presumably) pressing the START button?
2- Do I have to reinstall the APPS that may need to be? All I'm after are the pics and msg downloads and then I can toss it!
3- Once this procedure/upload is complete and reboot takes place, the is then on it's original release with no security?
Heres a cookie for your help too...
S~
Click to expand...
Click to collapse
1. Just use the no wipe TAR file in the AP Slot in Odin, don't fill any other slots, only check the boxes that are pre-checked when ODIN starts. Then Reboot into download mode by shutting the phone down, then hold volume down and power to boot into download mode, select continue with the volume up button when prompted. Plug into your PC and click Start.
2. Well, maybe. If the force close is not a constant one (like it was for me, Nova launcher constantly crashed), then you should be good.
3. Well, the /system partition is restored. Your data is still present. What do you mean by Security? Also, if when you want to sell the S4, you want to Wipe to factory defaults, just use the Full-Wipe in ODIN.
4. Thanks man!!! I really appreciate it!
In response to your Double Edit: Haha. Not your fault, It took me a few reads through to understand half the stuff Ive learned here XD
npjohnson said:
1. Just use the no wipe TAR file in the AP Slot in Odin, don't fill any other slots, only check the boxes that are pre-checked when ODIN starts. Then Reboot into download mode by shutting the phone down, then hold volume down and power to boot into download mode, select continue with the volume up button when prompted. Plug into your PC and click Start.
2. Well, maybe. If the force close is not a constant one (like it was for me, Nova launcher constantly crashed), then you should be good.
3. Well, the /system partition is restored. Your data is still present. What do you mean by Security? Also, if when you want to sell the S4, you want to Wipe to factory defaults, just use the Full-Wipe in ODIN.
4. Thanks man!!! I really appreciate it!
Click to expand...
Click to collapse
GRrr!
It failed- Write Operation Failed. It didn't establish a connection, although it sees the com port anyway.
sgoeckner said:
GRrr!
It failed- Write Operation Failed. It didn't establish a connection, although it sees the com port anyway.
Click to expand...
Click to collapse
Oh. My bad, I forgot to include the step to install the Samsung mobile USB Driver here: http://forum.xda-developers.com/showthread.php?t=961956
Try again after that.
If not, try a diff. USB Port (preferably 2.0), for some reason, I have one USB on my laptop that actually gets along with ODIN. XD
Edit: are you using ODIN 3.09? I know that 3.07 has issues with Kitkat.
npjohnson said:
Oh. My bad, I forgot to include the step to install the Samsung mobile USB Driver here: http://forum.xda-developers.com/showthread.php?t=961956
Try again after that.
If not, try a diff. USB Port (preferably 2.0), for some reason, I have one USB on my laptop that actually gets along with ODIN. XD
Edit: are you using ODIN 3.09? I know that 3.07 has issues with Kitkat.
Click to expand...
Click to collapse
Using 3.09 and interesting, I run as admin the driver file and it makes like it starts something and then...nothing. Hmmm. Like I mentioned, it see's the usb attach to the laptop, comes up as a Portable Device but that's it...
sgoeckner said:
Using 3.09 and interesting, I run as admin the driver file and it makes like it starts something and then...nothing. Hmmm. Like I mentioned, it see's the usb attach to the laptop, comes up as a Portable Device but that's it...
Click to expand...
Click to collapse
Hmm... maybe a bad file? Try this more direct link: http://samsung-usb-driver-for-mobile-phones.en.softonic.com/download#
---------- Post added at 01:02 AM ---------- Previous post was at 12:58 AM ----------
sgoeckner said:
Using 3.09 and interesting, I run as admin the driver file and it makes like it starts something and then...nothing. Hmmm. Like I mentioned, it see's the usb attach to the laptop, comes up as a Portable Device but that's it...
Click to expand...
Click to collapse
.... maybe a stupid question, did you try the generic passcode? Like 0000 and 1234?
npjohnson said:
Hmm... maybe a bad file? Try this more direct link: http://samsung-usb-driver-for-mobile-phones.en.softonic.com/download#
---------- Post added at 01:02 AM ---------- Previous post was at 12:58 AM ----------
.... maybe a stupid question, did you try the generic passcode? Like 0000 and 1234?
Click to expand...
Click to collapse
OH HOLY CRAP! If it is, I'm gonna have to change the combination on luggage, they're the same...
Pretty sure it's not the file but will try the other one as well...
sgoeckner said:
OH HOLY CRAP! If it is, I'm gonna have to change the combination on luggage, they're the same...
Pretty sure it's not the file but will try the other one as well...
Click to expand...
Click to collapse
Well, if it doesn't install, just use the Google Generic Phone driver, just Google it.
Then plug into a different port on your computer (not a USB hub) and also make sure its a nicer (preferably Samsung) cable, then try flashing again.
sgoeckner said:
OH HOLY CRAP! If it is, I'm gonna have to change the combination on luggage, they're the same...
Pretty sure it's not the file but will try the other one as well...
Click to expand...
Click to collapse
Did you get this sorted? Is user data all you need off the phone? Contact/call logs/text messages...etc? Also, why did you not just pull the battery once it asked for a pin to get back to whatever form of security was set previous? When you set up your security, it asks for a pin so she would have had to enter one.
"Your words were found and I ate them, And Your words became for me a joy and the delight of my heart; For I have been called by Your name, O LORD God of hosts." - Jeremiah 15:16
liljoe727 said:
Did you get this sorted? Is user data all you need off the phone? Contact/call logs/text messages...etc? Also, why did you not just pull the battery once it asked for a pin to get back to whatever form of security was set previous? When you set up your security, it asks for a pin so she would have had to enter one.
"Your words were found and I ate them, And Your words became for me a joy and the delight of my heart; For I have been called by Your name, O LORD God of hosts." - Jeremiah 15:16
Click to expand...
Click to collapse
If I'm correct if an exchange email is set up on the device, rebooting wont do a thing, it will still want a passcode, one that she doesn't remember setting.
npjohnson said:
If I'm correct if an exchange email is set up on the device, rebooting wont do a thing, it will still want a passcode, one that she doesn't remember setting.
Click to expand...
Click to collapse
This is the screen I get when I incorrectly enter my swipe pattern. Stock/rooted. I'm thinking if they went with "forgot pattern" (which I'm not sure why the would), then they would have needed to enter email/password info to have the pattern image emailed to them. You cannot get to a point on an S4 (to my knowledge) where the security will overwrite the preferred and selected security (swipe in this case) for something else. Unless they selected "backup pin" and you get almost unlimited tries then and even still, once the 30 second lockout is over, security just goes back to whatever is set (swipe in this case). The question in the OP kind of does not make sense to me but if he's been flashing firmware, the security lock is not really his problem anymore if he still wants his user data....Unless I'm completely off base here.
[Edit] Her work requiring a pin if she gets company email to her phone just clicked. Lol. She would have had to set all that up through work though and definitely would've needed to select a pin number but that would all be done through work so changing the passcode through Google would do nothing anyway...
"Your words were found and I ate them, And Your words became for me a joy and the delight of my heart; For I have been called by Your name, O LORD God of hosts." - Jeremiah 15:16
liljoe727 said:
This is the screen I get when I incorrectly enter my swipe pattern. Stock/rooted. I'm thinking if they went with "forgot pattern" (which I'm not sure why the would), then they would have needed to enter email/password info to have the pattern image emailed to them. You cannot get to a point on an S4 (to my knowledge) where the security will overwrite the preferred and selected security (swipe in this case) for something else. Unless they selected "backup pin" and you get almost unlimited tries then and even still, once the 30 second lockout is over, security just goes back to whatever is set (swipe in this case). The question in the OP kind of does not make sense to me but if he's been flashing firmware, the security lock is not really his problem anymore if he still wants his user data....Unless I'm completely off base here.
[Edit] Her work requiring a pin if she gets company email to her phone just clicked. Lol. She would have had to set all that up through work though and definitely would've needed to select a pin number but that would all be done through work so changing the passcode through Google would do nothing anyway...
"Your words were found and I ate them, And Your words became for me a joy and the delight of my heart; For I have been called by Your name, O LORD God of hosts." - Jeremiah 15:16
Click to expand...
Click to collapse
OK, so this is my WIFE we're talking about here; as far as she's concerned, it's Magic we're discussing here
She had Backup setup, so she got her contacts but the messages and photos that weren't stored on the SD card are what she's looking for. The pics her Sisters in Peru sent her over WhatsApp, downloads and SMS.
Thanks to everyone for pitching in. Not sure why it went to the PIN request, or what that PIN is but it does warn that after 10 attempts it'll wipe the device...but if I go to Google and do a LOCK command and change pin there, it resets the number of attempts to zero. SO. THEORETICALLY speaking I could enter 0000-9999 and see which one works but that may take a few years ....
sgoeckner said:
OK, so this is my WIFE we're talking about here; as far as she's concerned, it's Magic we're discussing here
She had Backup setup, so she got her contacts but the messages and photos that weren't stored on the SD card are what she's looking for. The pics her Sisters in Peru sent her over WhatsApp, downloads and SMS.
Thanks to everyone for pitching in. Not sure why it went to the PIN request, or what that PIN is but it does warn that after 10 attempts it'll wipe the device...but if I go to Google and do a LOCK command and change pin there, it resets the number of attempts to zero. SO. THEORETICALLY speaking I could enter 0000-9999 and see which one works but that may take a few years ....
Click to expand...
Click to collapse
I'd Install some different drivers and see which one gets ODIN to succeed, because if it will flash, that will work.
npjohnson said:
I'd Install some different drivers and see which one gets ODIN to succeed, because if it will flash, that will work.
Click to expand...
Click to collapse
I'm worried that being LOCKED, it shuts down the port or something....
sgoeckner said:
I'm worried that being LOCKED, it shuts down the port or something....
Click to expand...
Click to collapse
Uh. It shouldnt be locked. The phone should be in download mode. Have you been putting it in download mode?
OK so it TOOK the NC5 downgrade, but now it's at the "enter PIN" screen again. It HAD been in a boot loop with "android.process.acore" has stopped. Now it seems stable, it's not rebooting anyway.
What now?
I beat my head against this for about eight hours yesterday and am at my wit's end. Thanks in advance for any help.
The short version: After rooting my Blue VIvo 5, installing a few apps and setting Nova Launcher as my launcher, I started getting some errors. Apps would fail mysteriously or not launch at all. Reinstalling the apps didn't help. I tried to take an OS update that the phone said was available, but when I tried to update it said the system was damaged and I couldn't install the update.
Well, I thought naively, I'll just remove all my user data and start over. That will restore the original ROM and I'll just start over, right?
BIG mistake.
Now when I try to start up my phone the sequence goes like this:
1. I get a popup that says "Unfortunately, Carefree Launcher has stopped."
2. After clearing that popup I can choose my language.
3. Next I go tot he screen where I choose my wireless connection. Choosing the connection works, but the next screen where I put in my password only allows me to speak - there's no keyboard option. The only time during the process I really laughed was when I saw what Google's voice recognition software tried to enter for the wifi password.
4. I managed to get the password entered by using the OTG dongle and a USB keyboard. After that, though, it goes to the "Checking for updates" screen, at which point it tells me "Unfortunately, Google Play Services has stopped." Then it loops back to the "choose your network" screen.
5. Lather, rinse, repeat.
I managed to get TWRP installed and running, but the stock ROM file I found on another thread (BLU_V0050UU_V09_REPAIR.zip) won't install. SP Flasher (which I also tried) throws a message about a mismatched baseband unit of some kind, and TWRP says there's a file called META-INF/com/google/android/update-binary missing from the archive.
So here I am, asking the community what I can do short of laying out $200 for another phone. I might be able to install the AOSP or CM12 ROMs that are in this forum, and I might do that if I have to replace the phone anyway, but if there's a way to restore the phone to its initial OOB state, I would love to know how to do it.
Again, thanks for any help you can give me.
Update, 16 hours later: I had a flash of inspiration this morning. Since it looked like at any rate I was going to have to get another phone I went ahead and ordered the replacement for same-day delivery. It arrived this afternoon, I unboxed it, set it up and backed it up with "adb backup". Then, I tried to restore the backup onto the bricked phone.
You guessed it. I never saw a notification that the backup was loading. It was the same wifi network, check for updates, broken google play loop again.
So unless someone has a brilliant idea as to how to restore the original firmware, I am going to keep the old bricked phone around and try installing aosp or cm12 on it, whichever looks like it's further along. Maybe both. Why not?
Anyway cheers.
Do you not know how to use SP Flash Tool?
Download the original rom + SP Flash Tool from elsewhere in this forums and flash it. The one for the Gionee S6 or A55 slim on the Marshmallow thread will do. I think someone has posted the original vivo 5 ROM somewhere as well.
Basic steps are open SP Flash Tool.
Load the scatter file (comes with the rom). This will fill a lot of fields in the flash screen (boot, recovery, logo, system, userdata, etc.).
Do not change anything. Click "Start"—this will wipe your phone. If you don't want it wiped, disable the "userdata" field.
Connect your phone properly turned off.
It should detect your phone right away.
Wait for the flash to end.
Disconnect your phone and turn it on.
Should boot alright.
If it doesn't detect your phone, see in Device Manager if your phone is properly recognized. If it's not, download the MediaTek PreLoader USB VCOM drivers.
victorvscn said:
Do you not know how to use SP Flash Tool?
Click to expand...
Click to collapse
Thank you for your reply. In answer to your quesiton: Maybe not. Everybody starts somewhere, and while I have quite a few years of experience in desktop computers, I'm still learning the world of Android. I've flashed quite a few Kindle Fire tablets (that's the origin of my user name, 'nerdfire') but this has been my first experience with a phone.
victorvscn said:
Download the original rom + SP Flash Tool from elsewhere in this forums and flash it. The one for the Gionee S6 or A55 slim on the Marshmallow thread will do. I think someone has posted the original vivo 5 ROM somewhere as well.
Basic steps are open SP Flash Tool.
Load the scatter file (comes with the rom). This will fill a lot of fields in the flash screen (boot, recovery, logo, system, userdata, etc.).
Do not change anything. Click "Start"—this will wipe your phone. If you don't want it wiped, disable the "userdata" field.
Connect your phone properly turned off.
It should detect your phone right away.
Wait for the flash to end.
Disconnect your phone and turn it on.
Should boot alright.
If it doesn't detect your phone, see in Device Manager if your phone is properly recognized. If it's not, download the MediaTek PreLoader USB VCOM drivers.
Click to expand...
Click to collapse
I've got SP Flash running, but it's the Linux version. which I think is the same, as Windows except that it looks like there's a "Download" button rather than a "Start" button. Unless I'm missing something, which could easily be.
I followed the directions above, not checking "userdata", and hit "Download." No response from the program for over 30 minutes. I eventually found the timeout setting, lowered it to 2 minutes, and ran the program from a console window. The console output indicated that SP Flash was finding the proper USB port, but then nothing. No communication with the phone and the program eventually timed out.
It could be a lack of drivers. Linux comes with drivers for most common USB devices baked in, but this might not be one of them. Thanks for the hint - I'll check when I get home later tonight.
Again, I appreciate the help.
NerdFire said:
Thank you for your reply. In answer to your quesiton: Maybe not. Everybody starts somewhere, and while I have quite a few years of experience in desktop computers, I'm still learning the world of Android. I've flashed quite a few Kindle Fire tablets (that's the origin of my user name, 'nerdfire') but this has been my first experience with a phone.
Click to expand...
Click to collapse
Sorry about that, mate, I came out rather bluntly for some reason. Just wanted to ask whether you'd had any experience with it.
NerdFire said:
I've got SP Flash running, but it's the Linux version. which I think is the same, as Windows except that it looks like there's a "Download" button rather than a "Start" button. Unless I'm missing something, which could easily be.
I followed the directions above, not checking "userdata", and hit "Download." No response from the program for over 30 minutes. I eventually found the timeout setting, lowered it to 2 minutes, and ran the program from a console window. The console output indicated that SP Flash was finding the proper USB port, but then nothing. No communication with the phone and the program eventually timed out.
It could be a lack of drivers. Linux comes with drivers for most common USB devices baked in, but this might not be one of them. Thanks for the hint - I'll check when I get home later tonight.
Again, I appreciate the help.
Click to expand...
Click to collapse
I have no experience flashing with Linux, but that definitely looks like lack of the right drivers. Maybe following this tutorial will work for you: https://forum.xda-developers.com/ge...torial-how-to-setup-spflashtoollinux-t3160802
The thread says you need to know the specific way to boot up after connecting the cable, depending on the phone. On the Vivo, my experience is that you don't need to press anything, just connecting the cable with the phone powered off will do. However, if you happen to brick your phone by flashing something wrong, or interrupting a flash, you'll need to press volume down upon connecting the cable.
victorvscn said:
Sorry about that, mate, I came out rather bluntly for some reason. Just wanted to ask whether you'd had any experience with it..
Click to expand...
Click to collapse
No worries, I didn't take offense.
victorvscn said:
I have no experience flashing with Linux, but that definitely looks like lack of the right drivers. Maybe following this tutorial will work for you: https://forum.xda-developers.com/ge...torial-how-to-setup-spflashtoollinux-t3160802
The thread says you need to know the specific way to boot up after connecting the cable, depending on the phone. On the Vivo, my experience is that you don't need to press anything, just connecting the cable with the phone powered off will do. However, if you happen to brick your phone by flashing something wrong, or interrupting a flash, you'll need to press volume down upon connecting the cable.
Click to expand...
Click to collapse
I did a little digging and won't go through all the gory details, but the long and short of it was, after removing a package in my Linux distribution that was interfering with accessing the serial port, I was able to flash the stock ROM onto the phone. So I am good to go. Plus, now I have a good idea of how to start over again if necessary
Thank you again so much for your help.,
NerdFire said:
No worries, I didn't take offense.
I did a little digging and won't go through all the gory details, but the long and short of it was, after removing a package in my Linux distribution that was interfering with accessing the serial port, I was able to flash the stock ROM onto the phone. So I am good to go. Plus, now I have a good idea of how to start over again if necessary
Thank you again so much for your help.,
Click to expand...
Click to collapse
Good to hear!
NerdFire said:
No worries, I didn't take offense.
I did a little digging and won't go through all the gory details, but the long and short of it was, after removing a package in my Linux distribution that was interfering with accessing the serial port, I was able to flash the stock ROM onto the phone. So I am good to go. Plus, now I have a good idea of how to start over again if necessary
Thank you again so much for your help.,
Click to expand...
Click to collapse
where can I find the stock Rom ? Can you Share link please?
Man, im pulling my hair out trying to get this box working again.
Short brief: I bricked it lol. But Ive got it to connect to the PC again via the shorting it out trick.
I've flashed a couple of different iso's to no success.
Which I mean, it completed 100%, but once disconnected, it wouldn't boot up.
I just cannot find the specific one for my MXQ Pro.
As I said, the specs are
S905X
6.0.1 Marshmallow
H234_V2.2
2017-04-08 is whats written on the mother board.
I'm trying to flash it using USB_Burning_Tool 2.0.7.2
Ive probably wasted 100gig in downloads so far trying to find firmware thats compatible. I'm just about ready to throw it in the bin.
As a last ditch effort, does anyone know where I can find compatible firmware for this thing?
cheers
Xdegenerate said:
Man, im pulling my hair out trying to get this box working again.
Short brief: I bricked it lol. But Ive got it to connect to the PC again via the shorting it out trick.
I've flashed a couple of different iso's to no success.
Which I mean, it completed 100%, but once disconnected, it wouldn't boot up.
I just cannot find the specific one for my MXQ Pro.
As I said, the specs are
S905X
6.0.1 Marshmallow
H234_V2.2
2017-04-08 is whats written on the mother board.
I'm trying to flash it using USB_Burning_Tool 2.0.7.2
Ive probably wasted 100gig in downloads so far trying to find firmware thats compatible. I'm just about ready to throw it in the bin.
As a last ditch effort, does anyone know where I can find compatible firmware for this thing?
Click to expand...
Click to collapse
try this android 6.1 https://mega.nz/#!OpAATBTY!CY_KUix-gKUaAxecY8pREqu8Wi9WvkbSJNXhInKDzMQ
and this android 7.1 https://mega.nz/#!q4Y0xKbJ!W1-HBCiRGBgq_tW6AFzsbOUweRRs7ov8Cg6h92ILQi8
frake50 said:
try this android 6.1 https://mega.nz/#!OpAATBTY!CY_KUix-gKUaAxecY8pREqu8Wi9WvkbSJNXhInKDzMQ
and this android 7.1 https://mega.nz/#!q4Y0xKbJ!W1-HBCiRGBgq_tW6AFzsbOUweRRs7ov8Cg6h92ILQi8
Click to expand...
Click to collapse
Thanks, but no success.
Usb Control setup errors
Xdegenerate said:
Thanks, but no success.
Usb Control setup errors
Click to expand...
Click to collapse
in this case you need to open the cover again and write down which manufacture you have of thechip -- samsung or Ky hynix i think in your case maybe HX
you can try
https://drive.google.com/drive/folders/1eg_hjvzCzs0H2bGk_oEfuLKvynjlh-3u 7.1
frake50 said:
in this case you need to open the cover again and write down which manufacture you have of thechip -- samsung or Ky hynix i think in your case maybe HX
you can try
https://drive.google.com/drive/folders/1eg_hjvzCzs0H2bGk_oEfuLKvynjlh-3u 7.1
Click to expand...
Click to collapse
Which part am I looking at to figure out which one it is?
https://imgur.com/a/TTNyuV1
Edit: Oh, i think i see it.
SK hynix!
Xdegenerate said:
Which part am I looking at to figure out which one it is?
https://imgur.com/a/TTNyuV1
Edit: Oh, i think i see it.
SK hynix!
Click to expand...
Click to collapse
exactly yours NAND SK hynix manufacture ... only firmware with box had this nand will work.. if you flash firmware from Samsung box it will freeze at boot as you wrote at yours first post.
the pervious post i added link at google drv are Hynix Nand firmware.. you can also try and search after Docooler 4K box as they are Hynix too.... 4pda.ru had section with many firmware..
version from Docooler android 7.1 V1880-16G V2322 7.1 passed on your box
check here too
https://forum.xda-developers.com/an...ters/amlogic/docooler-m9s-pro-t3450711/page26
good luck
frake50 said:
exactly yours NAND SK hynix manufacture ... only firmware with box had this nand will work.. if you flash firmware from Samsung box it will freeze at boot as you wrote at yours first post.
the pervious post i added link at google drv are Hynix Nand firmware.. you can also try and search after Docooler 4K box as they are Hynix too.... 4pda.ru had section with many firmware..
version from Docooler android 7.1 V1880-16G V2322 7.1 passed on your box
check here too
https://forum.xda-developers.com/an...ters/amlogic/docooler-m9s-pro-t3450711/page26
good luck
Click to expand...
Click to collapse
well, the first link worked. It's booted up. Only problem is, the remote doesnt respond, it only allows me to push down. I installed the next one successfully too, but same problem. The remote only allows a down navigation. Pressing anything else won't work.
Keyboard and mouse respond just fine.
I've tried changing the remote files, even tried the Beelink one, but none of them are working.
I've tried two remotes, both doo the same thing.
The firmware is rooted.
One thing I'm seeing is a notification saying the SU binary needs updating. However the link I downloaded it from says not to, as it will cause a boot loop.
I'm wondering if perhaps when I opened the box and shorted it to read to usb burner, if maybe I damaged the reciever or something? However, when pressing buttons on the remote, pressing up does change the blue light to red on the box, so it is recieving something, just not doing what it should.
But pressing left or right does not change the light.
Edit. I've just discovered pressing up is actually being used as the return key, it backs out of apps.
None of the 4 files, or the Beelink file fix the issue.
Xdegenerate said:
well, the first link worked. It's booted up. Only problem is, the remote ..Edit. I've just discovered pressing up is actually being used as the return key, it backs out of apps.
None of the 4 files, or the Beelink file fix the issue.
Click to expand...
Click to collapse
Try this remote.conf unzip it and replace it in system/etc don't forget change the permission to 0644
frake50 said:
Try this remote.conf unzip it and replace it in system/etc don't forget change the permission to 0644
Click to expand...
Click to collapse
How do I change the permission?
Xdegenerate said:
How do I change the permission?
Click to expand...
Click to collapse
use attached RootExplorer
after you replace the file in place just remark it with long press with mouse.. then go to the top righ of the program and choice permission in windows open you can just right 0644 then hit OK
frake50 said:
use attached RootExplorer
after you replace the file in place just remark it with long press with mouse.. then go to the top righ of the program and choice permission in windows open you can just right 0644 then hit OK
Click to expand...
Click to collapse
No success
Remotes still acting the same way.
Well, in one way I've resolved this, but without resolving the problem.
I can't fix the blue tooth standard remote problem. I think i may have screwed something up when I was short circuiting the mother board.
However, purchasing an android remote that uses a usb reciever does the trick. I bought one of thoseveral android keyboard remotes. It works perfectly fine, only issue is I can't power on and off with the remote. I have to pull the power out or switch it off and on by the wall.
However there is another remote with a power button, I presume it would be able to power on and off. I'll mention this incase in future anyone has this issue.
Xdegenerate said:
well, the first link worked. It's booted up. Only problem is, the remote doesnt respond, it only allows me to push down. I installed the next one successfully too, but same problem. The remote only allows a down navigation. Pressing anything else won't work.
Keyboard and mouse respond just fine.
I've tried changing the remote files, even tried the Beelink one, but none of them are working.
I've tried two remotes, both doo the same thing.
The firmware is rooted.
One thing I'm seeing is a notification saying the SU binary needs updating. However the link I downloaded it from says not to, as it will cause a boot loop.
I'm wondering if perhaps when I opened the box and shorted it to read to usb burner, if maybe I damaged the reciever or something? However, when pressing buttons on the remote, pressing up does change the blue light to red on the box, so it is recieving something, just not doing what it should.
But pressing left or right does not change the light.
Edit. I've just discovered pressing up is actually being used as the return key, it backs out of apps.
None of the 4 files, or the Beelink file fix the issue.
Click to expand...
Click to collapse
What file did you use to get your box working again? I believe I am in the same boat as you on this and could use a life raft. Trying alternate imgs for other boxes is where I am at, as all images I find for this box (aside from one labeled red and black) will not copy to the box and get stuck at 7%.
If you have any pointers at all I would love to see some life back in this box. All I wanted was to update to 7.1. Damn.....
dwoycheshen said:
What file did you use to get your box working again? I believe I am in the same boat as you on this and could use a life raft. Trying alternate imgs for other boxes is where I am at, as all images I find for this box (aside from one labeled red and black) will not copy to the box and get stuck at 7%.
If you have any pointers at all I would love to see some life back in this box. All I wanted was to update to 7.1. Damn.....
Click to expand...
Click to collapse
Try my customised ROM, I have this installed on my MXQ pro 4K (1gb RAM), runs well, has drivers for my strange clone wifi chip (ethernet works better than the clone realtek wifi chip), Its minimal and de bloated and i have a new version coming probably tomorrow wich looks better, removed the purple ect... let me know how you get on, some advice oce through initial set up, go to settings, apps, and disable chromecast, then reboot, or it will fill your internal storage & my remote dont work, i use a usb wireless and also use the tv remote through CEC
New Versoin 6 added with many improvments updated 12/05/2202
https://forum.xda-developers.com/android-stick--console-computers/amlogic/rom-android-tv-custom-rom-7-1-2-s905x-t4098131
Hi.
Yesterday I've recived my ordered Vontar. I was not a fan of the system so i changed it via sd card. I've done it a couple of times with different ones but it something strange happened. Now, when i turn on this device with a 'reset' button and a sd card in it, it won't show 'updating' screen. In fact, I can't even go to 'apply update from ext' - the 7z file won't show under this option. But, I can install TWRP from Slimbox therad and wipe all. Also i tried to 'install' img file via TWRP but in the end it show 'System not installed'. I checked all the comments in this section but i found no answers. I think that's the only place for me to receive help because i was searching the web for 5 hours and now i'm out of ideas. I'm using custom roms on my phone since 2015 but this tv boxes are new to me.
Please help me.
Thanks in advance.
andreyGM said:
Hi.
Yesterday I've recived my ordered Vontar. I was not a fan of the system so i changed it via sd card. I've done it a couple of times with different ones but it something strange happened. Now, when i turn on this device with a 'reset' button and a sd card in it, it won't show 'updating' screen. In fact, I can't even go to 'apply update from ext' - the 7z file won't show under this option. But, I can install TWRP from Slimbox therad and wipe all. Also i tried to 'install' img file via TWRP but in the end it show 'System not installed'. I checked all the comments in this section but i found no answers. I think that's the only place for me to receive help because i was searching the web for 5 hours and now i'm out of ideas. I'm using custom roms on my phone since 2015 but this tv boxes are new to me.
Please help me.
Thanks in advance.
Click to expand...
Click to collapse
This usually indicate that either the bootloader is not compatible, The DTB dosnt have the right gpio pins assigned to the reset button making it non functional among other reasons, i Strongly advise against using an SD card to try new firmwares as you can end up in a situation like this where your box is semi broken with no way to get out of it, you should buy/obtain a USB A Male to USB A Male Cable & Use USB Burning Tool As This Is How to Recover From a Bad Flash & Not 100% Compatible Firmwares and even recover a "Bricked Box" that looks like it wont even power on (no LED or output to TV), Been Using This Method For Years And Havent Bricked A Box Beyond Repair Yet
aidanmacgregor said:
This usually indicate that either the bootloader is not compatible, The DTB dosnt have the right gpio pins assigned to the reset button making it non functional among other reasons, i Strongly advise against using an SD card to try new firmwares as you can end up in a situation like this where your box is semi broken with no way to get out of it, you should buy/obtain a USB A Male to USB A Male Cable & Use USB Burning Tool As This Is How to Recover From a Bad Flash & Not 100% Compatible Firmwares and even recover a "Bricked Box" that looks like it wont even power on (no LED or output to TV), Been Using This Method For Years And Havent Bricked A Box Beyond Repair Yet
Click to expand...
Click to collapse
Thanks for an advice. Yesterday i was very scared because of this situation. I thought that i wasted about 50$ but now i'm more chilled. Somewhere i've read that Vontar is basically the same as for example as HK1 but installing it's OS was not a great idea (I've done similar things on my Huawei G620s with the similar phone OS). I will try the USB method and reply the result. My ordered cable will be in a few days. Again, thanks for a reply. This thread could be useful if someone will have the same problem like me.
andreyGM said:
Thanks for an advice. Yesterday i was very scared because of this situation. I thought that i wasted about 50$ but now i'm more chilled. Somewhere i've read that Vontar is basically the same as for example as HK1 but installing it's OS was not a great idea (I've done similar things on my Huawei G620s with the similar phone OS). I will try the USB method and reply the result. My ordered cable will be in a few days. Again, thanks for a reply. This thread could be useful if someone will have the same problem like me.
Click to expand...
Click to collapse
Good Luck & Let Us Know How You Get On
aidanmacgregor said:
Good Luck & Let Us Know How You Get On
Click to expand...
Click to collapse
Like You said. Two minutes and Vontar is running a new OS without any problems. My SD card will come back to my car as a navigation. Thank You.
Hi.
I tried flashing a rom on a H96 Pro Plus 3+32GB box with an Amlogic S912, chip.
First couple of times when i tried flashing, it went up to 3-4% and gave out an error. Then i unchecked the erase flash and erase bootloader options and it went to 8% and then gave out an error once again.
After a couple of tries with the erase bootloader and erase flash options. It succeded flashing. But when i plugged in the box. There was no picture, there was just a blue light on the box.
The computer won't recognize the box after that, i've tried putting a rom on a SDcard, i've tried shorting some pins, not sure if they were the correct ones, but no luck. There is power going to the box, the blue light is on, but it won't turn on or display any signal.
Please help!
Thanks in advance!
Hi if you just search u would find the answer faster than writing this thread
anyway
hopefully it will help
other wise you should give more detailed and explained info
mazjed said:
Hi if you just search u would find the answer faster than writing this thread
anyway
hopefully it will help
other wise you should give more detailed and explained info
Click to expand...
Click to collapse
Hi.
Trust me i've searched for a week without any success. Unfortunately the video didn't help me since my problem currently is that the box is getting power but there is no hdmi signal, nor the box is getting recognized by the pc after flashing the rom.
Thanks for trying to help.
then the only chance you have is the short method
mazjed said:
then the only chance you have is the short method
Click to expand...
Click to collapse
Hi
I tried shorting pins, like in the tutorial but nothing happened. Not getting recognized still.
Hi
Ok, so i've fixed the tv box and it turns out i was doing something wrong. I didn't have power plugging it in. I was relying on the usb connection to give enough power to the box. I've done this to get back the box. Please if you don't know what you are doing, get someone that really knows. I'm not responsible for any damage that may happen. This is just what i've done to recover the box.
1. Hold the reset button on the box
2. Plug in USB in the pc and in the box
3. Wait 2 seconds and then plug in power.
4. Hold the 5th and 6th pin (i think). Please watch the video andmake sure that you know what you are doing, since 1 bad move could render the box totally unusable. Thanks. you should hold the pins for a couple of seconds and it should pop up
Also i wasn't able to install Aidenrom (while flashing it gives out an error) or Atvexperience (it cant get imported by usb burning tool)
I reinstalled the default rom. And i was using USB Burning Tool V 2.0.8
Thanks for your help.