This guide will help you to recover dead boot or downgrade knox bootloader on N7105.
If you are on dead boot for some reason,you can skip step 1.
if you want to downgrade from knox bootloader,first backup your data.this will wipe the device
STEP 1
Write to sdcard n7105_boot1.img file
Disassemble the phone and inserd the sdcard in it`s place.connect the lcd cable,battery and power button cable to the motherboard as in picture
!!!!! THIS IS VERY DANGEROUS PROCEDURES,YOU CAN DAMAGE THE LCD CABLE!!!!
{
"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"
}
Around the resistor are glue.you must carefully remove the glue with tweezer.Heat the glue to ~ 80-100 *C with hotair gun or hairdryer then carefully remove it.
With a fine tweezers short red marked resistor
!!! you must keep battery connected,lcd ,short with tweezer and press power button with two hands !!!
Press power on button and keep shorting the resistor 3 more seconds then remove short.After few seconds you will see on screen `download completed`
After that you can assembles the phone.Now phone are in dead condition but it`s ok
STEP 2
Write to sdcard n7105_boot2.img file
Connect the battery and press power on buton. SDCARD MODE should appear on screen
Press vol down key to enter download mode
Now you can use odin
cool! but too complicated for norm users.
Excellant
I think that flashing can be dangerous and on these forums we get many cases of bricked phones
The details the OP has posted are just the type of details that forum members need
THE OP has put warnings into the post and just as with flashing bootloaders or radios or custom rom
you can trash an expensive phone .... but users change front glass with the posserbility of damaging
the LCD ... they change back panels ,,, some fit wireless chargers ... change main boards adn fit new modules internally
I say BRILLIANT post just right for those trapped on nasty knox who would like to downgrade
five stars lets have more hardware mods
No idea how you came across this info. Thanks for sharing. Would love to know the technical reasons behind why/how this works. Fantastic how-to for people in a bind and needing a last resort kind of solution.
Danger but cool!
The part to remove glue and to shortcircuit the power is the most danger one, which I think a noob like me will fail on this part.
But cool... never think about this one.
Sent from the corner of this rounded earth (N7105 v4.3, powered by LionROM)
Just one more detail. Will we need to glue resistor to the motherboard before assembling the phone back?
Hi!
Is there a solution?
Because of the display should guarantee!
If there is a solution can someone help me step by step?
German official N7105 Galaxy 4.3
Hungarian Telekom dependent device
Thank you:
Lackó
---------- Post added at 09:39 AM ---------- Previous post was at 09:34 AM ----------
Hi!
Is there a solution?
ODIN MODE
PRODUCT NAME: GT-N7105
CUSTOM BINARY DOWNLOAD: YES (4 COUNTS)
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
KNOX WARRANTY VOID: 1
AP SWREW: A2
Because of the display should guarantee!
If there is a solution can someone help me step by step?
German official N7105 Galaxy 4.3
Hungarian Telekom dependent device
Thank you:
Lackó
disparo said:
Just one more detail. Will we need to glue resistor to the motherboard before assembling the phone back?
Click to expand...
Click to collapse
Really? Resistor is soldered down to mobo. You have to remove glue which covers it from top only not whole resistor.
Hello, there are stillimages are alldead.
Hi , I've succeeded in getting to the last step. So what do I do now? Flash it in Odin? with? I tried flashing with a stock 4.3 N7105 ROM and it says "There Is No Pit Partition" and fail, so please advice. I still think my eMMC is not damaged. Can someone verify if we can get to the last step as what asteraky has shown, does it mean our eMMC doesn't need to be replaced. I am short of this last step, I know there is a ray of hope in reviving this Note 2 N7105.
This is what I get
and what does
INVALID RPMB DATA means ? All I can suspect is that the current bootloader in the phone is the 4.3 with KNOX Authentication key, the boot SD has the 4.1.2 bootloader . If only someone can dump a new BOOT SD Repair with the new 4.3 files in it , it might work. Just my theory on this. Does anyone get the same issue?
zelith said:
Hi , I've succeeded in getting to the last step. So what do I do now? Flash it in Odin? with? I tried flashing with a stock 4.3 N7105 ROM and it says "There Is No Pit Partition" and fail, so please advice. I still think my eMMC is not damaged. Can someone verify if we can get to the last step as what asteraky has shown, does it mean our eMMC doesn't need to be replaced. I am short of this last step, I know there is a ray of hope in reviving this Note 2 N7105.
This is what I get
and what does
INVALID RPMB DATA means ? All I can suspect is that the current bootloader in the phone is the 4.3 with KNOX Authentication key, the boot SD has the 4.1.2 bootloader . If only someone can dump a new BOOT SD Repair with the new 4.3 files in it , it might work. Just my theory on this. Does anyone get the same issue?
Click to expand...
Click to collapse
did you try a pit file if not i found one here http://forum.xda-developers.com/showthread.php?t=2137008
This is what I get guys
tried n7105_boot1.img file and got "SDCARD DOWNLOAD FAILED"
with n7105_boot2.img file, I get the "Invalid RPMB data"
I have another working n7105 with 4.3 rooted, is there a way to make my own boot.img file?
zelith said:
This is what I get guys
Click to expand...
Click to collapse
Why do you have repartition checked
Sent from my SGH-I317 using XDA Premium 4 mobile app
hey all..
i am following instructions to every word but when i get sd card mode it says sdcard download failed...
why is this?? what am i doing wrong??
thanks
rob
Does it need to be a 2Gb SDCard, does anyone know?
I'm trying with a 32Gb SDCard and getting nothing.
i tried this method
but no luck, no shows anything
my phone is dead and motherboard is ok , no short
any other solution
thanks
What is the resistance value of this component? Lost mine, need to replace it with spare.
What about for N7100? Does anyone have the file needed to save on sdcard?
WARNING... CORRECT ME IF I'M WRONG, BUT THE 2ND PHOTO (ONE OF MOST IMPORTANT) ISN'T ACTUALLY A NOTE2 IS IS??
I Don't think it matches the other photos (also light background vs others)... so don't pull your whole phone apart unless you are SURE the 2nd photo showing the resistor, is the CORRECT ONE!!! Can someone verify this? It also doesn't match a Note2 disassembly video i watched on youtube...
Related
BHP090808 PRESENTS
I545 ALL-IN-ONE TOOL ROOT + RECOVERY INSTALLER
**READ READ READ AND READ AGAIN**
DO NOT RUN IF YOU ARE ON NEW ME7 OTA UPDATE!
This tool was created to simplify the rooting and recovery installation on this device. The rooting method used is the same method already posted in this development section. I just put all the resources into a tool and provided easy to follow instructions. The root process is not a one click. You must read instructions in tool window for each step of the rooting process. It is very straightforward and easy to follow, but you must follow the instructions exactly. Once rooting is complete all other steps are one click features including recovery installation.
Make sure you have latest samsung drivers installed. I recommend downloading Samsung Kies, It will automatically download latest drivers for you. Make sure unknown sources is checked and USB Debugging is enabled or the tool will not see your phone. Also make sure you do not have any pw or pattern lock screen enabled. As soon as you start step 1 check your phone screen. You will see a prompt to authorize your computer. Select ALWAYS ALLOW. This is the cause of the majority of errors. Also the usb cable that came with your s4 is recommended. If you are having issues with odin recognizing your phone check drivers and try using a different usb port. If using a desktop I recommend using the rear usb ports. Prep step (#2) removes install-recovery.sh and KNOXAgent.apk from your phone. These have been known to cause unwanted errors.
If when rebooting from recovery you are prompted with a message advising root may have been lost would you like recovery to fix it? I have always chosen NO and had no issues.
I do not offer support on either recovery or any rom you flash after this process. Check their respective threads for any and all information. Links to both recovery threads are included as options in tool.
I've included latest CWM (credit OUDHS & Shabbypenguin) and TWRP (credit Team Win). The rooting method and kernels used were provided by sextape. The step by step root process from open1your1eyes0. The motochopper exploit was created by the legendary djrbliss. Also a big thanks to djrbliss for Loki, without which none of this would be possible. Make sure to find these fine folks and give thanks, money, beer, your first born..... whatever you see fit.
I'd also like to thank niv3d, an21281, CraziiChief and all of my other testers. I'd also like to thank my wife and kids for leaving me alone while I worked on this. Mirrors are ok, just pm me the link to list in the OP.
Hope this makes someones life easier.... Have a nice day!!!!
Instructions:
Download zip file
Unzip on desktop
Connect phone with USB debugging enabled
Click RUN_ME (inside unzipped folder)
Pick option and go!!
Have patience it takes a few for cpu to see phone after reboots and in Odin
dont disconnect phone until process is complete
If stock start with option 1
If already rooted start with option 2 then choose recovery
Download-
I545 All-In-One Tool
https://mega.co.nz/#!I1c1jTBY!GCtdvXRoeXiCRNgjXge3CA9UZ3FIBtHf-m2_kQCr3BI
Mirror-
http://db.tt/1wpdewwY
Dont forget to hit the thanks button and rate thread 5 stars:thumbup:
And if youd like to buy me a beer I wont complain :beer:
Thanks for the beer list::beer:
(Donations Received)
yamaharider
Michael Oconnell
SolemnSinner
Mills23
Eric Lee
Artiepea
JNava420
Footbaggin
Charles Uniman
Updated 5/30
oudhs cwm is now 1.0.3.5
Updated 5/31
Fixed script typos
(Thanks scrosler)
Updated 6/1
Added to prep script
Added additional instruction script
Updated 6/3
Fixed script typos
(Thanks opethfan89)
Updated 7/8
TWRP updated to 2.6.0.0
Great job! This tool simplifies the root process and makes it a breeze for those who are tempted to root and flash! Give it a shot you won't be disappointed!
{
"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 tested this utility a few hours ago and it works great! Just make sure to follow the directions and give it time to do every step, very easy!
Complete newb question here, and searching didn't turn up much.. Seeing as there is no Bootloader unlock yet, theoretically you should be able to just revert to stock and unroot and no one would know you were ever rooted/ROMd, right?
If I completely missed a post that explained this, sorry.. I searched and didn't see it.
Yep. Just Odin back to stock and you're done.
Sent from my SCH-I605 using Tapatalk 4 Beta
Just used this method to root and install recovery on my new S4 and it worked great! thanks for the tool
You sir, are awesome. So easy. Always nerve racking rooting a new phone but this is cake. Took 5 minutes. A caveman could do it! Thank you!
great tool! worked very well! thanks!
Worked like a dream, thanks a lot!
Tool Updated...
CWM is now 1.0.3.5
Thanks. Success! Ive never seen odin in action, that was cool. Thanks for the easy instructions throughout the process. Very easy.
Sent from my SCH-I545 using Tapatalk 2
Thanks,m just had to trade my phone in due to manf. defect. This'll make re-rooting a lot easier!
Download link broken. Says file is corrupt.
Sent from my Galaxy Nexus using xda premium
USB Debug
New to Galaxy S4 where can I find USB Debug in setting? thx!
kevinniven said:
New to Galaxy S4 where can I find USB Debug in setting? thx!
Click to expand...
Click to collapse
To unlock the Dev Options menu, go to Settings -> About Device and scroll down to the "Build Number." Now, tap on your "Build Number" five times, and you should see a toast notification pop up saying "Developer mode has been enabled." Back out of the About Device menu and you'll see Dev Options back where it belongs, so you can turn on USB Debugging and whatever else you want to.
(taken from http://gs4.wonderhowto.com/how-to/enable-hidden-developer-options-your-samsung-galaxy-s4-0146687/)
Elvis_Marmaduke said:
Thanks,m just had to trade my phone in due to manf. defect. This'll make re-rooting a lot easier!
Click to expand...
Click to collapse
Just curious....what was the defect?
Tar file
All seems to be going ok but not seeing TAR file in Oden?
viceversa said:
Just curious....what was the defect?
Click to expand...
Click to collapse
It was a small thing in the top left corner of the screen, I could only see with the screen off. It looked like glue or a tiny hair under the glass. I was mostly just worried it was going to get worse over time. I didn't even notice it until I was putting a screen protector on (you know how impossible it is to get rid of all that dust). Free replacement through Verizon though because it's a defect.
I tested on LG G2 Korea Version F320S, F320L, F320K
- Why bootloop?: Some people Update OTA after flash CWM or TWRP so it will be bootloop. Or some strange reasons
- What should we do when we can not flash Stock firmware by FlashTool.1.0.54?
Let do follow this guide:
- Download file:
Flashtool V1.5 --> http://www.fshare.vn/file/TNVQZ9N74T ( tks to GSM Hosting forum )
Crack Flashtool : http://www.fshare.vn/file/TS1SGGVYWT ( tks to GSM hosting Forum )
File .TOT firmware :
F320S ->>> http://www.fshare.vn/file/T3SZR52W6T
F320K ->>> http://www.fshare.vn/file/TZRVMVMPFT
F320L V11c -->>> http://www.fshare.vn/file/TVR9DPAC7T
.dll file F320S/L/K >----- http://www.fshare.vn/file/TKW8J7QPQT
Driver: http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
- Let do:
Step1: Install Flashtool V1.5. Default install folder C:\LG\LGFlashtool
Copy crack file Megalock.dll to C:\LG\LgFlashtool
Step2: Enter download mode: Turnoff, push vol+ and plug USB cable in
Open Device Manager on your computer and choose COM41 for phone connection:
{
"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"
}
Step3: Open Flashtool, choose .dll and .tot file, then fresh yellow icon like this:
Step4: When Flashtool show Realdy, push USB out for 5secs and plug in again. Flash tool will automatic run
Step5: Wait for finishing:
Read more: http://choimobile.vn/threads/huong-dan-cuu-soft-brick-lg-g2-f320s-l-k.12932/#ixzz2h8Fy9fJB
Suggest you read the rules for XDA no warez allowed, CRACKED SOFTWARE = WAREZ!
fma965 said:
Suggest you read the rules for XDA no warez allowed, CRACKED SOFTWARE = WAREZ!
Click to expand...
Click to collapse
This is extremely useful, please blackout offending list and leave the post alone.
JoeTF said:
This is extremely useful, please blackout offending list and leave the post alone.
Click to expand...
Click to collapse
As a RC i can't do that.
Even though it is cracked, we don't see it as "warez". Almost every device has it cracked, so noone would be able to use it if we wouldn't allow it.
I mean, we also "crack" the bootloader of devices, which would be considered as warez, too, in that case
Cheers
laufersteppenwolf said:
Even though it is cracked, we don't see it as "warez". Almost every device has it cracked, so noone would be able to use it if we wouldn't allow it.
I mean, we also "crack" the bootloader of devices, which would be considered as warez, too, in that case
Cheers
Click to expand...
Click to collapse
hmm i guess, the way it was worded seems like you were cracking software tbh. my bad
fma965 said:
hmm i guess, the way it was worded seems like you were cracking software tbh. my bad
Click to expand...
Click to collapse
oops, may be a bit unluckily worded... the first "we" was meant as the mod staff, and the 2nd "we" as xda in general
laufersteppenwolf said:
oops, may be a bit unluckily worded... the first "we" was meant as the mod staff, and the 2nd "we" as xda in general
Click to expand...
Click to collapse
sorry, yeah i meant the OP not your reply
fma965 said:
sorry, yeah i meant the OP not your reply
Click to expand...
Click to collapse
Good post. Please leave this post coz I am also the lucky guy can get repair my bricked G2 using this usefuly TOT recovery method.
If possible, remind to set back correct version number (F320 L / K / S) in build info. which match with your IMEI#.
dokyson said:
I tested on LG G2 Korea Version F320S, F320L, F320K
- Why bootloop?: Some people Update OTA after flash CWM or TWRP so it will be bootloop. Or some strange reasons
- What should we do when we can not flash Stock firmware by FlashTool.1.0.54?
Let do follow this guide:
- Download file:
Flashtool V1.5 --> http://www.fshare.vn/file/TNVQZ9N74T ( tks to GSM Hosting forum )
Crack Flashtool : http://www.fshare.vn/file/TS1SGGVYWT ( tks to GSM hosting Forum )
File .TOT firmware :
F320S ->>> http://www.fshare.vn/file/T3SZR52W6T
F320K ->>> http://www.fshare.vn/file/TZRVMVMPFT
F320L V11c -->>> http://www.fshare.vn/file/TVR9DPAC7T
.dll file F320S/L/K >----- http://www.fshare.vn/file/TKW8J7QPQT
Driver: http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
- Let do:
Step1: Install Flashtool V1.5. Default install folder C:\LG\LGFlashtool
Copy crack file Megalock.dll to C:\LG\LgFlashtool
Step2: Enter download mode: Turnoff, push vol+ and plug USB cable in
Open Device Manager on your computer and choose COM41 for phone connection:
Read more: http://choimobile.vn/threads/huong-dan-cuu-soft-brick-lg-g2-f320s-l-k.12932/#ixzz2h8Fy9fJB
Click to expand...
Click to collapse
can't eneter in download mode i am stuck!!! help!!!
can someone give me the files for my D80210a
Stuck
Every time I try to press vol.up and plug in I still load right into twrp
ocarlty said:
Every time I try to press vol.up and plug in I still load right into twrp
Click to expand...
Click to collapse
I have the same problem with the CWM.
when i press the yellow arrow it gives me this error
i press ok and it continues to the step i have to reconnect the phone.
i reconnect it and i get this
i have changed the com number
i don't know what is the problem...
taxexpert said:
I have the same problem with the CWM.
Click to expand...
Click to collapse
Me too. Ever get this figured out?
I think what this boils down to is USB debugging was disabled by the factory reset. I had reset my device to prepare to sell it. When it booted back up I got an OTA offer and, not thinking, I accepted it. However, I still had CWR and root. I think OTA'S require stock recovery to work properly. So, no USB debugging and CWR as the recovery = soft brick. And, since CWR does not have a terminal option, there's no way to enter commands. I'm thinking this is going to be a warranty claim for me.
Will it work to restore a D805?
dokyson said:
I tested on LG G2 Korea Version F320S, F320L, F320K
- Why bootloop?: Some people Update OTA after flash CWM or TWRP so it will be bootloop. Or some strange reasons
- What should we do when we can not flash Stock firmware by FlashTool.1.0.54?
...
Click to expand...
Click to collapse
Hi!
Thank you for this n.n
Will it work to restore a D805? If not, then I better be careful with OTAs, or I better don't use any recovery as I'm not going to
flash any custom ROM till the G2 is done with official updates (2015?).
Thanks again n.n
- L.
I get this problem any help would be appreciated. thanks.
Could someone give another link on file for F320S > LGF320SAT-00-V10e-SKT-KR-JUL-29-20130
Becuse I have tried to download it by link in the topic. It takes me more than 8 hour, but file was corrupted (2.3 GB not 2.5 GB).
Please - I need TOT for F320
Sorry, if I interrupt here. I'm very new to forum.
My LG G2 F320S having Boot Loop after i updated on 4th Jan 2014.
I try to get TOT file for - 320S ->>> Given location But it seems not working. (I meant not downloading. I tried several days).
If anybody having it please please share with me.
Thanks Lot.
LK
Weird issue
Hi All,
tried using flashtool but I get the error that I need to check my phone model or the DLL.
I bought this phone from the Philippines with model number LG D802. I had flashed other roms for this with D802.
But when I was trying a while ago since I got a bootloop issue, the phone's downlaod mode is in korean and says in the phone and flashtool that my phone is running F320K? but it's so weird since I had D802 before even in the IMEI sticker in the back and to think I installed rayglobe ROM, before having the boot loop.
Any help would be appreciated.
THanks!
I know, it's kinda old model from Docomo but still there's no any info out there for rooting and unlocking. Mr. fi01 has made a bunch of tools for other models of Docomo phones but not for this one. So, I wonder if it's possible at all. Ideally, I wanted to get the root and unlock the bootloader to install my custom firmware (e.g., Cyanogen). Tried some roots by fi01, but none of them worked. And I cannot get any answer from him.
I could contribute some money for it (within reasonable limits, ofc.).
oneclickroot,this website say root is done.
root after how to unlock SIM?
o759 said:
oneclickroot,this website say root is done.
Click to expand...
Click to collapse
Really? I have tried a bunch of modern rootkits and exploits and none of them worked. But I figured out how to get root with some private exploit, based on RowHammer attack. Here's my long conversation with fi01 about rooting F-01F: https://github.com/android-rooting-tools/android_run_root_shell/issues/42
Do you have # sign in adb shell and both uid and gid = 0? If yes, then you are root for sure.
But still there is no rights to mount /system as rw because of SELinux and fjsec LSM thing. I'm trying to overcome that but it's not that easy.
Sorry, I don't know how to do SIM unlocking. My phone was already unlocked when I bought it.
There appeared some videos for rooting F-01F on older firmwares (Android 4.2.2 JellyBean, build # V32R63C).
https://www.youtube.com/watch?v=bfpBeUTShhg
https://www.youtube.com/watch?v=kAM2U1hkqng
https://www.youtube.com/watch?v=PvHot7Oo62Q
Sadly I had no success with that 'cause I'm on V10R22A and those rooting tools don't work.
Arrows nx f-01f is now rooted . with shouhuanguanli.apk . Indian FB group. If need more info PM me at facebook messenger "Mijery NyTontolo"
NB: need to repeat process if failed . (person : 23times, but I have root now )
Lez16 said:
Arrows nx f-01f is now rooted . with shouhuanguanli.apk . Indian FB group. If need more info PM me at facebook messenger "Mijery NyTontolo"
NB: need to repeat process if failed . (person : 23times, but I have root now )
Click to expand...
Click to collapse
This is Dianxinos Superuser app. But as I said earlier it's not working for KitKat firmwares (Android 4.4.2, build # V10R22A), because there's PXN enabled and no known way to disable fjsec LSM. On older builds there's no PXN, so ping pong exploit may be used (which seems to be already integrated into Dianxinos, OneClickRoot, KingRoot and others).
Well, anyway I tried to run Dianxinos apk many times. It cannot gain root:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please, could you tell what's your build #? (Settings -> About phone -> Build number (at the very end))
HW root
I have attempted to do hardware root but failed. :crying: It was an interesting undertaking, but almost impracticable.
For the reference I used these two wonderful articles: Hacking Hardware with a$10 SD Card Reader and eMMC Adventures, Episode 1: Building my own 64GB memory card with a $6 eMMC chip. Moving in steps through the papers, I determined that eMMC in F-01F is presented in two versions:
1. Toshiba THGBMAG8A4JBA4R, JX4135, Japan 1337KAE
TH: Toshiba NAND
G: Packaged as IC
B: Vcc (Flash power supply) = 3.3 V, VccQ (controller/interface power supply) = 1.8 or 3.3 V
M: eMMC device
A: Controller revision A
G8: 32 GB
A: ? NAND Flash
4: 4-stacked dice (4 8GB chips)
J: ?nm A-type Flash
BA: Lead-free and halogen-free
4: ? temperature grade (? to ? degrees Celsius)
R: package size = ?
2. Samsung KLMBG4GEAC-B001
Here's a photo of the PCB with eMMC revealed:
Both chips are completely interchangeable and share the same pinout. Another two chips on the picture are RAM, which is Samsung K3QF2F20DA-QGCE, 334, 1338 DUO28, GFF0539N, and the camera controller / media processor / ARM core, which is Fujitsu MBG046C E1, 1330 SLC.
Knowing that, I whittled down the eMMC chip to see the contact pads, where the balls were located. After that I traced some pins and got that image:
The power and ground pins could be seen here:
As you may see, DAT0 is quite difficult to solder to (you may need a soldering iron with a very thin tip). But the real hardcore is both CMD and CLK as they are located at the tiny resistors' ends in the very corner between eMMC and bigger resistors. For the better understanding here's a photo with those little resistors completely removed:
So it appears to be a practically impossible thing to get the wires soldered to CMD and CLK, not damaging other components. A spoon of tar is a compound, which covers some of the resistors. I doubt, the most virtuoso in the electronics could do that task (almost of the same complexity as unsoldering an eMMc and soldering it back). That's why I should stop at HW rooting. Maybe someone find those pictures useful and do some further explorations.
help !!!
please help me for root fujitsu f01j.
I'd like to report that F-01F (V10R22A) is rooted now using CVE-2017-8890 exp: https://github.com/dadreamer/CVE-2017-8890. I adapted the exp from thinkycx with some tricky ROP chain to overcome fjsec protection. The LSM and SELinux are still in place after the system restart, so it's a subject for bootloader unlocking and the system modification, but no progress is made for that yet.
dadreamer said:
I'd like to report that F-01F (V10R22A) is rooted now using CVE-2017-8890 exp: . I adapted the exp from thinkycx with some tricky ROP chain to overcome fjsec protection. The LSM and SELinux are still in place after the system restart, so it's a subject for bootloader unlocking and the system modification, but no progress is made for that yet.
Click to expand...
Click to collapse
is any more progress yet for now?
fiefie7 said:
is any more progress yet for now?
Click to expand...
Click to collapse
If you mean the bootloader unlocking, then no more work will be done for that. One of my devices is almost dying due to the bad battery and the second is SIM-locked and software bricked. Therefore I'm not going to spend my resources for these obsolete phones anymore.
well, that's too bad...
Long story short, I accidentally deleted my bootloader flashing atvXperience (aml_sdc_burn.ini had "erase_bootloader = 1" in it and sh*t hit the fan).
Result: red LED, no screen, no magic sdcard, no recovery, lots of tears :crying:
Searching for solutions I found this very helpful blog post: https://blog.danman.eu/bricking-and-unbricking-vontar-x96-mini/
but... my board was different (Q6X V4.0 17392) and the pin wasn't the same or even in the same general place.
images:
{
"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"
}
The advise in that blog post allowed me to find the correct pin for my board using a multimeter and some time&luck
I then describe the procedure that revived my box:
1.- watch image and mimic wire solder (marked with a red circle and GND label)
2.- short marked resistor using the grounded wire and plug power. Hold the wire for 2-3s and disconnect wire from resistor. Unplug power.
3.- connect usb to pc and otg connector on board. When pc recognizes it, plug power. (if you don't plug in the power, the board has not enough minerals energy and the flashing fails.
4.- use flashing utility to reflash your device (not explaining that here; lots of advise on other threads).
Also, if someone needs the stock Android 9 firmware, here it is:
https://mega.nz/#!UcQ12KpL!NPjAQlFLUHwVxf7y_Lw9V4vZAaCYeuD6f1RpqwgmCH8
I hope this helps
DanAlucard said:
Long story short, I accidentally deleted my bootloader flashing atvXperience (aml_sdc_burn.ini had "erase_bootloader = 1" in it and sh*t hit the fan).
Result: red LED, no screen, no magic sdcard, no recovery, lots of tears :crying:
Searching for solutions I found this very helpful blog post: https://blog.danman.eu/bricking-and-unbricking-vontar-x96-mini/
but... my board was different (Q6X V4.0 17392) and the pin wasn't the same or even in the same general place.
images:
The advise in that blog post allowed me to find the correct pin for my board using a multimeter and some time&luck
I then describe the procedure that revived my box:
1.- watch image and mimic wire solder (marked with a red circle and GND label)
2.- short marked resistor using the grounded wire and plug power. Hold the wire for 2-3s and disconnect wire from resistor. Unplug power.
3.- connect usb to pc and otg connector on board. When pc recognizes it, plug power. (if you don't plug in the power, the board has not enough minerals energy and the flashing fails.
4.- use flashing utility to reflash your device (not explaining that here; lots of advise on other threads).
Also, if someone needs the stock Android 9 firmware, here it is:
https://mega.nz/#!UcQ12KpL!NPjAQlFLUHwVxf7y_Lw9V4vZAaCYeuD6f1RpqwgmCH8
I hope this helps
Click to expand...
Click to collapse
thank you for sharing this. by the way this is the first time i read that there is already android 9 for x96 mini. have you already tried to install this rom? do you have screenshots also?
thanks sir.
claishem said:
thank you for sharing this. by the way this is the first time i read that there is already android 9 for x96 mini. have you already tried to install this rom? do you have screenshots also?
thanks sir.
Click to expand...
Click to collapse
I don't have screenshots right now, as I'm not in my home right now, but that is the exact rom that came installed on my box. Asked the seller for it and he sent it. Flashed and tested. Android 9.
Also, atvXperience is working on an android 9 version. Seems like amlogic distributed a pie sdk. Can't confirm though.
My box is a 2g/16g version. Can't assure it will work on 1g/8g or 4g/32g
DanAlucard said:
I don't have screenshots right now, as I'm not in my home right now, but that is the exact rom that came installed on my box. Asked the seller for it and he sent it. Flashed and tested. Android 9.
Also, atvXperience is working on an android 9 version. Seems like amlogic distributed a pie sdk. Can't confirm though.
My box is a 2g/16g version. Can't assure it will work on 1g/8g or 4g/32g
Click to expand...
Click to collapse
thanks. by the way, i attempted to flash the android 9 img in the link you provided but when i import it in the usb burning tool it says something like img parse error. i wonder why.
claishem said:
thanks. by the way, i attempted to flash the android 9 img in the link you provided but when i import it in the usb burning tool it says something like img parse error. i wonder why.
Click to expand...
Click to collapse
Well... I make the magic sdcards on linux manually, so I can't test the usb burning tool as I don't have any windows machines
This is the original link the seller sent me: https://mega.nz/#!QXhWTCiQ!NPjAQlFLUHwVxf7y_Lw9V4vZAaCYeuD6f1RpqwgmCH8
I can reupload to see if that is the problem, but I can't do it before monday :angel:
Hi recently I was trying to update Atvxperience rom but by mistake i installed s905x version. Thus it ended with a red light and black screen... I have no usb to usb cable so I was using sd card method for flashing.. Now the issue is that i have a different board and test pins as shown in your post i could not find in my board. Now help please. My board is this. Please help me.
mmrx said:
Hi recently I was trying to update Atvxperience rom but by mistake i installed s905x version. Thus it ended with a red light and black screen... I have no usb to usb cable so I was using sd card method for flashing.. Now the issue is that i have a different board and test pins as shown in your post i could not find in my board. Now help please. My board is this. Please help me.
Click to expand...
Click to collapse
thanks it worked.. however i shorted pins by looking here... https://forum.freaktab.com/forum/tv...icussions/791910-help-x96-mini-q6x-v2-2-17355
My board also is Q6X V4.0 17392, but my eMMc chip is SK Hynix. I tried to short these 2pins but nothing happend. The light flashes red and blue continuously, and the PC can't detect the board , though my PC can detect X96 MAX+.:crying:
update: I found the solution. In fact, I didn't flash the bootloader. I shorted the pin in the green circle and ground with TF card inserted and it began to flash the firmware automatically...
mmrx said:
thanks it worked.. however i shorted pins by looking here... https://forum.freaktab.com/forum/tv...icussions/791910-help-x96-mini-q6x-v2-2-17355
Click to expand...
Click to collapse
I´m shorting the two gold colored circles and it still doing nothing.
In my version with a toshiba nand flash I had to short this resistor here for it be detected by the pc again:
Napalm_PT said:
In my version with a toshiba nand flash I had to short this resistor here for it be detected by the pc again:
Click to expand...
Click to collapse
Hi what firmware did you use for the Toshiba Chip i cant find firmware for mine anywhere
mmrx said:
thanks it worked.. however i shorted pins by looking here... https://forum.freaktab.com/forum/tv...icussions/791910-help-x96-mini-q6x-v2-2-17355
Click to expand...
Click to collapse
Hi what nan chip do you have on that board i also have the v 2.2 but mine has the toshiba nan chip and i seem t have very bad luck finding firmare
Tenho uma Q6X V3 pc reconhece mais o flash para em 7%,[0x32030201]Uboot/Get result/DiskInitial error.tentei cum varias firmwares diferentes
Mod translation: I have a Q6X V3 pc that recognizes the flash at 7%,[0x32030201]Uboot/Get result/DiskInitial error. I tried with several different firmwares
Hey All
Its been a while since I got to play with anything these days but I recently found one of these POS 10in touchscreen units in the dumpster and it fires up into a menu running android. So I was hoping I could reflash this and use it like a tablet given it's also got a small thermal printer in it, so maybe try and save it from e-waste
I searched online for more details and came across this HERE which is identical to what I have so hoping I can root it and flash it with a clean android?
I would love to repurposed this to use as a touch screen tablet or similar, since it's got a GSM module and can take an SDCard too as I opened it up and took some pictures and I managed to get it in a recovery mode as well - from the PIX its using a rockchip RK3368
{
"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 am not sure if the mini usb port is a OTG port to try and use ADB but I have not been able to do much with it and hoping someone can guide me through to possibly a reflash or ways to unlook root and add in another bootloader/rom
I've downloaded the files from citaq website but so far not been successful to do much with it, has anyone played with these and turned them into something more practical for the home?
Here's hoping for some tips - Apology if this is in the wrong section, move as needed :good:
Cheers
Kosti
@Kostiz
Device actually is running Android 5.1.1. It seems it has only 1GB RAM what is far too little to run a full fledged Android.
As long as you don't replace device's Stock Recovery by TWRP or similar recoveries, after a successful rooting don't install Magisk and/or Xposed Framework, you're on the safe side to play with, IMHO.
As 1st step check whether device is accessable by means of both ADB and Fastboot.
jwoegerbauer said:
@Kostiz
Device actually is running Android 5.1.1. It seems it has only 1GB RAM what is far too little to run a full fledged Android.
As long as you don't replace device's Stock Recovery by TWRP or similar recoveries, after a successful rooting don't install Magisk and/or Xposed Framework, you're on the safe side to play with, IMHO.
As 1st step check whether device is accessable by means of both ADB and Fastboot.
Click to expand...
Click to collapse
Hey, Thanks for chiming in!
So in order to get ADB and or Fastboot its suggested to enable USB debugging in the device system settings, but I am not sure on how to do this, would it be safe to assume this is already USB debug is already enabled?
Could I back up the original stock recovery
I'm a little green on the whole process hence looking thought I'd ask here, I don't think I even have an OTG cable handy
I will see if I can load ADB on a windows box and try and talk to this unit
Cheers
Kosti
@Kostiz
An OTG-cable isn't needed, because the recovery menu
doesn't give you the opportunity to load something from an USB-device
OK, some success!
I went back and connected a mini USB straight to the PC and ADB driver installed detected the android device.
Ran ADB in windows powershell
So whats the best method to backup the entire ROM, and recovery files in the event I stuff this up?
Do I use just ADB for this or someother tools?
I did try one tool here from the vendors website but stuck as not sure what the Chinese characters mean..
Is the fact that this is only 1G i couldn't run Android at all and needs to be stripped down?
Cheers
Kosti
@Kostiz
Android Oreo Go Edition is a lightweight distribution of Android that runs better than normal Android on devices with <= 1 GB of RAM
How to backup device's Stock ROM is eplained here.
Thanks again mate!
Seem I have to do a lot of reading and thankfully everything is here, just got to spend time to read and have a go!
BTW how do I go about using volume rockers and power button to move around the menu in recovery when there is none but only the two buttons as shown the reset and recovery buttons on the main board?
BTW, the current ROM installed boots into a special menu, all other settings are hidden, would there be a way to enable seeing all the items and when getting the the settings (gear icon) that pops up in the corner, only takes me to the standard wifi menu to choose a wifi, so it seems everything else is hidden, if by enabling these I could potentially not need to do anything other than stop the default application from starting up - if that makes any sense
Could I just get back into a adb shell and try
adb shell
su
pm enable applicationname
I have to read up on rooting first I assume before I do much more, this is getting exciting, LOL :good:
Kostiz said:
BTW how do I go about using volume rockers and power button to move around the menu in recovery when there is none but only the two buttons as shown the reset and recovery buttons on the main board?
Click to expand...
Click to collapse
You use Android's HOME button to navigate within the Recovery menu, use POWER button to select option.
Hi, fellas! Please help me with one of these Citaq H10 POS. All we have is bootloop with some custom ROM showing vendor's logo.
Forcing it into recovery gives me some dead android screen with "No command" text.
Please guide me through this challenge, cause I have no other option but to ressurect it somehow.
Good news is that I have another one that is working fine, so we could try cloning it or something. Please help!
Yet I can't attach pics, cause of few posts, but if needed I can PM some.
citaq h10-2
I am also stuck with this machine citaq h10-2 , i did use a wireless kb to move up/down and not the 2 buttons on the motherboard , i can talk with it with ADB but all you can do is put it in sideload to upload new firmware and put it in fastboot but in fastboot you only get a black screen , what I have don is > opened up developer mode but you have no OEM UNLOCK tick box in side so running any bootloader unlock dose not work and i have run them all, if you google this machine for flashing new firmware you only get XDA this forum, unless any body knows another place to get the info from please let us know as i do think this would make a nice tablet with printer, the firmware is 5.1.1 and would love to put 6.0 or above on it but. i did download some firmware and used sideload to install it but it come up with error , i did try and make a backup but cannot do it ?, I think the firmware was from a galaxy s5 , I am not into all this firmware flashing so I am learning as I go along and if I brick it up well it was for free any way as the takeaway was shutting down and he gave it to me so no loss, if any body knows how we can get 6.0 or above on this machine please let us know.
A big thank you to all that can help put android 6.0 or above on this tablet.
Did you guys take a look at the solution here ? It worked for me ! All with a 2k ohm resistor...
Hola, alguien tiene la Rom de este dispositivo?