Hi guys. Ralekdev, Rebellos and Myself have become quite good at hacking the extra roxor out of Samsung devices. We started with The UnBrickable Mod which now spans 15 total devices on the Samsung Galaxy S series. The UnBrickable Mod turned the Galaxy S into a development board. So we moved on to sucessfuly hacking the Qualcomm bootloaders on the Verizon Galaxy S3 and while our exploits for this device have not yet been needed, we have them ready to deploy on several devices and we've learned alot. Today we would like to present to you:
UnBrickable SD-The ultimate in Exynos Necromancy
The UnBrickable SD allows for total resurrection of an otherwise hard-bricked and dead device. It takes a device-specific SDCard, and a jumper to be placed across a tiny resistor. This triggers the device to silently boot at which point it will count to 10 and reload the device's bootloaders. This uses Samsung Official firmware unlike UnBrickable SD Mod (unreleased as of the time of this post) which allows for dual-booting of custom and official.
Why would I need this?
The processor has a small bit of ROM called IROM that tries to initialize the EMMC to load SBOOT. SBOOT then fully initializes the EMMC(Internal and soldered down MMC chip) where it pulls boot parameters, partition tables and all other information for the device to boot. if the SBOOT is damaged, the device will no longer boot and Odin/Factory modes are destroyed and the device is hard-bricked. This failed boot means the device cannot function and is locked up.
How does UnBrickable SD work?
The UnBrickable SD works because the processor is configured to attempt to load SBOOT from EMMC and then fail-over to SD, and finally UART. We've prepared an SDCard via the sdcard command in SBOOT below. By disabling the EMMC during the IROM sequence, this device will automatically fail-over to SDCard boot, check the signatures, see a valid image, and reload the SBOOT onto the EMMC thus enabling Odin.
Instructions
You will need:
The SDCard Image: http://d-h.st/KIV
The Partition Information Table(PIT file)
The Odin Firmware(Heimdall one-click coming soon) http://forum.xda-developers.com/showthread.php?t=2006138
Samsung Kies (for its drivers) http://www.samsung.com/us/kies/
Once you have the required tools, we can begin the procedure.
Create your UnBrickable SD.
Unzip the SDCard Image file from the zip.
Write it to an SDCard
Linux:
Code:
sudo dd if=GCAM-bootable-odin-from-sd-60mb-DDimg.img of=/dev/MYDEVICE
where MYDEVICE is the sdcard (usually SDB or SDC
Windows: use this tool https://launchpad.net/win32-image-writer/ . I'm not going to explain because I use Linux.
Disassemble the device
I've prepared this video which shows how to disassemble the device. You can stop after you remove the LCD. Just pull the EM shields off after that so you can access the resistor.
Insert the SDCard
If you need instructions, you should have stopped long ago
Short the EMMC Resistor
You can use a pair of tweezers or a piece of wire, really anything to conduct electricity from one side of the resistor to the other. Below you can see some needles connected by a piece of wire which I use to short this resistor.
{
"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"
}
Press the power button wait a couple of seconds and release the short
While booting, the device provides a 10 second countdown on the UART2 port. during this 10 second countdown, the EMMC needs to become enabled in order to write the bootloaders back to the device. The entire process takes 30 seconds and you will see nothing on the screen.
Flash with Odin
This procedure is the same as shown in the video below, however you will put the firmware from above in the PDA section instead of CF-AutoRoot and put the PIT from above into the PIT section
Conclusion
You have sucessfully restored your device to stock condition. Please hit the thanks button below this post.
Additional Resources
[R&D] Port SDCard Recovery to Other Exynos4412 Devices: http://forum.xda-developers.com/showthread.php?t=1986887
Would you like to see the UnBrickable SD on your Exynos4 device (GS2, GNote, Gnote2)? I need a working device and a broken device to develop and test.
So similar procedure will also work on Galaxy S3 ?
drraptor said:
So similar procedure will also work on Galaxy S3 ?
Click to expand...
Click to collapse
Yes. the same procedure will work on the S3. I'm also working on bringing this to other devices as well.
What kind of image do you use for restoring the device? Just the stock one? 'Cause I (think) I saw you using a Ubuntu image on the Nexus 7...
u mentioned in the post that 15 devices of galaxy s series support this unbrickable mod which are those 15 devices? is Samsung Galaxy S i9003 included in this list or support this unbrickable mod and does all the the devices have the same procedure to use the unbrickable mod?
mfsr98 said:
What kind of image do you use for restoring the device? Just the stock one? 'Cause I (think) I saw you using a Ubuntu image on the Nexus 7...
Click to expand...
Click to collapse
I made the image using the working device using a UART connection. It consists of an official, Samsung signed SBOOT image that reloads SBOOT onto the EMMC.
pratik_s said:
u mentioned in the post that 15 devices of galaxy s series support this unbrickable mod which are those 15 devices? is Samsung Galaxy S i9003 included in this list or support this unbrickable mod and does all the the devices have the same procedure to use the unbrickable mod?
Click to expand...
Click to collapse
Nope. We only support Samsung Processors. Not OMAP or even Qualcomm for that matter.
AdamOutler said:
I made the image using the working device using a UART connection. It consists of an official, Samsung signed SBOOT image that reloads SBOOT onto the EMMC.
Nope. We only support Samsung Processors. Not OMAP or even Qualcomm for that matter.
Click to expand...
Click to collapse
is there any chance of getting this mod for i9003 in future?
pratik_s said:
is there any chance of getting this mod for i9003 in future?
Click to expand...
Click to collapse
I'm not working on it and I have no plans to do so.
AdamOutler said:
Yes. the same procedure will work on the S3. I'm also working on bringing this to other devices as well.
Click to expand...
Click to collapse
Is it working on galaxy S 2 ?
Sent from my GT-I9100 using xda app-developers app
drraptor said:
Is it working on galaxy S 2 ?
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Nope. I need a device. read the inital post.
great
i had to use this method on my Mk1 Galaxy Tab, worked like a dream..
ill be honest it stretched my hardware altering skills to the limit, always goot to keep learning.
Now i just need to actually buy a Galaxy Camera.. suppose i should make sure its a good shooter first !!
Thanks for your endless skills Adam.
Awsome! But do i just put the GCAM-UnBrickable zip file on my sd card? but how will it work if i brick my SG3 and i cant turn anything on? im sorry if its a dumb question, but i dont understand lol
terminal 7 said:
i had to use this method on my Mk1 Galaxy Tab, worked like a dream..
ill be honest it stretched my hardware altering skills to the limit, always goot to keep learning.
Now i just need to actually buy a Galaxy Camera.. suppose i should make sure its a good shooter first !!
Thanks for your endless skills Adam.
Click to expand...
Click to collapse
Are you talking about UnBrickable Mod? This is a bit different. This is a temporary mod and uses SDCard instead of USB.
Guzup said:
Awsome! But do i just put the GCAM-UnBrickable zip file on my sd card? but how will it work if i brick my SG3 and i cant turn anything on? im sorry if its a dumb question, but i dont understand lol
Click to expand...
Click to collapse
follow the instructions. you need to image the card with the image file in the zip.
Hi Adam...
Thank you for your idea,,,,,
But,This is released for officially use samsung service centers.....So.I Think no news here
I Know Your Topic is for Exynos4412 But if you want,i can send you any other SW method for repair many phone witout jtag,
like P7500,P7510,P5100,P5110,P3xxx.,Also I9300 SD_Method....I9250,I9100G,I9020,I9023,etc
Anyway,Thanks for help other pepole
But,Possible for bad understand me? can you explain me for more detail..?
Thank you
(i have any phone in my shop,"work and dead",so if you want,just tell me),Also i'm Product Supporter of "RIFF-BOX"...So,I can check everyting(Possible and supported CPU) with Jtag,,,,
BABAK236 said:
Hi Adam...
Thank you for your idea,,,,,
But,This is released for officially use samsung service centers.....So.I Think no news here
I Know Your Topic is for Exynos4412 But if you want,i can send you any other SW method for repair many phone witout jtag,
like P7500,P7510,P5100,P5110,P3xxx.,Also I9300 SD_Method....I9250,I9100G,I9020,I9023,etc
Anyway,Thanks for help other pepole
But,Possible for bad understand me? can you explain me for more detail..?
Thank you
(i have any phone in my shop,"work and dead",so if you want,just tell me),Also i'm Product Supporter of "RIFF-BOX"...So,I can check everyting(Possible and supported CPU) with Jtag,,,,
Click to expand...
Click to collapse
This isn't i9020/9023, which I designed the UnBrickable Resurrector for repair. This is an undocumented procedure. This isn't NVFlash from those Tegra based devices. This isn't the i9250 and i9100 which use the OMAP specific tool. This isn't JTAG either, I have a box.
The most similar method was released for i9300 but the T-Flash method has never worked properly for myself or others. This is something which did not exist before the first post in this thread.
Keep this in your repair bookmarks for when you need it along side your Riff box. Riff takes 6 wires generally. Every one of the 16 solutions I've come up with has been 1 or less.
How do I image a sdcard? And If my device gets bricked I just pop the card in and power it on? when I image the card will it do something special to the card? Or can i still use it to store stuff on.
Sent from my GT-I9300 using xda premium
Guzup said:
How do I image a sdcard? And If my device gets bricked I just pop the card in and power it on? when I image the card will it do something special to the card? Or can i still use it to store stuff on.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Most of your questions are already answered in the OP. (commands, revive instructions etc.)
Can the sd still be used? No. There is ARM code and a boot image copied to the beginning of your SDCard. This procedure will destroy the file system metadata although, physically, all the files are still present but not accessable anymore.
@Adam
By disabling the EMMC during the IROM sequence, this device will automatically fail-over to SDCard boot
Click to expand...
Click to collapse
Is this what shorting the resistors actualy does?
We've prepared an SDCard via the sdcard command in SBOOT below
Click to expand...
Click to collapse
So the T-Flash Option in Odin basically uses this sdcard command to create the bootloader sd?
Hi Adam
I Want Just helping You.....
So,I think you don't need
Anyway,Thanks
theq86 said:
Is this what shorting the resistors actualy does?
So the T-Flash Option in Odin basically uses this sdcard command to create the bootloader sd?
Click to expand...
Click to collapse
Yes. Shorting the resistor disables the EMMC. The TFlash works differently.
This is different from TFlash. Using TFlash you insert a boot loader from your computer and flash it to the device with Odin. The TFlash is supposed to create a boot loader from an sboot.bin.tar.md5. It has problems and seems not to work... Like ever..
I know the first few posts said the mod will work on the s3.. but since the US versions don't have exynos, I have to ask will this work on the US versions? Including Verizon?
Related
Hey guys.. This tool will recover your bricked Nexus S after a bad firmware update. If your phone is showing anything on-screen, this tool is not for you. Don't forget to hit the donate button .. hey, it's Christmas and my kid could use some extra toys. Note: 1/2 of any donations received from the UnBrickable are split with Rebellos for firmware development.
Introduction
Last night I received a PM that Nexus S devices were getting bricked after applying a T-Mobile update. I responded by creating Revision 37 of the UnBrickable Resurrector. Rebellos and I have developed a software solution to get bootloaders back on what would otherwise be a Hard Bricked (or lucky bricked) Nexus S.
You Will Need
You will need some software on your computer to get started. Here's what you need
Ubuntu running on your computer- Get Ubuntu here: http://ubuntu.com/download
Team Hummingmod's UnBrickable Resurrector R38 or higher- http://code.google.com/p/hummingbird-hibl/downloads/list
The latest version of Java- http://java.com/en/download/installed.jsp
Software Based Resurrection
Now that we have all the prerequisites taken care of, let's resurrect your device.
In Ubuntu, right-click the UnBrickableResurrectorR38.jar, click properties>Permissions>"Allow executing file as program"
Plug in your Nexus S
Right-click the resurrector, open with Java, and observe the following image
{
"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"
}
Select "S5PC110 (Nexus S) from the drop-down box.
Click the Download Mode button. The resurrector will ask for a password to access the Linux device.
Enter your password, then hold the proper key combination on your device to access Fastboot or Download Mode.
Depending on the button combination you hold, your device will end up in Fastboot or Download Mode. For Download Mode you can use Heimdall or create a Windows Virtual Machine and launch Odin. Fastboot may be easier to use for you. See other threads in this forum for loading software in Fastboot or Download Mode.
Please note, I do not own a Nexus S, so please follow the advice and answers of others who help you with your particular model in this thread.
See here for more information: http://forum.xda-developers.com/showthread.php?t=1396056
Great work Adam, glad to see you here!
Google Nexus S 4.0.3
I screwed up my bootloader.img and it courrupted boot partition. When I use the tool, I just get booted back into Android and can not do anything with ROM Manager
Any suggestions?
AndroidUser00110001 said:
I screwed up my bootloader.img and it courrupted boot partition. When I use the tool, I just get booted back into Android and can not do anything with ROM Manager
Any suggestions?
Click to expand...
Click to collapse
Hold a key combination while using the UnBrickable Resurrector
AdamOutler said:
Hold a key combination while using the UnBrickable Resurrector
Click to expand...
Click to collapse
What do you mean by that? What key combo? I have the android shoveling dirt now and looking for the images to use with odin.
wow adam! i havent hard bricked my phone but i love this.i love to have as many backup or recovery options as possible,thanks alot bud and i will certainly donate next payday and i hope others do also.
Excellent work Adam
Though i am not in need of it, since my phone is not bricked.
But this dedicated thread will definitely help those who have bricked their phones, and stop them from opening up multiple posts regarding the same issue.
by the way, can you update the title to include ICS firmware update, so that people searching would know exactly what the thread is about. Just a thought.
AdamOutler said:
Hey guys.. This tool will recover your bricked Nexus S after a bad firmware update. If your phone is showing anything on-screen, this tool is not for you. Don't forget to hit the donate button .. hey, it's Christmas and my kid could use some extra toys.
.
Click to expand...
Click to collapse
THANK YOU VERY MUCH!!!!
I just bricked my device, stupid me screwed up my updater script and ****ed up the boot partition
Thank you once again for this tool, totally saved me today :-D
Brilliant work!!!
Just contributed to your justifications to your wife of your time spent on phones.
cant open the file?
please help :..(
"The file '/home/ubuntu/Downloads/UnBrickableResurrectorR38.jar' is not marked as executable. If this was downloaded or copied from an untrusted source, it may be dangerous to run. For more details, read about the executable bit."
garner said:
cant open the file?
please help :..(
"The file '/home/ubuntu/Downloads/UnBrickableResurrectorR38.jar' is not marked as executable. If this was downloaded or copied from an untrusted source, it may be dangerous to run. For more details, read about the executable bit."
Click to expand...
Click to collapse
You skipped stage number one
cyberalex88 said:
You skipped stage number one
Click to expand...
Click to collapse
sorry im a nood in linux
---------- Post added at 11:45 AM ---------- Previous post was at 11:36 AM ----------
Oh god :..( device not found, totally stuck
garner said:
sorry im a nood in linux
---------- Post added at 11:45 AM ---------- Previous post was at 11:36 AM ----------
Oh god :..( device not found, totally stuck
Click to expand...
Click to collapse
Generally, use of the UnBrickable Resurrector requires a hardware modification. Open the phone, remove the xOM5 resistor and make the xOM5 value high instead of low. I'd like a chance to document the modification on the Nexus S. If you'd like to send it to me I can resurrect it for the price of shipping. Send me a PM.
AdamOutler said:
Generally, use of the UnBrickable Resurrector requires a hardware modification. Open the phone, remove the xOM5 resistor and make the xOM5 value high instead of low. I'd like a chance to document the modification on the Nexus S. If you'd like to send it to me I can resurrect it for the price of shipping. Send me a PM.
Click to expand...
Click to collapse
So this makes me -and all the others who could resurrect their phone- even MORE lucky, doesn't it...
AdamOutler said:
Generally, use of the UnBrickable Resurrector requires a hardware modification. Open the phone, remove the xOM5 resistor and make the xOM5 value high instead of low. I'd like a chance to document the modification on the Nexus S. If you'd like to send it to me I can resurrect it for the price of shipping. Send me a PM.
Click to expand...
Click to collapse
thanks for your reply
I have got your resurrector working it does something to my phone where it shows that its charging then it boots into ics but when i disconnect the usb lead it switches off and does not boot? any help anyone?
garner said:
thanks for your reply
I have got your resurrector working it does something to my phone where it shows that its charging then it boots into ics but when i disconnect the usb lead it switches off and does not boot? any help anyone?
Click to expand...
Click to collapse
I had that problem yesterday. After you run program, plug phone into usb cable, hold button combo as you normally would to get into the bootloader, when bootloader comes up you can use fastboot from linux or boot into windows to use fastboot to repair your boot.img and bootloader.img. Do not unplug phone if you are going to reboot into windows.
Talk about someone really helping the community in a pinch. This is huge, cause I know there's gonna be a lot of inexperienced users out there freaking out. Great job dude
Hi Adam,
thank you... you saved my phone and all my data stored in!
I'm a Windows user so I installed Ubuntu "inside" Windows, I follow all the steps pressing the two volume buttons during resurrection (in order to activate the download mode), then I reboot in Windows where Odin did the rest.
Merry Christmas!
I'm not with my phone in hands now, but I'll check this solution when i get home. Just bricked my phone yesterday due to an update from gingerbread to ics. I can't see anything on my screen, even the keys are not working. I hope your solution does the trick. Thanks in advance.
WARNING: This should be the VERY VERY VERY VERY (Am I clear enough about this?) LAST thing you do to try and fix a chromecast. This can possibly fry a chromecast for good, so know going into this that it may not work!
Because of this, Me, XDA, and all other users are NOT RESPONSIBLE for any damage, problems, or issues that may arise from using this method. By using this tutorial, you agree and understand the above warning.
So, I had a Chromecast that I got stuck in "backupsys" boot mode, where it would try to boot the backupsys partition. Issue is, it would not boot, and you can't force it to boot from jumpdrive while it is in "recovery" or "backupsys" mode.
Well after tearing the thing down and getting UART setup, I started messing around, and found a way to FORCE the device to read from USB, regardless to the bootmode.
How this works is during the boot process, you jump 2 select pins on the PCB by the CPU, which causes the device to have a block read error while reading the system flash. When this happens, the device falls back into USB read mode.
Because this causes a read interrupt, it "MAY" have unknown effects on the longevity of your device, so like I said before, this should be a LAST RESORT OPTION ONLY.
What You Need:
Chromecast with Rootable Bootloader
Paper Clip/Needle to jump some TINY pins
UART hooked up to your computer
Jump Drive with the Root Image & USB OTG Cable
Process:
Step 1: Tear down your device, and have it hooked up to UART on your computer.
Step 2: Have the USB OTG Cable and Jump Drive with the root image plugged into the chromecast. Do not have it plugged into power yet.
Step 3: On the top side of the chromecast (Not the side with the UART Pins), carefully remove the RF shield to reveal the WiFi Chip and CPU.
{
"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"
}
Step 4: Have putty open and connected to your UART COM port. Also have "reboot recovery" in your clipboard. (Copy that command so you can right-click in putty to send it quick)
Step 5: Now, prepare to jump pin #26 (shown in photo below, marked with red square on right side of CPU) when you plug in the chromecast to power it.
Step 6: Plug in the chromecast power, and watch the UART output. Once the Chromecast LED turns read, use the paper clip to short pin #26 and you should get the following outout:
Code:
sys_init start. boot_strap=0x00000080 (source=NAND), boot_state=0x0
PG868: leakage=208 vcore=10 sysctl=59
Customer key found, loading customer key...
Loading Secure Customer Key Store is finished
Loading Secure Customer Key Store is finished
Finish loading Customer Key store
bootloader image verified, start...
eureka-b3 BG2CD [Jun 6 2013 12:07:51] ver:9086b04-dirty
OTP status=0x000000FF lkg curr=208 mA
nand_randomizer_init_by_flash_type(chip_id = 0x2C48044AA500): !!! RANDOMIZED !!!
[FASTLOGO] init.
[FASTLOGO] Set CPCB1 output reso 8.[SHOWLOGO] start
showlogo_init_irq, Enable IRQ_dHubIntrAvio0(0x20) for cpu 0
[FASTLOGO] done.
fts: v155 loaded from 0x00268000
Read failed @ 0x7814c000
ERROR: Failed to read CPU image ret -1
Booting from NAND failed, booting from USB....!
timer_clk_freq = 0x47868c0
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 2 USB Device(s) found
scanning bus for storage devices... 1 Storage Device(s) found
If you do not see "Booting from NAND failed, booting from USB....!", unplug the chromecast, and try again.
Step 7: The chromecast will now try and boot the Jump Drive image. During this, there will be a root shell hiding under all the output. You need to QUICKLY and repeatedly press Enter until you see "/ # " flash on the screen. Once you see that flash, QUICKLY press right-click so putty pastes your clipboard, and then press enter. If you do this fast enough, the kernel will run "reboot recovery" and restart.
Step 8: The device will now try to boot the normal recovery partition. This is fine, because even if it fails, the bootloader will detect this and reset the device to normal boot mode after a few power cycles. After a few power cycles, the chromecast should eventually show the following over UART:
Code:
sys_init start. boot_strap=0x00000080 (source=NAND), boot_state=0x0
PG868: leakage=208 vcore=10 sysctl=59
Customer key found, loading customer key...
Loading Secure Customer Key Store is finished
Loading Secure Customer Key Store is finished
Finish loading Customer Key store
bootloader image verified, start...
eureka-b3 BG2CD [Jun 6 2013 12:07:51] ver:9086b04-dirty
OTP status=0x000000FF lkg curr=208 mA
nand_randomizer_init_by_flash_type(chip_id = 0x2C48044AA500): !!! RANDOMIZED !!!
[FASTLOGO] init.
[FASTLOGO] Set CPCB1 output reso 8.[SHOWLOGO] start
showlogo_init_irq, Enable IRQ_dHubIntrAvio0(0x20) for cpu 0
[FASTLOGO] done.
fts: v168 loaded from 0x0029c000
[SHOWLOGO] stopped
Boot normal GTV image
fts: record v169 commited @ 0x002a0000
Uncompressing Linux... done, booting the kernel.
And congrats, the device is now back to Normal Boot Mode! You can now hold the power button during power on to properly flash the rooted image, and your device should be good to go!
DEVS: If you want to help make this easier, can you make a USB image that just boots the kernel and stops at command line? Would make this process easier.
FAQ:
Q: Why do I need this? I can just hold down the button to boot from a Jump Drive.
A: This is true, but if a Chromecast is in any other boot mode besides normal, then it will be unable to boot from USB. This is just how the bootloader is coded. (I submitted a patch to google regarding this, even though it would never help us out thanks to the updated locked bootloader).
Q: Will this allow be to Downgrade/Root my device?
A: Answer is Probably not, even though this is untested. This is because the bootloader is still loading from the device, so it will still probably check the USB Drives image for a valid signature.
Q: I tried this, but my device still won't boot.
A: Well then there is probably not much else you can do, besides looking for a fix yourself. Remember, its a $35 dollar device so it may just be best to buy a new one.
Reserved
This reminds me of what people did for the xbox 360 with the dual nand chips, or what Adam Outler did with the galaxy camera. He had a switch that would choose whether to boot the default eMMC or a SD card.
Aaron Swartz, Rest in Pixels.
ddggttff3 said:
Reserved
Click to expand...
Click to collapse
Can you explain why you chose pin 26?
Thanks
zackoch said:
Can you explain why you chose pin 26?
Thanks
Click to expand...
Click to collapse
In all honesty, trial and error with a device I didn't think would ever work again.
EDIT: Also, getting very very lucky.
jamcar said:
This reminds me of what people did for the xbox 360 with the dual nand chips, or what Adam Outler did with the galaxy camera. He had a switch that would choose whether to boot the default eMMC or a SD card.
Aaron Swartz, Rest in Pixels.
Click to expand...
Click to collapse
In case anyone didn't pick on my meaning, it would be cool if we could use a switch to boot from USB or eMMC.
Aaron Swartz, Rest in Pixels.
jamcar said:
In case anyone didn't pick on my meaning, it would be cool if we could use a switch to boot from USB or eMMC.
Aaron Swartz, Rest in Pixels.
Click to expand...
Click to collapse
technically this may be possible, but I am not a developer but don't quote me. The fact that we can load a kernel off a jump drive though should mean we have the ability to load and run a system image off of a jump drive.
I just got a second chromecast and am awaiting my USB OTG power cable, I do plan to root this one and work on seeing if my idea is possible.
Aaron Swartz, Rest in Pixels.
How did you get the remainder of the shield off? I got the covers off but I can't get the shield off.
EDIT: I got it. Another question: do you leave your chromecast "naked" or?
jamcar said:
How did you get the remainder of the shield off? I got the covers off but I can't get the shield off.
EDIT: I got it. Another question: do you leave your chromecast "naked" or?
Click to expand...
Click to collapse
You should put the RF shields back on after you do this modification, as they prevent interference and issues. During the dissection of my device though, I fully removed the shields (including the sides), so I have no choice but to run that one naked, but it is sitting on the side as I have another rooted chromecast I use for day to day usage.
Short pin 26 to Ground?
Sent from my XT897 using XDA Premium 4 mobile app
rbeavers said:
Short pin 26 to Ground?
Sent from my XT897 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
To be more clear, you should jump both pins at point 26. I am planning on re-doing this thread now that flashcast is out, and can make this a hell of a lot easier.
Have not used my chromecast since I bought it, prob early August. Used it the first day and put it back in the box. Decided to play with it again and root it. Problem is as soon as you plug it into the TV it starts to update (have/had wifi off just in case). So I assume it downloaded the update way back when I first used it. Not sure if this update patches the root exploit or not and I don't want to find out. Will this method get make out of "update mode"? Anything else I can try? You mentioned Flashcast any way to use it?
Thanks
BB
Bad Bimr said:
Have not used my chromecast since I bought it, prob early August. Used it the first day and put it back in the box. Decided to play with it again and root it. Problem is as soon as you plug it into the TV it starts to update (have/had wifi off just in case). So I assume it downloaded the update way back when I first used it. Not sure if this update patches the root exploit or not and I don't want to find out. Will this method get make out of "update mode"? Anything else I can try? You mentioned Flashcast any way to use it?
Thanks
BB
Click to expand...
Click to collapse
First off, any official OTA for the chomecast will patch the root exploit, so if that update goes through you will be unable to root your chromecast.
As for this method working for you, if you follow the jumping method as stated in OP, then yes, this method would force your chromecast to boot from the USB Cable.
As for using flashcast, thanks to tchebb's help, if you just boot flashcast 1.1.1 on a jumpdrive, it will automatically delete the OTA from the device, and reset the boot mode back to normal. So the need to use UART is no longer required!
ddggttff3 said:
First off, any official OTA for the chomecast will patch the root exploit, so if that update goes through you will be unable to root your chromecast.
As for this method working for you, if you follow the jumping method as stated in OP, then yes, this method would force your chromecast to boot from the USB Cable.
As for using flashcast, thanks to tchebb's help, if you just boot flashcast 1.1.1 on a jumpdrive, it will automatically delete the OTA from the device, and reset the boot mode back to normal. So the need to use UART is no longer required!
Click to expand...
Click to collapse
I've tried doing the root method posted here:
http://forum.xda-developers.com/showthread.php?t=2529903
When I connect the CS to the usb side of the OTG cable it flashs red and then white and that's it.
Might I be doing something wrong?
Thanks
BB
Bad Bimr said:
I've tried doing the root method posted here:
http://forum.xda-developers.com/showthread.php?t=2529903
When I connect the CS to the usb side of the OTG cable it flashs red and then white and that's it.
Might I be doing something wrong?
Thanks
BB
Click to expand...
Click to collapse
Is your device rootable? if it has taken any official google OTA yet, then the device will be unable to use or boot flashcast as google patched the root exploit.
Next time please try to keep questions to the relevant thread, thanks.
ddggttff3 said:
First off, any official OTA for the chomecast will patch the root exploit, so if that update goes through you will be unable to root your chromecast.
As for this method working for you, if you follow the jumping method as stated in OP, then yes, this method would force your chromecast to boot from the USB Cable.
As for using flashcast, thanks to tchebb's help, if you just boot flashcast 1.1.1 on a jumpdrive, it will automatically delete the OTA from the device, and reset the boot mode back to normal. So the need to use UART is no longer required!
Click to expand...
Click to collapse
IIRC, in another thread it was stated that Flashcast made no changes to the Chromecast, it was just to setup the USB drive to flash the Chromcast and it was the Pwnedcast ROM that made the needed changes to prevent the OTA from taking place.
It's mentioned in this post:http://forum.xda-developers.com/showpost.php?p=46307051&postcount=124 or am I misunderstanding what you mean?
wptski said:
IIRC, in another thread it was stated that Flashcast made no changes to the Chromecast, it was just to setup the USB drive to flash the Chromcast and it was the Pwnedcast ROM that made the needed changes to prevent the OTA from taking place.
It's mentioned in this post:http://forum.xda-developers.com/showpost.php?p=46307051&postcount=124 or am I misunderstanding what you mean?
Click to expand...
Click to collapse
That is correct, flashcast makes no changes, but it DOES reset the boot mode of the device back to normal. this is done to ensure that no device gets stuck in recovery mode forever, as well as deletes /cache/ota.zip so if a official google OTA is on the device, it gets deleted.
ddggttff3 said:
That is correct, flashcast makes no changes, but it DOES reset the boot mode of the device back to normal. this is done to ensure that no device gets stuck in recovery mode forever, as well as deletes /cache/ota.zip so if a official google OTA is on the device, it gets deleted.
Click to expand...
Click to collapse
Deleting /cache/ota.zip isn't considered a change? So, if ALL that is done to a 12072 build is to setup the Flashcast USB drive, it can't be updated by Google?
wptski said:
Deleting /cache/ota.zip isn't considered a change? So, if ALL that is done to a 12072 build is to setup the Flashcast USB drive, it can't be updated by Google?
Click to expand...
Click to collapse
No, the device will still be able to update from google if flashcast is ran, flashcast just deletes any already downloaded OTA that has yet to be installed.
First few things: I've searched already, can't find any similar threads that actually help. I have the international version. I was running the CM10.2 Rom prior to 'the accident'. I will put a bounty on this if I have to.
There's a bit of a story to this so I'll go over it all - not sure what's relevant.
I've been running out of storage for days, a 64GB SD card is in the mail. I currently have an 8GB one as well as the internal 16GB, both of which were near full, but the external one had relatively more than the internal one, so I decided to use foldermount and link2SD to move some space over. That all went fairly well.
This morning I got invited to the Aviate Beta launcher, which looked interesting. Tried to install, didn't have enough space. So I decided to make a backup of Nova, go into the play store, uninstall nova to free up space and then install Aviate without leaving the playstore. It worked, turns out I don't like Aviate much, so I worked backwards. Uninstalled Aviate, went to install Nova. Not enough space (idk how). Uh oh.
So I deleted some less-necessary apps that I could reinstall later. Not enough storage. Notification comes up in the bar along the lines of "storage critically low, device may malfunction". Now whenever I attempted to enter settings, the process crashed. Great. Simple fix, flash a NANDroid back-up in CWM. I can't remember what the message was, but there was something wrong with the back-up.
Wiped everything and tried to flash CM10.2 from the external SD Card but it wouldn't mount. Data also wouldn't mount. I tried several SD Cards ( ie about 10, different brands, sizes, classes, etc out of hope). So I decided I'll open up and Odin and just re-do everything per /showthread.php?t=2387980.
Turn the phone back on, stock Jelly Bean lockscreen was there, and once unlocked only the notification bar was there (no launcher). So I used different versions of Odin, different cables, downloaded the image several times, etc etc. Nothing fixed it. In fact, it's worse now. after booting past the Samsung logo, the screen just goes black now. smh
Can anyone help? It would be extremely appreciated. It's also a time sensitive issue as I need the device for work on Monday.
Sorry if I've missed anything. Yes I'm a noob, but you great people at XDA have helped a lot of people out before so I'm hoping you can help me.
Thanks!
Sorry to bump...
... getting pretty desperate. $50 for anyone who can provide information that leads to the fixing of the device by the end of the day (AEST). Paypal or bank transfer. PM me or post below.
EDIT: 101 views and no-one knows anything? If you know it's unrecoverable, please say so.
tiskael said:
... getting pretty desperate. $50 for anyone who can provide information that leads to the fixing of the device by the end of the day (AEST). Paypal or bank transfer. PM me or post below.
EDIT: 101 views and no-one knows anything? If you know it's unrecoverable, please say so.
Click to expand...
Click to collapse
I'm going to assume you have the i9295, but have you tried Kies? I want aware that there was an Odin package for your phone.
Devo7v said:
I'm going to assume you have the i9295, but have you tried Kies? I want aware that there was an Odin package for your phone.
Click to expand...
Click to collapse
Yes, the i9295 - the international version. The Odin md5 can be found on this thread: /showthread.php?t=2387980.
Sorry if this sounds rude (it's not, I just don't know how to use kies) but what's that supposed to do? I can't find a way for Kies to fix anything... I tried this thread: /showthread.php?t=1984717 but when I have to enter my phone model (GT-i9295) it says "Please check the model name and enter it" and closes the pop-up window within kies. Any more help?
Thanks for trying so far.
Sorry for bumping but i need this fix. $100 to the first person who can fix this by Monday.
I can't possibly believe that no-one knows how to fix this, or at least whether it's fixable or not. Is anyone willing to answer my question?
Check this threads or ask the guys who helped me there, they are Awesome
So after boot you get an totally black screen? Only theorigial Samsung boot logo before it turns dark?
I had this problem twice, but can you tell me if you start the phone after the dark screen do you have sound (like the phone still works, but only no screen) or nothing?
The first time i had sound, need to say that i never solved this problem, re-installed stock firmware, (recovery still works, you only need to know wat to puch) Unrooted my phone, and send it in for waranty, They send me a new phone, never know what was the problem, it can be o broken screen, but i never believed it totally... check this thread for that: http://forum.xda-developers.com/showthread.php?t=2363185&page=9
The other time i had this i installed a other CWM Recovery Version, i had one installed, but some problems with it, installed an other version, after Reboot the Same Samsung Logo...Dark screen, installed this CWM: http://forum.xda-developers.com/attachment.php?attachmentid=2464887&d=1387533161
Good Luck with it M8
Here is something that could/couldn't help you...
I am not sure/not tested this so i am not responsible for anything that happenes to your phone
1.DOWNLOAD A STOCK FRESH SAMMY ROM FROM SAMMOBILE
2.Use odin3.7
3.Open ODIN AND CHOOSE PDA THEN CHOOSE THE FIRMWARE YOU EXTRACTED /DOWNLOADED
4.Now flash the firmware
5.When reached at the state you previsouly in reboot to download mode again and do step 3 again
6.Now download the pit file from HERE
7.In odin screen make sure 3 buttons are checked F.rest time , auto reboot , REPARTITION
8.Now choose frimware in pda
9.CHOOSE THE FILE YOU HAVE ALREADY DOWNLOADED FROM ATTACHMENT IN SIDE THE PIT BOX LIKE THE PICTURE UNDER
{
"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"
}
10.hit start and let the device flash like normal
11.it will auto reboot ...hope this fixes your issue
THE PIT FILE IS CALLED i9295.pit and is from here
HERE IS SOME INFO ABOUT PIT FILES
What are pit files ?
A pit file is a kind of file often used in samsung phones / tablets , these files contain partition tables of the device and the spaces of them with the arragment of each partition with there corresponding mount points ; these files can difenitly dangerous and can kill your tab/phone with a breeze if not used with care
Click to expand...
Click to collapse
What do pit files really do ?
Pit files can help in fixing a broken mmc for ex:
Click to expand...
Click to collapse
NOTE: I AM NOT RESPONSIBLE IF THIS WILL MAKE THINGS EVEN WORSE
make a try and let me know
try this too..
When my DATA is not mounting, i feel bad as well for in my case, i can't do what mythi's solution by flashing PIT file and stock rom using odin, coz my usb port isn't functioning anymore.. in short, my phone is just charging and not syncing to PC anymore... what i did is go to cwm, tried to mount /data there but gives me an error... what i did next is format /data and /data/media (/sdcard) then flash the new cm11 KITKAT they just finished building... reboot, waited for 2 min or so, boom my phone is back to life..
Just recently I purchased a Teclast X98 Air III 32 GB (Android 5 only) – Tablet. Immediately when holding it in my hands I hardbricked it successfully. (Oh my … )
My aim was (is) to reconfigure this tablet to dual-boot with Android and Windows.
From my reading around here and on other forums I got the impression that I am not the only one with this intention. And it seems that I am by far not the only one running into soft- and (for my case) hardbricking problems right from the first step (failed BIOS flash).
So, here is described how I did not succeed (so far):
(Oh, I am sorry for all my misuse of the English language; which has to be expected to happen. I haven’t really used this language for a while and I guess I’ve never been all too good at it. Well, as I have the impression, that there is some bunch of other German native speakers around here, they might help out, if it is running for really nasty misunderstandings … hopefully.)
I hardbricked the tablet trying to flash the BIOS to dual-boot using this (http://techtablets.com/2015/09/teclast-x98-air-iii-gets-dual-boot-bios-and-files-released/) method at TECHTablets.
As a result it’s just all dark now. No way to turn in on. No entering into DnX-Mode (pressing Power + Vol+ - Vol- all together), no answering on fastboot commands (of course not, I guess).
Next step is flashing this tablets BIOS-chip directly with an EEPROM-clip and –flasher following these instructions (http://www.android-hilfe.de/thema/teclast-tablet-unbrick-anleitung.664569/) from android-hilfe (German).
{
"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"
}
I did borrow those and I am too stupid to get the clip hold on that chip!
For the moment I hope, it’s not purely me not being able to connect that clip on that chip, but that it is the quality of that clip. Following what has been said on TECHTablets (http://techtablets.com/forum/topic/unbrick-x98-pro-bios-usb-flash/) that might be the case. So I ordered a quite expensive (for what it does) alternative clip for € 20,--, which should arrive within three days.
Supposing I haven’t just already destroyed the tablets board manually with my first tries to get the clip getting grip of that BIOS-chip, which BIOS should I flash?
I thought of flashing the 2.05 BIOS-Version from Mireks 7.0 - ROM. Is that a good idea or bad idea? Has anyone already experienced (positive) results trying this (or something else)?
The original, single-boot BIOS is shown here:
After attempting to flash the 2.02 - dual-boot - BIOS from the mentioned TECHTablets-description the tablet first booted into BIOS …
“ROM Image update denied
EFI_NOT_FOUND! Rom Image not loaded”
… I cannot remember exactly, what I did there within the BIOS itself, but it then flashed again, went off, stayed off = hardbricked.
1. You flashed 1.00 BIOS not 2.02
2. Do you have a pendrive connected when try to power on?
3. Did you charged overnight? How about the battery status?
blackbile said:
1. You flashed 1.00 BIOS not 2.02
Click to expand...
Click to collapse
Yes but no. The file I flashed was BIOS 2.02. I checked that. It doesn't really make sense. But now it shows BIOS Ver. 1.00. I saw that and have been pretty confused. Anyhow, I just messed it totally up.
2. Do you have a pendrive connected when try to power on?
Click to expand...
Click to collapse
No. Should I?
3. Did you charged overnight? How about the battery status?
Click to expand...
Click to collapse
Well, it is just totally dark. It cannot be powered on. Charged for 3 h before I tried to power it on again after the failed flashing. Nope. Darkness.
Mine is work now, but was in a state as the last photos of you, (that was if I disconnected a pendrive after flashed a bad changed BIOS - if I connected nothing happen just black screen...) in short - dont connect the pendrive.
Try to charge more and after that try to power on and step in the BIOS.
Maybe send me a link what BIOSes you tried to flash the first one is very interesting 1.00 - 2.02
blackbile said:
...
Maybe send me a link what BIOSes you tried to flash the first one is very interesting 1.00 - 2.02
Click to expand...
Click to collapse
Following TECHTablets instructions (http://techtablets.com/2015/09/teclast-x98-air-iii-gets-dual-boot-bios-and-files-released/) I downloaded from the provided link "dual system BIOS: http://pan.baidu.com/s/1kTyAH2f": http://pan.baidu.com/s/1kTyAH2f. <--!!! CAUTION! I hardbricked !!!
NO fellow!!!
Here is the version number what you flash first - from this "pan.baidu.com/s/1kTyAH2f":
Version %x.%02x.%04x. Copyright (C) 2013 American Megatrends, Inc. BIOS Date: 09/11/2015 14:54:18 Ver: tPAD100 $LGO$
So what we see on your photo that you flash 1.00 dual BIOS. After that what did you do? Did you changed the partition what seen in the mentioned Techtablets tutor?
Maybe you had to flash Windows 10 after 1.00 BIOS, but I could not help more, I have original dual boot Air 3G...
blackbile said:
...
Here is the version number what you flash first - from this "pan.baidu.com/s/1kTyAH2f":
Version %x.%02x.%04x. Copyright (C) 2013 American Megatrends, Inc. BIOS Date: 09/11/2015 14:54:18 Ver: tPAD100 $LGO$
So what we see on your photo that you flash 1.00 dual BIOS. After that what did you do? Did you changed the partition what seen in the mentioned Techtablets tutor?
Maybe you had to flash Windows 10 after 1.00 BIOS ...
Click to expand...
Click to collapse
Well, no, there was no chance to change anything like the partition table after the first step. At least there was not the possibility to follow that guide any longer. because I was stuck in the tablets BIOS and then the tablet went off ... and stays off so far.
Basically I still have the question, which BIOS I should flash now using the BIOS-chip-clip and the EEPROM-flasher mentioned in the first post.
(And if that works, after charging the battery, I would continue using DnX-mode, I guess?)
kelebek said:
Well, no, there was no chance to change anything like the partition table after the first step. At least there was not the possibility to follow that guide any longer. because I was stuck in the tablets BIOS and then the tablet went off ... and stays off so far.
Basically I still have the question, which BIOS I should flash now using the BIOS-chip-clip and the EEPROM-flasher mentioned in the first post.
(And if that works, after charging the battery, I would continue using DnX-mode, I guess?)
Click to expand...
Click to collapse
while i am not familiar with that usb programmer you used, still:
- when you flashed (write) the bios did you performed a verify at the end?
- if the verify was OK then it means you don't need another clip (should this not work the verify would have failed)
- have you disconnected the battery after the bios flashing (if it was connected) ? it is needed to reinitialize the board
- what voltage is that programmer using? to my knowledge your bios works at 1.8V so a 3.3V programmer may easily do bad stuff on your board (even if the bios verifies, which means it is in good status other components on the board will be 'touched' by the voltages)
- if you used multiple/differnet bios files i would rule out the bad bios file possibility
ionioni said:
while i am not familiar with that usb programmer you used, still:
- when you flashed (write) the bios did you performed a verify at the end?
Click to expand...
Click to collapse
I didn't get as far as programming the BIOS-chip with that programmer. (Because I couldn't make that clip get grip of that BIOS-chip.)
...
- what voltage is that programmer using? to my knowledge your bios works at 1.8V so a 3.3V programmer may easily do bad stuff on your board (even if the bios verifies, which means it is in good status other components on the board will be 'touched' by the voltages)
Click to expand...
Click to collapse
The programmers type is CH341A and I do have the impression, that it works at 3.3 - 5 V. From what I have read at android-hilfe it worked for programming an Air III anyway. And there are positive reports using this programmer with Teclasts Air 3G - tablets on android-hilfe ... and on TECHTabelts too I think.
I realized your warning about this but feel to not having too many other options. (You might possibly name a programmer, that should work here and that provides the correct voltage?)
...
Click to expand...
Click to collapse
kelebek said:
I didn't get as far as programming the BIOS-chip with that programmer. (Because I couldn't make that clip get grip of that BIOS-chip.)
Click to expand...
Click to collapse
well what can i say, on my Lenovo Yoga Tab 2 the SPI has his pins with much less exposure than what you are having on your x98 so no clip would have been good (as the lateral descending part of the pins basically were not existent, but from the pictures you posted is not your case as i can see there is area on the pins for the clip to grasp), anyways in my case i had to chose between buying an spring loaded adapter (such as this one ) or solder some wires, considering i already waited one month for my programmer to come and the adapter would have take another one i went for soldering thin wires, but this is a delicate operation and can easily destroy other stuff if you don;t have the required tools know/how
The programmers type is CH341A and I do have the impression, that it works at 3.3 - 5 V. From what I read at android-hilfe it worked for programming an Air III anyway. And there are positive reports using this programmer with Teclasts Air 3G - tablets on android-hilfe ... and on TECHTabelts too I think.
I realized your warning about this but feel to not having too many other options. (You might possibly name me a programmer, that should work here, and that provides the correct voltage?
Click to expand...
Click to collapse
hmm... what can i say, mine was a 1.8V capable programmer and yes others have programmed using a 3.3V programmer (the SPI has an absolute maximum voltage rating of Vcc + 1V = 2.8V, higher than that there's no warranty from the OEM, still 3.3 is bigger than 2.8, what can i say could work or not), but for sure a 5Vcc one will break him
Opening the x98 air iii
Hey, I'm not even at the point where you are: I can't get this thing openend. I saw a Video on android-hilfe, which shows how to open the earlier Versions of the x98, which have round corners. So how did you manage to open the tablet?
Thanks in advance!
Jonas
kelebek said:
Just recently I purchased a Teclast X98 Air III 32 GB (Android 5 only) – Tablet. Immediately when holding it in my hands I hardbricked it successfully. (Oh my … )
My aim was (is) to reconfigure this tablet to dual-boot with Android and Windows.
From my reading around here and on other forums I got the impression that I am not the only one with this intention. And it seems that I am by far not the only one running into soft- and (for my case) hardbricking problems right from the first step (failed BIOS flash).
So, here is described how I did not succeed (so far):
(Oh, I am sorry for all my misuse of the English language; which has to be expected to happen. I haven’t really used this language for a while and I guess I’ve never been all too good at it. Well, as I have the impression, that there is some bunch of other German native speakers around here, they might help out, if it is running for really nasty misunderstandings … hopefully.)
I hardbricked the tablet trying to flash the BIOS to dual-boot using this method at TECHTablets.
As a result it’s just all dark now. No way to turn in on. No entering into DnX-Mode (pressing Power + Vol+ - Vol- all together), no answering on fastboot commands (of course not, I guess).
.
Click to expand...
Click to collapse
joney94 said:
Opening the x98 air iii
... I can't get this thing openend. I saw a Video on android-hilfe, which shows how to open the earlier Versions of the x98, which have round corners. So how did you manage to open the tablet?
...
Click to expand...
Click to collapse
Are you refering to this video? -> https://www.youtube.com/watch?v=841pMJC_QOk
That worked for me, even with my Air III. Although I didn't have that plug. I used my fingernails, it took some time and a lot of patience.
I succeeded: Dual-boot, Mireks Android 5 + Windows 10.
But: I had to go the rough road with getting that BIOS on the BIOS-chip using a programmer (see opening post). Therefore I couldn't explain any easy way (without opening the tablet + using a programmer) to get it done.
kelebek said:
I succeeded: Dual-boot, Mireks Android 5 + Windows 10.
But: I had to go the rough road with getting that BIOS on the BIOS-chip using a programmer (see opening post). Therefore I couldn't explain any easy way (without opening the tablet + using a programmer) to get it done.
Click to expand...
Click to collapse
Which BIOS version you used? I have a bricked device as well and I didn´t manage to find the original bios from anywhere.. I used to have dual boot version but bricked with an update..
Edit: I am using CH341A programmer.
Edit2: After several attempts I finally found a bios that worked for me. And got my tablet working again The clip did not work with me so I had to solder pins to bios-chip to get it working.
Bios that worked for me can be found here: http://forum.xda-developers.com/showpost.php?p=64847156&postcount=603, thanks to @SkubiDoo
Dahlorna said:
Which BIOS version you used? I have a bricked device as well and I didn´t manage to find the original bios from anywhere.. I used to have dual boot version but bricked with an update..
Edit: I am using CH341A programmer.
Edit2: After several attempts I finally found a bios that worked for me. And got my tablet working again The clip did not work with me so I had to solder pins to bios-chip to get it working.
Bios that worked for me can be found here: http://forum.xda-developers.com/showpost.php?p=64847156&postcount=603, thanks to @SkubiDoo
Click to expand...
Click to collapse
this 2.05 bios is a dual boot bios?
bosondehiggs said:
this 2.05 bios is a dual boot bios?
Click to expand...
Click to collapse
Actually it is not, it is Android bios. But I was able to boot to Android partition. I haven't got the time to find right dual boot bios and flash it.
Dahlorna said:
Actually it is not, it is Android bios. But I was able to boot to Android partition. I haven't got the time to find right dual boot bios and flash it.
Click to expand...
Click to collapse
Hi, I had a brick flashing a dualboot BIOS due to a model number mistake (I need coffee please...). I fixed the problem reflashing a correct dualboot bios with this method:
http://forum.xda-developers.com/x98-air/help/baytrail-dnx-mode-bios-flashing-tool-t3295105
http://techtablets.com/2015/09/teclast-x98-air-iii-gets-dual-boot-bios-and-files-released/
bios file (I think it's dualboot 1.00) http://pan.baidu.com/s/1kTyAH2f
I flashed mirek v7 on a 8gb partition (only 4 for data) with his flashing tool, and now i'm installing win10. Yup, very slow.
melon96 said:
Hi, I had a brick flashing a dualboot BIOS due to a model number mistake (I need coffee please...). I fixed the problem reflashing a correct dualboot bios with this method:
http://forum.xda-developers.com/x98-air/help/baytrail-dnx-mode-bios-flashing-tool-t3295105
http://techtablets.com/2015/09/teclast-x98-air-iii-gets-dual-boot-bios-and-files-released/
bios file (I think it's dualboot 1.00) http://pan.baidu.com/s/1kTyAH2f
I flashed mirek v7 on a 8gb partition (only 4 for data) with his flashing tool, and now i'm installing win10. Yup, very slow.
Click to expand...
Click to collapse
Thanks! I have to try that out. Unfortunately I somehow brocked my LCD connector and no there is streaks on the screen and nothing else. :s more soldering I think..
Dahlorna said:
Which BIOS version you used? ...
Click to expand...
Click to collapse
I used the dual-boot BIOS-file from http://pan.baidu.com/s/1kTyAH2f (download). This is version 1.0. If found it mentioned on http://techtablets.com/2015/09/teclast-x98-air-iii-gets-dual-boot-bios-and-files-released/. So far it is the only dual-boot BIOS I could find for the M5C5. This BIOS major plus - from my point of view - is, that I works fine: it gave me dual-boot to Android + Windows on my M5C5.
Did you have to unplug the battery? If yes, what wire did you unsolder?
HI, I bricked my N950u after rooting with the SamV2 method for snapdragon. I rooted it fine, then tried flashing stock firmware and supersu zip. I know snapdragon is bl locked but I thought I could possibly do something besides hard brick lol. Anyway, does a rooted n950u that they could share a partial or full sys dump with me so I can make a debrick img. Also if anyone knows how to un/debrick please let me know and share. Thanks in advance!!!!
P.s. I know it was stupid to do lol
p.p.s. if your not going to contribute to the solution and or insult my foolish decision please keep your comments to yourself, thanks
You cannot debrick. What does your phone do?
EDIT: you probably are not bricked anyway. Actually you might be bricked if you flashed stock rev1 firmware instead. That would brick you...
me2151 said:
You cannot debrick. What does your phone do?
EDIT: you probably are not bricked anyway. Actually you might be bricked if you flashed stock rev1 firmware instead. That would brick you...
Click to expand...
Click to collapse
I definitely am bricked because my pc picks the phone up as "HS-USB QDLOADER 9008" i.g. hard brick. Doesnt boot into odin, no display on the phone but vibration feedback when trying odin button combo
Vell123 said:
I definitely am bricked because my pc picks the phone up as "HS-USB QDLOADER 9008" i.g. hard brick. Doesnt boot into odin, no display on the phone but vibration feedback when trying odin button combo
Click to expand...
Click to collapse
Yup. Thats 100% a hardbrick. Unfortunatly the debrick img method doesnt work on this phone. Only way to fix at this moment is a carrier swap. Thats how I got mine fixed.
me2151 said:
Yup. Thats 100% a hardbrick. Unfortunatly the debrick img method doesnt work on this phone. Only way to fix at this moment is a carrier swap. Thats how I got mine fixed.
Click to expand...
Click to collapse
Carrier swap? can you explain a bit more? But I believe if I had a system dump for the note 8 I can make a un/debrick image just like previous Samsung devices. I'm willing to try but i dont have the software needed
Vell123 said:
Carrier swap? can you explain a bit more? But I believe if I had a system dump for the note 8 I can make a un/debrick image just like previous Samsung devices. I'm willing to try but i dont have the software needed
Click to expand...
Click to collapse
Mine died in the middle of an update and when i got it back on a computer it was in 9008. Was unable to fix it. took it to my carrier as I have insurance and they replaced it.
me2151 said:
Mine died in the middle of an update and when i got it back on a computer it was in 9008. Was unable to fix it. took it to my carrier as I have insurance and they replaced it.
Click to expand...
Click to collapse
Ahhh... definately dont have insurance. But thanks is your device rooted
Long shot but... qfil / firehose msm8998 is the way to go with this. Can be done, the hard part is getting the firehose programmer (and maybe rawprogram0 / patch0 xmls too)
Isnt it supported by Z3x / Sigma / Infinity / Octoplus?
Doesnt that "aryk" site have a load of programmer files that could work with your device?
Failing that, JTAG / EMMC flash (pinouts should be around somewhere)
Sorry can`t be more help. I`m working on a similar issue with a Moto Z2 play atm
EDIT: I`m sure the 835 (what you have) supports booting from the SD card.
You need to ask someone with a rooted Snapdragon N8 to make a copy of the first 167(ish) MB of mmcblk0
Like this... (Brief idea... whoever does this needs to do it obviously from shell, on the device itself wether thats from TWRP shell or ADB in *nix / Win thats up to you)
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1024 count=168960
Once some kind soul has done this for you and you have downloaded it, write the resulting image to decent SD card using Win32diskimager, place in device and try booting. See if the bootloader runs enough to get you into ODIN.
YMMV but it is a recovery method for Snapdragons. Weather you overwrite EFS / Lose IMEI I don`t know. Only just getting back into Sammy scene.
It is kind of like a failsafe incase of EMMC corruption I think.
I can`t help with this sadly as I`m Exy
N10AP said:
Long shot but... qfil / firehose msm8998 is the way to go with this. Can be done, the hard part is getting the firehose programmer (and maybe rawprogram0 / patch0 xmls too)
Click to expand...
Click to collapse
Please explain a bit more
Isnt it supported by Z3x / Sigma / Infinity / Octoplus?
Click to expand...
Click to collapse
I have a z3x box
Doesnt that "aryk" site have a load of programmer files that could work with your device?
Click to expand...
Click to collapse
Please explain more if possible or provide web links
Failing that, JTAG / EMMC flash (pinouts should be around somewhere)
Sorry can`t be more help. I`m working on a similar issue with a Moto Z2 play atm
EDIT: I`m sure the 835 (what you have) supports booting from the SD card.
Click to expand...
Click to collapse
Thats what I hope to do
You need to ask someone with a rooted Snapdragon N8 to make a copy of the first 167(ish) MB of mmcblk0
Like this... (Brief idea... whoever does this needs to do it obviously from shell, on the device itself wether thats from TWRP shell or ADB in *nix / Win thats up to you)
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1024 count=168960
Once some kind soul has done this for you and you have downloaded it, write the resulting image to decent SD card using Win32diskimager, place in device and try booting. See if the bootloader runs enough to get you into ODIN.
YMMV but it is a recovery method for Snapdragons. Weather you overwrite EFS / Lose IMEI I don`t know. Only just getting back into Sammy scene.
It is kind of like a failsafe incase of EMMC corruption I think.
I can`t help with this sadly as I`m Exy
Click to expand...
Click to collapse
Thanks for your input its help!
Vell123 said:
Thanks for your input its help!
Click to expand...
Click to collapse
I AM Rooted however all of my stuff is experimental. So my files wont work for you. Good luck though.
me2151 said:
I AM Rooted however all of my stuff is experimental. So my files wont work for you. Good luck though.
Click to expand...
Click to collapse
you cant do a backup and share files please:fingers-crossed:
Vell123 said:
you cant do a backup and share files please:fingers-crossed:
Click to expand...
Click to collapse
Sorry maybe u already tried it but here in UK there is a **** ton of mobile repair shop and in some of them are some heavy dutie geeks.
Maybe look around your area and see if you can find someone with big passion for problem solving.
Just got my Note 8. But I remember hard bricked phones in the past brought back to life with jtag devices. Anyone try Jtag device or gotten Jtag service done to hard bricked Note 8?
Last tax season was supposed to buy 1, but car issues. I know they're expensive. But if they can fix phones with ease. Then well worth it.
Vell123 said:
HI, I bricked my N950u after rooting with the SamV2 method for snapdragon. I rooted it fine, then tried flashing stock firmware and supersu zip. I know snapdragon is bl locked but I thought I could possibly do something besides hard brick lol. Anyway, does a rooted n950u that they could share a partial or full sys dump with me so I can make a debrick img. Also if anyone knows how to un/debrick please let me know and share. Thanks in advance!!!!
P.s. I know it was stupid to do lol
p.p.s. if your not going to contribute to the solution and or insult my foolish decision please keep your comments to yourself, thanks
Click to expand...
Click to collapse
did you manage to fix this? i have some unbricking files i want to test, let me know please
ProUnlocker said:
did you manage to fix this? i have some unbricking files i want to test, let me know please
Click to expand...
Click to collapse
i sent it to samsung but i going to re root and copy img partitions
I have unbrick files for flashing qdl9008 mode for bootloader rev 2.
If you are on samfail v2 or v2.5 maybe ot the normal rev 2 bootloader they should work.
Let me know if you need them.
BigCountry907 said:
I have unbrick files for flashing qdl9008 mode for bootloader rev 2.
If you are on samfail v2 or v2.5 maybe ot the normal rev 2 bootloader they should work.
Let me know if you need them.
Click to expand...
Click to collapse
I definately could use them. I am in the same boat.
Unbrick Files
guysmiley82 said:
I definately could use them. I am in the same boat.
Click to expand...
Click to collapse
Go to this thread.
I will post the files and instructions there in the thread i started for unbricking.
https://forum.xda-developers.com/galaxy-note-8/how-to/note-8-n950u-qdl9008-edl-mode-unbrick-t3851345
did you get this resolved, I am stuck only being able to go into upload mode. I can shut it off with power and vol. down but the only thing it does is go back into upload when I try button combos. bootloader 6 btw