I'm writing this in android development section because this is only section for both models, i hope this is not a problem.
Also i want to say thanks to sataccount from gsmhosting, he found working map at the end.
This guide is for hard bricked phones, where bootloader is destroyed and there is no any tools which recognize phone.
When you connect phones without bootloader Windows detects them as exynos7420 in other devices in device manager.
All this is achieved using trial/error method and I still don't know real sboot map and where is what in sboot.bin.
What i found till now is that sboot consist from this parts:
1. fwbl1 bl1
2. bl2 bl2
3. el3_mon el3
4. bootloader bootloader
5. tzsw tzsw
I repaired my g925a and have files only for this model, but i will try to explain how to prepair files for any other model.
We have to use same version of bootloader which was previosly in phone, or if you are unsure use latest sboot.bin.
Download tools: http://www.mediafire.com/file/sg5m2ti3k6a63z5/USB_Down_Load_32bit.zip
In folder USB_DownLoad_Tool there is a folder Disk1
Connect phone and hold power button.
Windows will detect exynos7420 device, install Driver:
click manually,
com and lpt ports,
have disk,
point to data1 folder.
Don't run setup from Data1 folder!!!
Now we have to copy
WinDNWApi.dll
WinDNWApi.lib
in:
c:\Program Files\SAMSUNG\Exynos USB Driver\Drivers\
Probably there is no this folder, just create it and copy 2 files.
Don't copy WinDNWApi.dat as it is written in original manual, this file is for older exynos chip and procedure will not work, everything works without this file (it only has maps for 5250 and some other cpu)
Now we have to create boot files.
Download sboot.bin for your device, as i wrote best to find same bootloader which was in device before brick.
In some hex editor create 4 files (i'm using frhed, just click copy, enter offset, new file, paste, save and over again for all four files) with this map (again thanks to sataccount):
Novi1.bin 0..0x1FFF (size 0x2000 or 8192 )
Novi_2.bin 0x2000..0x31FFF (size 0x30000 or 196608)
Novi_3.bin 0x32000..0x3dfff (size 0xC000 or 49152)
Novi4.bin 0x3E000..10EFFF (size 0xD1000 or 856064)
This is all without tzsw. If phone still does not enter to odin mod, make last file from 0x3E000 to the end of the file (18F10F) and try again.
Start multiuploader.exe
Connect phone and hold power button.
Browse and find SH-usb-booting.cfg (in attached file proba folder, that is where you will probably prepare all boot files)
click start and phone will enter odin mode.
Start odin and flash sboot and everything else.
First of all thanx this is a real sharing is caring thing.I'm seeing a way to downgrade bootloader here as tzsw gets separated well this can be done by daring dev who can take risks.
I'm not sure about downgrading.
When i tried to repair my phone, first i tried with 5.1 sboot (eng and normal). It hangs on second file. It checks somethings before start to load real bootloader. Maybe to fill whole device with zeros with dd command (deleting pit can be enough, but also maybe it ignores PIT and read some specific bytes on sda) and then restoring phone as it is just builded in factory. Of course first to make backup of EFS etc...
Even with downgraded sboot, i'm not sure can we use 6.0 and 7.0 roms?
Best way is someone with IDA knowledge to find bytes for unlocking and we can write them to sboot with dd if="something" of =/dev/sdb bs=xx count=xy
At least it is now repairable if it is bricked after that
Good find, thanks.
How did you break the bootloader (sboot) anyway?
Dd if=sboot_from_925f of=/dev/block/sdb
I had engineering boot (kernel) with adb root access. And after that phone is dead.
On 925a sboot is on sdb (just sdb without numbers), cm.bin on sdc. Probably same on all variants.
Hi
I'm not sure I understood the hex files creation step.
Start byte : 0
End byte : 0x1FFF
Size : 8192 for Novi1.bin for example
Right ?
Yes, that's it
Just compare with my files if unsure.
OK Thanks
Congrats for this amazing guide
G928c dont know version inside.
I tried 7.0 but tool hang after novi1 transfer.
with android 6 sboot all 4 files transfer succeed but no download mode
if I do 0x3E000 to the end of the file, tool hang after 1st file.
according to customer 7.0 was inside before brick.
ok I tried different 7.0 which take me to on display usb recovery mode.
but phone not detected by pc after reset by keys now phone completely dead.
no exynos mode, no download mode nothing.
PC not sensing phone anymore.
Did you restore exynos mode?
Try to add tzsw ( novi4 should be from 0x3E000 to the end of sboot.bin).
yes I open phone and re-insert battery. Now exynos mode.
(novi4 should be from 0x3E000 to the end of sboot.bin) give me USB Recovery Mode. but as previous post no detection.
do sboot contain tzsw ?
if so what is address for tzsw ?
tzsw is from 10F000 to the end of file. But you added it and phone loaded when you made novi4 from 0x3E000 to the end of sboot.bin.
I think it is still problem with different sboot version, it must be same as version previously in phone. Try few more sboot bin.
You don't have to pull out battery, just press volume down and power for more then 20 seconds, it is same like you reinsert battery.
I reconfirmed version form client and he said he is sure about 7.0 version.
this variant have only 3 files of 7.0 and I tried all sboot from 3 available versions.
zogu said:
You don't have to pull out battery, just press volume down and power for more then 20 seconds, it is same like you reinsert battery.
Click to expand...
Click to collapse
yes this is the way but in my condition not reset after 30sec and I feel phone heat too. thats why I decide to open phone.
Phone enter download mode and pc does not detect it, it is really strange, like it hangs after entering mode. Maybe is phone (flash memory) broken?
try with jig cable, maybe this can help, it is only idea i have...
zogu said:
Phone enter download mode and pc does not detect it, it is really strange, like it hangs after entering mode. Maybe is phone (flash memory) broken?
try with jig cable, maybe this can help, it is only idea i have...
Click to expand...
Click to collapse
I also think this can be memory issue.
tried all possible ways but no success.
device returned to customer.
anyways thanks for this guide and your quick response.
:good:
I dd over sdb, BOTA0 BOTA1 RECOVERY CACHE and SYSTEM, am i sol on this one? Phone doesnt get detected by pc. Even tried unplugging the battery. For those curious why...I found out theres a partiton flag set on all of those partitions. Its SYSMAGIC X , X being a number. Lowering that number on the system by dd' ing sda18 and rebooting, results in a fw error, binary 3 device 4. Aka phone thinks system installed is lower then what it really is. I know u cant downgrade the bootloader using your method, but if u dump sdb, and edit the sysmagic line in a hex editor, dd it back. It will now be corrupt, I wonder if you can now downgrade to the version we faked. Anyone care to give it a trytry?
how i open multidownloder it giving massage mfc110u.dll missing when i try to install it said opreating sysytem not supported i have window 7 32 bit sp1 but its not working
jhony352 said:
how i open multidownloder it giving massage mfc110u.dll missing when i try to install it said opreating sysytem not supported i have window 7 32 bit sp1 but its not working
Click to expand...
Click to collapse
It worked for me on win 7 32 bit...
Try to reinstall Visual C++ redistributable 2012
https://www.microsoft.com/en-us/download/details.aspx?id=30679
cfg file for s6 sm-g920p
thx its working
Please can you help me from where i can download cfg file for S6 sm-g920p i have sboot.bin file it is in bin format and this file is not open and work in mfc multidownloader
Related
I have done this on a Windows 7 64-bit PC. If you have a Linux, run *.sh instead of *.bat
Required:
1. A formatted micro SD card.
2. Fully charged phone.
3. A windows PC.
4. Android SDK.
5. Backup tools to backup existing data on your Android phone.
Create GoldCard:
A GoldCard turns your device into a generic device, thereby allowing modifications like installing another firmware possible. There are different methods to create a GoldCard but I found this the easiest:
1. A formatted SD card is necessary for this. A GoldCard is nothing but a formatted SD card with modified CID. Insert the SD card in the phone and format the card (Settings -> SD Card & Phone Storage -> Unmount SD Card -> Format SD Card).
2. Download “Klutsch’s GoldCard creation tool” from here. Run this tool as administrator. (this tool is windows only)
3. Enable USB Debugging mode in your phone (Settings -> Applications -> Development -> USB Debugging) and connect the phone to your windows PC.
4. Click on “Get CID” Tab and copy the CID that is generated. In case you get any error, select MMC0.
5. Open the link “http://psas.revskills.de/?q=goldcard“, enter your email id and the CID. You will then get the GoldCard image to the mentioned email id.
6. Download the GoldCard image to PC, from the GoldCard creation tool, click on ‘load GoldCard.img’, select the image that you just downloaded and click on “Patch MMC”.
7. Voila, you now have your GoldCard. Please do not use this card for any other purpose till the rooting process is over and it’s time to downgrade the OS.
Remove the GoldCard and use the primary card till the GoldCard is needed. (not necessary)
Downgrade the OS:
Download the following packages before starting this process:
• Android SDK (copy the SDK to C:\ add C:\androidSDK\Tools to your windows path)
• hack4legendv5.zip
• RUU 1.31 for Legend
Connect your phone to the PC ‘charge only’ mode. copy the contents of hack4legendv5.zip to androidSDK/tools directory and then run the script crackin.bat The phone will reboot couple of times and there will be lot of errors shown in the terminal. In the end look for the line showing permissions for the file /dev/mtd/mtd0. It should look like this:
crwxrwxrwx 1 1001 2002 90, 0 Jul 19 16:19 /dev/mtd/mtd0
Click to expand...
Click to collapse
This means that your phone is ready for OS downgrade.
Now, connect your phone to the PC in ‘charge-only’ mode and execute the file RUU_Legend_HTC_WWE_1.31.405.5_R_Radio_47.26.35.04_ 7.05.35.26L_release_126592_signed.exe and just follow the instructions and the phone will reboot to 1.31 version of firmware. And it’s time for Legend to get rooted. There will be a few errors but don’t get disheartened.
Root the Legend:
Time to use the GoldCard. Insert the GoldCard and connect the phone to the PC in ‘charge only’ mode.
1. Download the file r4-legend-root.zip from here. Unzip the file to a directory and cd to the directory.
2. Switch off your Legend, switch it back on in ‘fast boot’ mode (keep the back button pressed while switching the phone ON). When you see that the phone has booted into fast boot screen.
3. Connect the phone to the PC and run step1-windows.bat
4. After that is over, select RECOVERY option. Fastboot screen –> Boot loader -> recovery. You need to use phone’s volume rocker to move up/down the menu and power button to select the option. The phone screen should now show a phone with red caution sign.
5. From the terminal window, run step2-windows.bat. Once this step is completed, the phone will be back in recovery mode. From the options, select ‘wipe data’ and then select the option to update the ROM, select the file ‘rootedupdate.zip’ from SD card. The rooting process will now start and after few minutes, the phone will boot with rooted firmware.
Moderators and other experienced Members, I know my editing isn't perfect here 'cause I'm in a hurry but this is the guide I followed and I was rooted within 15 minutes. Feel free to edit (Mods) and suggest (Members). Umm... does this belong to the Development section?
Fantastic guide. Really great. I had half a mind to do one myself, no need now. This should help a lot of people. It might also be worth going through the other threads, and pulling out an FAQ with links to relevant posts. I'll help with that if you like.
Get this in the stickies!
ishan_rulz said:
Required:
3. A windows PC.
Click to expand...
Click to collapse
Hmm, Windows? Haven't seen that for several years (thankfully) except on our house, but I can still manage to root...
Sent from my HTC Legend using XDA App
@TheGrammarFreak
Okay, if you have additional points, just write it down... I'll add it next time I edit it.
@BlaY0
I have only tested this on a Windows PC, but I'm sure it'll work on Linux too. Added it as a note before the guide. Thanks.
where do i dl "rootedupdate.zip" or when u do step 1 and step 2 it will be on card or what?
MeBeSad said:
where do i dl "rootedupdate.zip" or when u do step 1 and step 2 it will be on card or what?
Click to expand...
Click to collapse
The scripts push it on there. That's why the download is so big...
Bump. Well... can someone have this moved to the development part.
Any way to root via OS X?
I'm getting this error when trying to get the CID in the gold card tool, what am I doing wrong?
------------------------
* daemon not running. starting it now *
* daemon started successfully *
------------------------
Could not locate CID in output
Im also getting the same error as tecchtalknews and have no idea what is causing it. ps im using a sand disk 2gb sd card that came with the phone, and yes usb debugging is on.
ahh never mind, i just had to sync it with htc sync before i used gold card tools
Does it work for 2.2 devices XD
Sent from my HTC Legend using XDA Premium App
im stuck on .
copy SDK and android SKD to C ... are you suggesting installing the complete SKD and then copying the folder to C instead of C/program files / Android SDK .?
and when double clicking crackin.bat . the terminal shows up for about 4 seconds then disappears and nothing happens on my phone ..
help first time rooter ..
Cheers
ok so my problem is that i click "crackin.bat" my phone reboots several times, but them the cmd closes before i can see if it's "crwxrwxrwx 1 1001 2002 90, 0 Jul 19 16:19 /dev/mtd/mtd0" or not.. however i think it should be because i've already gotten the other, wrong "cr---w--" (or something) and i think i might be doing it right this time, but after that when i go with the "RUU_Legend_HTC_WWE_1.31.405.5_R_Radio_47.26.35.04_ 7.05.35.26L_release_126592_signed.exe" it gives me error "(-5001 : 0x80070002)" and nothing happens .. please help cuz i've whiped all the data to my phone although i had a lot of stuff and i'm really looking forward to this :/ newb rooter, sry :?
am also having the same problem
help
Hello,
I want to install the 2.2 rom, but I dont know how, I've searched here, but I couldnt understand much, the link I've tried are dead or in russian (which confuses me a lot).
So I'd really love if someone could make a step by step tutorial to help me out.
Please, include links.
Thanks
And please, if you can, plz help me understand what is the recovery mode, and how to do so...
Thank again
Follow this thread: http://forum.xda-developers.com/showthread.php?t=857213
If you can't understand...I'll post another guide.
This is a guide I followed from another forum, and posted elsewhere with some minor additions in case anyone had problems.
The guide is from a forum post at the android forums,it is NOT my work, the added bits are mostly what I have found from browsing here and from asking questions. While I can't be held liable if you mess your phone up having done so myself I thought this could helpa few people and save them searching various threads for answers so hope it helps
The guide
To install this ROM you need to have fastboot enabled on your phone. If you have Android 1.6/2.1 installed from LG, then fastboot is not enabled. I will explain how to enable fastboot on your phone (this involves re-flashing/replacing your currently installed firmware):
I am unable to post links yet so you will have to copy and paste the appropriate link into your browser replacing the ** with tt
KDZ Updater Carphone Warehouse Unlocked.zip can be downloaded at h**p://goo.gl/7aRTc - A link to a zip archive with all the files needed to flash to Android version 2.1 with fastboot (Carphone Warehouse Unlocked)
KDZ Updater Europe Open.zip can be downloaded at h**p://goo.gl/BOcYT - A link to a zip archive with all the files needed to flash toAndroid version 2.1 with fastboot (Europe Open)
Download the version that best applies to you, if you live in the UK, I'd recommend you download the Carphone Warehouse Unlocked version, whereas if you live in Europe, I'd recommend the Europe Open version (simple right? )
I live in the UK and used the open rom from Europe as the Carphone Warehouse rom would not install
Now, how to flash these versions; I'll explain in detail how to flash the ROM's from starting with backing up.
Instructions to install ROM with Fastboot:
1. Before you start, make sure you backup all your data by installing the z4root.1.3.0.apk file onto your phone, then open it and choose 'Permanent Root'. Your phone will root and reboot. Then go to the Market and install 'MyBackup Root', open it and do a backup of your apps and personal data (contacts, sms, call log etc.) Once this is done, go to Settings>SD Card and Phone Storage>Unmount SD Card, a notification in the notification bar should appear saying 'SD Card safe to remove'. Remove the battery cover and remove the SD card and store it in a safe place. Then continue to step 2.
2. Extract the .zip file you downloaded to your computer (e.g. your desktop). Open the folder and install MSXML 4.0 SP3 Parser (msxml.msi).
3. Once that has finished, install LGAndroidDriver_WHQL_ML_Ver1.0_All_Win7.exe which are the drivers so your computer will recognize your phone.
4. Next, open KDZ_FW_UPD.exe
(i) Change 'Type' to '3GQCT' *THIS IS A MUST, THE UPDATE WILL NOT WORK OTHERWISE AND YOU MAY BRICK YOUR PHONE*
(ii) Make sure 'PhoneMode' is set to 'DIAG'
(iii) Browse for the 'V20B_00+Fastboot.kdz' file.
5. Prepare the phone by enabling USB Debugging by going to Settings>Applications>Development>Enable USB Debugging and connect the phone to the computer via USB cable and wait for the drivers to install for the phone.
6. Click 'Launch software update' and do not use your computer until the update is complete. The update will take roughly 10-20 mins to complete.
If you have a problem with this try a different rom, this guide offers two to choose from.
Instructions to install CyanogenMod:
Once the update is complete, your phone will reboot, what you need to do is power off the phone and whilst the phone is off, press and hold the 'Camera' button all the way ANDpower on the phone, make sure you hold the 'Camera' button. The phone will display the LG logo and disappear, then display a blank screen. The phone is now in fastboot mode!
Now you want to download this file: Flashing CyanogenMod.zip and extract it to a folder called 'Android' (without the quotes '') on the C: drive (you'll probably need to make this folder yourself.
1. Now open CMD with administrator privileges (Search for CMD in the start menu and right click on 'cmd' and click 'Run as Administrator' )
2. Connect the phone to your computer via USB cable and wait for the necessary drivers to install.
If when connected with a usb cable the computer says "waiting for device" and nothing else happens try installing the fastboot drivers. You can do this by going to the control panel of your pc, from the Windows start menu, opening the list of devices and where you see the one representing your phone (likely, as was the case with me, it will say android and have a yellow exclamation mark over it). Different versions of Windows do things slightly different but what you need to do is simply update the driver by choosing the icons properties box choosing UPDATE or INSTALL DRIVER and when asked pointing it to the folder where you unzipped the drivers.
3. Then go back to the cmd window and type:
Code:
cd C:\Android
(i) Then type:
Code:
fastboot.exe -w
(ii) Once that's completed, type:
Code:
fastboot.exe erase system
(iii) Once that's completed, type:
Code:
fastboot.exe flash system system.img
(iv) Once that's completed, type:
Code:
fastboot.exe flash boot boot.img
(v) Once that's completed, type:
Code:
fastboot.exe reboot
4. Your phone will now reboot with CyanogenMod 6.1.1 (Android 2.2.1). The first boot might take longer than a normal boot.
If your phone stays at a blank screen you simply forgot to do one of the above steps, in which case simply repeat them. It is likely if that happens that you simply forgot the flash boot image instruction.
5. You can now re-insert your SD card and go to Settings>SD Card and Phone Storage>Mount SD Card
Enjoy!
The instructions for flashing both the firmware with fastboot and flashing CyanogenMod are included in the zip archives called 'Readme'. I'll update the links so that you'll always have the most up to date version of CyanogenMod available for download, note that if you choose to update your phone you will loose all your data including apps etc. so backup before you update
And that, with a few comments added by myself, is the guide.
Once you have set your phone up the way you want power off your phone. Hold the HOME and POWER buttons down while the LG logo appears and you will see a menu appear on screen.
Using the volume down key to navigate the different menu choices, and the camera button to select an option choose the BACKUP OR RESTORE option and from the sub menu that it will give you choose BACKUP.
This will make a backup of your phone AND all your data, if you ever mess up an update or think you have damaged your phone in the future simply holdthe POWER and HOME buttons down and when the menu appears choose the RESTORE option
Click to expand...
Click to collapse
You also need fastboot drivers.
http://forum.xda-developers.com/attachment.php?attachmentid=495093&d=1295551234
guide to install openswift
please, anybody who has rights to edit first post of openswift thread,
add this link, is very good guide
http://android.modaco.com/content/lg-gt540-optimus-gt540-modaco-com/329916/a-full-guide-to-getting-android-2-2-on-your-phone-for-total-newbs-like-me/
somoant said:
please, anybody who has rights to edit first post of openswift thread,
add this link, is very good guide
http://android.modaco.com/content/lg-gt540-optimus-gt540-modaco-com/329916/a-full-guide-to-getting-android-2-2-on-your-phone-for-total-newbs-like-me/
Click to expand...
Click to collapse
Oh...there's the link. Been trying to find it! Thx =)
MegaBubbletea said:
Oh...there's the link. Been trying to find it! Thx =)
Click to expand...
Click to collapse
you're welcome
Another question, which one should I donwload?
KDZ Updater Carphone Warehouse Unlocked.zip
KDZ Updater Europe Open.zip
My phone is from US, so both would work?
brunouvn said:
Another question, which one should I donwload?
KDZ Updater Carphone Warehouse Unlocked.zip
KDZ Updater Europe Open.zip
My phone is from US, so both would work?
Click to expand...
Click to collapse
Either one will be fine. Those are just for temporary Rom because they have fastboot. You wont be keeping them.
Sent from my GT540 by MBt
little question... how long does it takes to complete the process? my phone is on download mode for like 30 minutes.. kinda nervous here, its stuck at:
3GQCT : wParam = 205, IParam = 0
btw, internet should be on?
What!? You sure u followed the instructions very carefully? Using the KDZ updater tool and correct settings?
yes, followed step by step
What happens if I cancel the process?
Well...which step are you on at the moment?
Step Complete : C Drive Erase
Wo wo wo...so it's done? Finish flashing v2.1 on ur android with fastboot?
dont understand, its done?
Well...what's happening on screen in the updater? Does your phone reboot now? No more safe mode?
If it is rebooting then it's done. Now all you have to do is get into fastboot mode which means holding CAMERA + POWER when turning on your phone.
on the phone is still download mode and the last line on the updater is:
3GQCT : wParam = 205, IParam = 0
Did you uncheck "Mass Storage Only" in the phone before you flashed? That may be ur problem....or try unmounting the SD.
yea, I think mass storage only was off, and sd card isnt in
What about USB debugging mode? That needs to be checked.
Simplest method of backup eMMC and install unlocked bootloader with TWRP.
May be used for locked and unlocked devices.
Devices: Redmi 3 and Redmi 3 Pro.
Benefits of this method:
1) no need device unlock
2) no need to install MiFlash/MiPhone
3) not need to download and install any ROM
4) it requires only one reboot
Manual:
1) unpack ZIP-file "redmi3_emmcdl_twrp.zip"
2) connect the device to a computer via USB
3) by holding down VolUp + Power run preloader and select "download"
4) if you installed the drivers in the Device Manager, you should see the device "Qualcomm HS-USB QDLoader 9008 (COM21)"
5) in Windows Explorer, open the folder that contains the previously unzipped file emmcdl.exe
6) do partial backup of eMMC: execute dump_emmc.cmd (the first 200 MB is enough)
7) do backup system partitions: execute dump_parts.cmd
8) the contents of the folder dump_emmc and dump_parts need to copy in a safe place!
9) [OPTIONAL] do install the patched bootloader and a special version of TWRP: execute install_aboot_twrp.cmd
10) now you need to reboot the device (you hold VolUp + Power button)
11) [OPTIONAL] boot into TWRP and make a backup current installed firmware (boot, system, data, cust)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
After these actions should not be flashing the ROMs, which contains a emmc_appsboot.mbn and any MBN-files !!!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Waiting for English manual.......... an method to quickly backup/restore bootloader lock state would come really useful as even custom ROMs seem randomly relock BL and unlocking procedure is becoming pita
Sent from my phone by Tapatalk
Downloading flash programmer: prog_emmc_firehose_8936.mbn
Successfully open flash programmer to write: prog_emmc_firehose_8936.mbn
Expecting SAHARA_END_TRANSFER but found: 0
!!!!!!!! WARNING: Flash programmer failed to load trying to continue !!!!!!!!!
Dumping data to file .\dump_parts\aboot.img
Dumping at start sector: 0 for sectors: 0 to file: .\dump_parts\aboot.img
Programming device using SECTOR_SIZE=512
<?xml version = "1.0" ?><data><configure MemoryName="emmc" ZLPAwareHost="1" SkipStorageInit="0" SkipWrite="0" MaxPayloadSizeToTargetInBytes="1048576"/></data>
After backup, how do i restore flashed image?
Do you have the source code of emmcdl.exe?
Can we do this on a linux box?
yangyangnau said:
Do you have the source code of emmcdl.exe?
Can we do this on a linux box?
Click to expand...
Click to collapse
https://github.com/binsys/emmcdl
Thank you, installing now CM13 on Redmi3pro (ido)
Just done my Redmi3 pro with your fine tool. Working like a charm, thank you! Now I'm installing my beloved CM13 on this device - so glad!! You are my hero! :highfive:
Does this mean we do not have to ask a unlock bootloader from Xiaomi?
parphane said:
Does this mean we do not have to ask a unlock bootloader from Xiaomi?
Click to expand...
Click to collapse
@remittor any answer?
parphane said:
Does this mean we do not have to ask a unlock bootloader from Xiaomi?
Click to expand...
Click to collapse
This, please update anyone?
I had error message:
error driver qdloader not found
Press any key to continue
In my device driver redmi 3 was detected as Quallcom hs USB qdloader 9008 com 21
Any ideas to solve my problem
edmone said:
I had error message:
error driver qdloader not found
Press any key to continue
In my device driver redmi 3 was detected as Quallcom hs USB qdloader 9008 com 21
Any ideas to solve my problem
Click to expand...
Click to collapse
I have the same problem...
can someone upload this file to another host..funny i try 23 times to download and in 96% download stopped
parphane said:
Does this mean we do not have to ask a unlock bootloader from Xiaomi?
Click to expand...
Click to collapse
1. This means you shouldn't ask anyone to what you want with your own things
2. This means you shouldn't wipe all your data to 'unlock' what had not intended to have any locks once you bought it to your ownership
3. This means you shouldn't backup (nor 'sync') all your personal data to the Google cloud services just to save them from erasure upon unlocking.
All these bootloader locks have nothing to secure. There is no real problem to solder off eMMC (eMCP) IC and read out all your 'secret' personal data with a HW eMMC/NAND programmer or even generic SD card reader (tiny soldering req'd) for any phone/tab/other MID. The only reason mfr's do solder generic SD's in the BGA cases (called eMMC), hide docs, implement locks, close full file system from user even for reading and exploring and do a bunch of other bad things is intention to force user send all his sensitive personal data to the Google's and other OS/Dev mfr's clouds to make them able to fully control any people's activity. It's a Matrix guys who wants to control your brain and soul not simply some cheap device. Don't give up! Do not 'sync' your personal data with any clouds and do not use any 'accounts' and Gapps at all where possible!
Thank you remittor for the perfect method!
There is also should be used to backup any device's partition's, whole media and state. It will greatly help to recover data in case of the device's SW and even partly eMMC failure. Once a patched aboot will give us ability to write the whole eMMC media, there should be the way to fix OEM's locking data structure to locking back in any cases (e.g. flashing original non-patched aboot). One could find the locking flags and publish results.
remittor said:
Simplest method of backup eMMC and install unlocked bootloader with TWRP.
May be used for locked and unlocked devices.
Devices: Redmi 3 and Redmi 3 Pro.
Benefits of this method:
1) no need device unlock
2) no need to install MiFlash/MiPhone
3) not need to download and install any ROM
4) it requires only one reboot
Manual:
1) unpack ZIP-file "redmi3_emmcdl_twrp.zip"
2) connect the device to a computer via USB
3) by holding down VolUp + Power run preloader and select "download"
4) if you installed the drivers in the Device Manager, you should see the device "Qualcomm HS-USB QDLoader 9008 (COM21)"
5) in Windows Explorer, open the folder that contains the previously unzipped file emmcdl.exe
6) do partial backup of eMMC: execute dump_emmc.cmd (the first 200 MB is enough)
7) do backup system partitions: execute dump_parts.cmd
8) the contents of the folder dump_emmc and dump_parts need to copy in a safe place!
9) [OPTIONAL] do install the patched bootloader and a special version of TWRP: execute install_aboot_twrp.cmd
10) now you need to reboot the device (you hold VolUp + Power button)
11) [OPTIONAL] boot into TWRP and make a backup current installed firmware (boot, system, data, cust)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
After these actions should not be flashing the ROMs, which contains a emmc_appsboot.mbn and any MBN-files !!!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Click to expand...
Click to collapse
hello, redmi 3s prime penguin logo only shows please say solution without any mobile data loss contact - 9106142185
Hello, my name is Marc-Yvan from Douala, Cameroon and I will tell you the whole story about how I successfully unbrick my Android Tablet. My aim is to share with you some tips about how to recover from a desperate situation of having an unusable tablet.
How I hard-bricked my Tablet:
First of all, let me tell you how I hard-bricked my beloved tablet after trying to unlock it from its original network lock. I got this tablet from a relative who live in USA but it was unfortunately network locked to the AT&T network. So I tried to unlock it by multiple means (by myself). I found a cracked software called “Octopus for Samsung” who was said able to unlock any kind of Samsung phones/tablet. When I tried to unlock my Tablet, the software starts the work and then told me that the device will turn off and turn on after a short time. But the Tablet did not turn on anymore and I spend 02 months trying to bring it back from the grave.
Definition:
Let me explain to you what is called a hard-bricked smartphone/tablet. It’s simply a smartphone/tablet which is unusable, doesn’t turn on (desperate black screen) and doesn’t react to any stimulation. But you have to know that these hard-bricked devices are displayed as unrecognized devices when plugged onto a computer. So a hard-bricked device is not a physically damaged device but is a sort of hardly logically damaged device which cannot boot at all and is not recognized by common flash tools such as Odin, etc.
How I unbricked my tablet:
Lucky Context (GOD’s help):
Fortunately, GOD helps me by guiding me through this situation in order to recover from it in a miraculous manner. I will explain it to you in a couple of points:
1- My Tablet was rooted before the incident. I did it by using an application found in play store: “Kingroot.apk”.
2- My Tablet was equipped with some tools like “Es explorer” and “Terminal Emulator”. You will understand how it fortunately helped me before the incident.
3- The real hand of GOD: In my quest of finding a mean to network unlock my tablet, I tried a method which was asking to save some partitions of the eMMC (A kind of processor memory. Sorry but I’m not an expert ). So I saved it to the memory of my Tablet and then transfered it to a folder in my computer (By using command lines with “Terminal Emulator”). This actually helped me after to revive my tablet.
Advice N° 1 (Prevention)
Before trying to explore the whole abilities of your Tablet by flashing it or trying to network unlock it; Do a backup of the primary boot partition of your eMMC by executing this command in the “Terminal Emulator” of your rooted device:
cat /dev/block/mmcblk0> sdcard/mmcblk0.img
Be careful, this command could save the life of your beloved Tablet. This command will actually copy the primary boot partition of your eMMC in a disk image which has the same name. So you have to keep that disk image in a safe place such as your computer or an external removable disk.
Advice N° 2 (Resolution)
The Story:
In my desperate actions trying to revive my hard-bricked tablet, I read tremendous forum posts and tried countless methods. Which lead me to install a new OS in my computer. It was actually Linux Ubuntu 16.4. I found a method which told me to try to write some kind of partitions images down to an SDCard to boot my Tablet with. But the partitions images proposed by the method didn’t succeed in recovering my Tablet. So some days later, when I turn on my computer, I fortunately found a file opened; it was the primary boot partition image file of my tablet that I saved before the incident (The real hand of GOD). So I decided (Inspired by the Holy Spirit) to try the previous method with the original boot partition image file of my tablet.
The Tip:
You will need an SDCard with a correct format (FAT32) and size (16Gb or 32Gb). You will also need to work in a Linux command line terminal. To write the boot partition image in your SDCard you will have to execute this command line:
sudo dd if=mmcblk0.img of=/dev/sdb bs=1024k status=progress
Note: The sd card may not be sdb though. In order to confirm, before writing, browse to /Dev and look at the properties of sdb to ensure it is in fact there (it might be sda, sdb, sdc, etc...). You can also try to unplug and then plug the SDCard to see the changes.
The Last Step (Eureka!!!)
The last step is just to insert the SDCard into the slot of your Hard-Bricked device, Turn it on and then feel its vibration that will let you know that your mission is completed. Your device is alive again.
Conclusion
The only conclusion that I can give is to NEVER GIVE UP when you are trying to solve a problem. You can be closer to the solution than you think.
Good Luck!
What are the chances you would upload the boot partition for me?
I hard bricked mine also, but unfortunately I didn't make a backup. Would you be kind enough to upload the bin file you dumped? I've looked everywhere and no one seems to have an emmc dump of this thing. lol
Hello forumers first of all I apologize for my approximate english I'm french and I talk about english only in forums so I will do my best you to understand myself.
I'm a new user on Androïd (and smartphone too) and after learning basics functions and many docs about this I decide to root my phone.It's new,not second hand so it was never used previously.With your threads to root it I succeed in unlocking bootloader without problems.Then I wanted to install TWRP by following your tutos and other sources (vidéos.......)and at each time fastboot don't load my image.
So I'm looking for solutions in forums and web and nothing works.Here is what I did after installing a win7 rather than my usualy Linux (install problems too )for this work :
use USB2.0 rather than 3.0 to connect my phone
use 2 different cable (original with my phone box and another)
install adb/fastboot on C:\ rather than Program Files (because permissions problems during install)
use one of your threads to redo it (image from shreps)
rename the image many times and another image version too and redownloaded it too
use complete path
use mfastboot v.2 too
This is a capture from terminal after fastboot :
so I spent hours to attempt many combination and reading posts but I don't know where to look for now.
Maybe can I use another recovery than TWRP to root?Which?
For info I'm not a dev
Hmm, one cause may be that you're missing the file extension from the file name. That TWRP image usually has .img on the end
I'd enable file extensions in Windows (here's a tutorial: https://www.howtohaven.com/system/show-file-extensions-in-windows-explorer.shtml ) and also use the Tab key on the keyboard to auto-complete the full file name. Make sure that the file name you're using has the extension (else Windows may not find it).
Also, when you flash TWRP, you may see 'Image not signed or corrupt', that is a normal message as TWRP is not cryptographically signed by Motorola.
With TWRP, you need to also boot directly to the recovery after flashing - easiest way to do this is to press the Volume keys on your device until you see 'Recovery' then press the Power key to select.
Hello echo92,
in my capture it was an attempt without .img extensions I should have pointed out that when I renamed it I attempt many solutions (even just name twrp.img or twrp-athene.img or twrp or twrp-athene or original name with and without extensions etc....).
Thanks for info for display extensions about windows because I looked for manip and not find
I'm under Linux so I didn't use win for many years but I have another pb with devices recognisation by adb and not to solved for the moment.So I install a win especially for rooting my phone it seems to be easier than Linux (and tuto are under windows)
So I will try again all my manips but in a nvidia forum I saw it was a windows issue and they only recommand to let complete path.
It's the most probant solution I have found until now.
I specify when I connect my phone after start it win recognize it normally so.........
I'm going crazy :silly: