Related
BLACK SCREEN ON BOOT ISSUE FIX
First of all Big thanks to my dear friend Ano11 for the bootloader image
If you format /sys_boot by mistake from CWM recovery and you end up with Black screen no NOKIA and only Vibrating and cant fix it on NOKIA Care Suite or NOKIA Flasher this is how to fix it.
Human Beings Issue Details:
by formatting /sys_boot you have deleted the program that will connect your phone to NOKIA Care Suite so it will no longer recognize your phone neither any NOKIA Flasher and now this is how bring it back to let the NOKIA Care recognize it again.
Alians Tech Details about issue:
formatting /sys_boot removes the bootloader which has fastboot, the device will no longer be a phone it'll be just a flash memory with alot of partitions accessible from any linux device. and since the /sys_boot is located on /dev/block/mmcblk0p3 we just need to restore a bootloader image there and it will restore fastboot that will fix everything then with NOKIA Care or NOKIA Flasher etc. "WE HAVE ADB WORKING DO ANYTHING YOU WANT!!!!!!"
Now to how to fix it!!!
Requirements:
1- Ubuntu Live CD (Dont use any other variation or another Linux because i ONLY Tested it on Ubuntu)
2- Download Attachment File.
3- A Good USB cable( i strongly recommend the original cable to avoid problems)
Steps to FIX:
1- Boot up in a Working Ubuntu (or Ubuntu Live CD)
2- Download and extract the attachment in Home Folder
3- Open up Ubuntu Menu and look up (Disks)
4- Remove your NOKIA X Battery and Unplug it from any USB or charger, re-insert battery, then hold Power button untill phone Vibrates then release power button. after you do all that plug it in USB to your computer
** if you have done those steps perfectly you should see a new device in (Disks) application will say(something-qualcomm-something) depends on the type of your phone. you will see a table on the right when you click it that has 3 partitions and then many other partitions grouped up don't touch these at all**
5- click on the third partition from left it should be in size of 52MB.
6- right click it and choose (Restore Disk from an Image).
7- Browse to your Home folder then in (NOKIA X RM980 BOOTLOADER) and choose mmcblk0p3.img
8- it will ask you if you are sure click Restore.
9-Wait for it to finish. when it does close Disks then unplug phone, remove battery, re-insert it, power up your phone.
BANG NOKIA APPEARS!!! The phone is back to life!!! no cloning needed and no NOKIA Care Center Needed. you can now use NOKIA Flasher and NOKIA Care Suite to restore your phone to factory firmware or use XDA Furoms to install CWM back and your favorite Custom ROM
UPDATE
You guys have asked me for the Backup procedure and i promissed to repost it but I did not have time to post so i'm very very sorry for being late!!
How to back up the bootloader partition
start up your nokia x RM-980, enable debugging, connect to USB and find an ADB then give it next comand:
Code:
adb shell
you should be in your phone shell. then:
Code:
dd if=/dev/block/mmcblk0p3 of=/sdcard/mmcblk0p3.img
that will backup your bootloader as mmcblk0p3.img in root of your sdcard
xWaLeEdOoOx said:
Hello guys!
since we all do mistakes, i alongside alot of people have formatted /sys_boot partition on our dear RM-980.
that partition is actually the bootloader and without it the phone bricks.
the signs of that brick is black and no screen lights but a vibration that indecates "PLEASE HELP ME!!"
connecting it to windows will cause seeing a drive that windows can't detect and it will ask to format it which is the worst IDEA EVER!! and fastboot will never detect the phone.
if plugged in to Linux you'll get full control over all phone partitions including internal SD, system, boot, bootloader etc.
its easy to flash images from linux side using gparted or "disks in ubuntu which i use" but also fastboot can't be used.
all we need is an mmcblk0p3 dump to save all dead NOKIA X lives!!
it can be easily done on ADB on any computer if you are willing to help follow the following easy steps:
start up your nokia x RM-980, enable debugging, connect to USB and find an ADB then give it next comand:
Code:
adb shell
you should be in your phone shell. then:
Code:
dd if=/dev/block/mmcblk0p3 of=/sdcard/mmcblk0p3.img
that will backup your bootloader as mmcblk0p3.img in root of your sdcard
now compress that in a zip and donate it here with your phone CODE (you can find it in the back of your phone)
I will collect the bootloaders for all the CODEs you people will send.
i don't think there will be much diffrence between them but.. we need to archive that since Microsoft is banning everything NOKIA X related out there!!
Thank you very much in advance
Click to expand...
Click to collapse
How to flash mmcblk0p3.img on linux pro? Thanks.
nguyentuyen said:
How to flash mmcblk0p3.img on linux pro? Thanks.
Click to expand...
Click to collapse
i will make it easy for you but first i need to test it. so if you have a working bootloader for RM-980 please follow my steps and upload the image on google drive, mega or mediafire and share it with us. i need to test my theory before putting people in danger.
xWaLeEdOoOx said:
i will make it easy for you but first i need to test it. so if you have a working bootloader for RM-980 please follow my steps and upload the image on google drive, mega or mediafire and share it with us. i need to test my theory before putting people in danger.
Click to expand...
Click to collapse
I use nokia X+ rm-1053,if you need i will upload it for you. Thanks
nguyentuyen said:
I use nokia X+ rm-1053,if you need i will upload it for you. Thanks
Click to expand...
Click to collapse
i'm still not sure about NOKIA X+ for where the bootloader is located in the mmc but thank you
xWaLeEdOoOx said:
I will collect the bootloaders for all the CODEs you people will send.
i don't think there will be much diffrence between them but.. we need to archive that since Microsoft is banning everything NOKIA X related out there!!
Thank you very much in advance
Click to expand...
Click to collapse
I uploaded my boot partition in this thread: http://forum.xda-developers.com/showthread.php?t=2784522&page=2
GUYS ITS NOW FIXED and i've updated the TOPIC for the instructions!!! GOOD LUCK
my nokia x is no vibrate no boot no logo no blank screen no charging now is it porsib
xWaLeEdOoOx said:
BLACK SCREEN ON BOOT ISSUE FIX
First of all Big thanks to my dear friend Ano11 for the bootloader image
If you format /sys_boot by mistake from CWM recovery and you end up with Black screen no NOKIA and only Vibrating and cant fix it on NOKIA Care Suite or NOKIA Flasher this is how to fix it.
Human Beings Issue Details:
by formatting /sys_boot you have deleted the program that will connect your phone to NOKIA Care Suite so it will no longer recognize your phone neither any NOKIA Flasher and now this is how bring it back to let the NOKIA Care recognize it again.
Alians Tech Details about issue:
formatting /sys_boot removes the bootloader which has fastboot, the device will no longer be a phone it'll be just a flash memory with alot of partitions accessible from any linux device. and since the /sys_boot is located on /dev/block/mmcblk0p3 we just need to restore a bootloader image there and it will restore fastboot that will fix everything then with NOKIA Care or NOKIA Flasher etc. "WE HAVE ADB WORKING DO ANYTHING YOU WANT!!!!!!"
Now to how to fix it!!!
Requirements:
1- Ubuntu Live CD (Dont use any other variation or another Linux because i ONLY Tested it on Ubuntu)
2- Download Attachment File.
3- A Good USB cable( i strongly recommend the original cable to avoid problems)
Steps to FIX:
1- Boot up in a Working Ubuntu (or Ubuntu Live CD)
2- Download and extract the attachment in Home Folder
3- Open up Ubuntu Menu and look up (Disks)
4- Remove your NOKIA X Battery and Unplug it from any USB or charger, re-insert battery, then hold Power button untill phone Vibrates then release power button. after you do all that plug it in USB to your computer
** if you have done those steps perfectly you should see a new device in (Disks) application will say(something-qualcomm-something) depends on the type of your phone. you will see a table on the right when you click it that has 3 partitions and then many other partitions grouped up don't touch these at all**
5- click on the third partition from left it should be in size of 52MB.
6- right click it and choose (Restore Disk from an Image).
7- Browse to your Home folder then in (NOKIA X RM980 BOOTLOADER) and choose mmcblk0p3.img
8- it will ask you if you are sure click Restore.
9-Wait for it to finish. when it does close Disks then unplug phone, remove battery, re-insert it, power up your phone.
BANG NOKIA APPEARS!!! The phone is back to life!!! no cloning needed and no NOKIA Care Center Needed. you can now use NOKIA Flasher and NOKIA Care Suite to restore your phone to factory firmware or use XDA Furoms to install CWM back and your favorite Custom ROM
Click to expand...
Click to collapse
my noka x rm980 059W119 v2 no power on no vibrate no boot no blank screen not detecting in pc now is it porsibal to repair
javidalana said:
my noka x rm980 059W119 v2 no power on no vibrate no boot no blank screen not detecting in pc now is it porsibal to repair
Click to expand...
Click to collapse
what did you do 1st of all?? and you need to charge your phone, keep it in charger "not pc" over night and then check if it vibrates
Please give any video of whole process because i dont see that opetion you told right click on that partion and you will see restore data from disk...
please help me to live my nxl......
Kunal111 said:
Please give any video of whole process because i dont see that opetion you told right click on that partion and you will see restore data from disk...
please help me to live my nxl......
Click to expand...
Click to collapse
In case you do not see any partitions, In that case you have not only formatted ("emptied") this partition but removed all partitions, I assume. So you have to make a new partition (or even all partitions) prior to restoring the mmcblk0p3.img disk image. I have no experience with doing this on a phone (don't know how critical the location and order of partitions is), but I guess a partition listing of a working Nokia X will help you further. Later today when I am at home I hope I can post the partition listing for you.
Help me
I have one problem how to flash that mmcblk0p3.img on nokia x
i download all file alos ubuntu .
Kunal111 said:
I have one problem how to flash that mmcblk0p3.img on nokia x
i download all file alos ubuntu .
Click to expand...
Click to collapse
It might help if you describe exactly what you are doing...
Is your device recognized as Qualcomm something at all?
In order to get it recognized on my Windows computer as Qualcomm device, I have to boot into bootloader mode, i.e.:
BootLoader Mode:
1. Turn off your device
2. Remove wires and battery
3. Hold on Volume + Key while you connect USB
4. Device should be detected as Qualcomm CDMA Technologies MSM
(copied from http://forum.xda-developers.com/showthread.php?t=2667572
So a different procedure as what the OP mentioned.
You so might try that on Ubuntu as well...
5-click on the third partition from left it should be in size of 52MB.
6- right click it and choose (Restore Disk from an Image).
I'hv not done only this process......
please help me how to restore
Thanxx in advanced
Kunal111 said:
5-click on the third partition from left it should be in size of 52MB.
6- right click it and choose (Restore Disk from an Image).
I'hv not done only this process......
please help me how to restore
Thanxx in advanced
Click to expand...
Click to collapse
Second attempt: Is your device recognized as a Qualcomm device? Do you see it in the device list on the left?
help
Yes , but how can i flast that img file on 52mb partion
Kunal111 said:
Yes , but how can i flast that img file on 52mb partion
Click to expand...
Click to collapse
And do you see the 52 MB partition on the right? What happens if you select it and rightclick on it, do you see the option "Restore partition from image" or something similar?
It helps if you post in detail what your problem is, otherwise we end up in many question-answer posts... Like we are doing now...
xWaLeEdOoOx said:
BLACK SCREEN ON BOOT ISSUE FIX
First of all Big thanks to my dear friend Ano11 for the bootloader image
If you format /sys_boot by mistake from CWM recovery and you end up with Black screen no NOKIA and only Vibrating and cant fix it on NOKIA Care Suite or NOKIA Flasher this is how to fix it.
Click to expand...
Click to collapse
Hi there,
First of all: thanks for the acknowledgements
This morning my son came to me complaining that his Nokia X was not working anymore.
I checked it and: no recovery mode, no bootloader access. Black screen, no Nokia logo, no vibration (!).
I thought: would I need this thread and my own bootloader image now?? That would be a coincidence!
Connecting the phone to the pc using USB still resulted in "Qualcomm device detected", but nothing more.
Then I noticed that the battery felt a bit loose inside the phone, also I noticed a crack in the plastic cover of the phone.
A closer look to the battery connector of the phone showed that two of them were really bent!
So I opened the casing to have a better access to the connector (really very easy using a torx T5 screw driver), nowhere these terrible plastic clips to break off when you open the device like in other phone brands...
Using my reading glasses and a magnifying glass I bent the clips back -> the phone was revived.
I guess my son must have dropped the phone real hard which resulted in bending these clips...
So people, the take home message is: also check the battery connectors closely when you experience similar problems.
Can you tell me how to back up my bootloader to an img? I have Nokia_XL.
I'm on elementary OS Freya.
ADB and fastboot are installed successfully.
vishalbiswas said:
Can you tell me how to back up my bootloader to an img? I have Nokia_XL.
I'm on elementary OS Freya.
ADB and fastboot are installed successfully.
Click to expand...
Click to collapse
Take a look at the second post, you can find the procedure in the quotes from the orginal posting of the OP (the OP removed it later from his post).
@op / @ xWaLeEdOoOx : maybe good to add this the procedure to your post again.
You may need to check if the partition name is the same for the XL version, e.g. by looking at the TWRP log files.
I didn't know when I was formating my phone in CWS recovery mode. But when I tried to restart the phone, is showed me blank screen and even there is no vibration of starting.
I am really mad at this, how to get back to start my phone?
if you wanna fresh nokia x stock rom then download nokia care suite from here - http://www.seidea.com/2015/05/20/nokia-care-suite-pst-5-0-5-6-134-1513/
and stock nokia rom from here - http://cellomania.com/ffu/
pyumredkar said:
if you wanna fresh nokia x stock rom then download nokia care suite from here - http://www.seidea.com/2015/05/20/nokia-care-suite-pst-5-0-5-6-134-1513/
and stock nokia rom from here - http://cellomania.com/ffu/
Click to expand...
Click to collapse
I will try what you suggest me.
But there is NO VIBRATION, and NO DISPLAY. I should slap myself for formatting the phone without understanding the risk.
Love Psyche said:
I will try what you suggest me.
But there is NO VIBRATION, and NO DISPLAY. I should slap myself for formatting the phone without understanding the risk.
Click to expand...
Click to collapse
formatting system partition from custom recovery also formats bootloader partition. you need to follow this guide - http://forum.xda-developers.com/nokia-x/general/fix-blank-screen-boot-format-sysboot-t3126617
pyumredkar said:
formatting system partition from custom recovery also formats bootloader partition. you need to follow this guide - http://forum.xda-developers.com/nokia-x/general/fix-blank-screen-boot-format-sysboot-t3126617
Click to expand...
Click to collapse
Is it worked for when there is NO vibration along with blank screen?
And if so, please upload bootloader for RM-1053 model (X+).
I would suggest you that you must flash nokia x bootloader partition for right now until ur device starts. because when you flash nokia x+ rom with care suite your appropriate bootloader img will be flashed correctly from nokia care suite
In the guide you provided:http://forum.xda-developers.com/nokia-x/general/fix-blank-screen-boot-format-sysboot-t3126617, at 4th point of "How to fix", it said your phone should be vibrated.
But my phone cannot vibrate. Have you got my point? It has NO VIBRATION, not just only blank screen.
it is the last option for repairing ur device, anotherly it seems hardbricked and Microsoft stopped developing repairing spare parts of the device. so no any other hope.
Do you mean, I have no solution for this issue?
maybe
I still have hope and waiting for help about the issue.
I thought I would have a solution, but nobody showed me a solution. Maybe there is no solution!
At first check, if battery is properly inserted (maybe some pins are bent?), then recharge battery.
Next try again with this tutorial: http://forum.xda-developers.com/nokia-x/general/fix-blank-screen-boot-format-sysboot-t3126617
You can download latest Nokia X bootloader from http://cellomania.com/ffu/ (type your CODE from sticker inside device and download RM980_1.2.4.1_boot.img file)
If it won't work, run terminal (in Ubuntu), connect phone again, wait some seconds, type
Code:
dmesg >> ~/dmesg.log
and send dmesg.log file (use file manager to find it) to any pastebin-like service, so we'll be able to check, if Ubuntu can detect the phone.
Super-SD The bootable Android SD-Card
This is a SD card that has been created using the Dragonboard 410 Boot Tools. LINK IS FOR REFERENCE TO THE TOOLS AND METHOD USED
https://git.linaro.org/landing-team...mmit/ecdf098b42ed9e561b8249bcbf6f883e8151a3bc
Very easy to make and use this sd card. Even for beginners. !! :fingers-crossed:
Benifits
Boots the android system completely from the sd card.
Both the Userdata and System are run on the card allowing the storage size to be increased both for system and userdata.
Runs a rooted system without Unlocking the Bootloader or making any modifications to the internal phone memory.
Changes you make will be applied to the SD - Card so by removing the SD Card and rebooting the phone will be in the original condition.
WILL NOT VOID YOUR WARRANTY !!!!!!!!!! :highfive: :good: :silly:
No Chance of Bricking the device.
The sd card can be mounted and changes applied to it using linux.
This removes any restrictions that would be present when attempting the same changes to the devices internal memory.
You can use this as a daily runner as well as using this to test anything.
Including Porting of roms.
The best thing is if anything ever went wrong during a test the phone will be undamaged.
Simply removing the sd card puts you back to factory state.
I could go on and on and on because there are so many benefits and uses for this.
KEY Features.
PRE-Rooted : When booting from the sd-card Super SU is already installed so Root is available.
Download Mode : Boots into Download Mode with Full S-OFF and Unlocked Status <-- ONLY WITH BOOT FROM the SD-Card.
Write-Protections :With the s-off Status SD-Card you can mount /system RW and flash partitions like FRP and MISC. Note that some partitions are Still Write Protected ( PG1FS) (Board_Info) (SEC).
FTM Mode : By holding volume up and the power key to boot the device will boot to FTM mode. If you can mount the last partition of the sd card as /mnt/media/ext_sd you should be able to use the device info tool to gain S-off and Boot Loader Unlock.
**********************************************************************************************************************************************************************************
NOTE -->> You can not unlock the boot-loader using this Card.UNLOCKING THE BOOT LOADER IS AN OPTION NOT A REQUIREMENT, CARD WORKS WITH A LOCKED BOOT LOADERTo Unlock Boot Loader See Here -->> https://forum.xda-developers.com/desire-526/general/verizon-htc-desire-526-boot-loader-root-t3587118**********************************************************************************************************************************************************************************
BOOT TWRP RECOVERY FROM SD-CARD WITH FisH ( Bootloader - Locked - is OK )
https://forum.xda-developers.com/an...locked-fish-hack-to-boot-want-device-t3578373
Say thanks to @steadfasterX for developing FisH.
I ported FisH for the Desire 526.
IMPORTANT INFORMATION FOR BOOTING / USING FISH
DO NOT FLASH ANY MODIFIED BOOT IMAGE OR RECOVERY IMAGE UNLESS YOU UNLOCKED YOUR BOOTLOADER FIRST
( WILL CAUSE A SOFT BRICK IF THE BOOT LOADER IS LOCKED )
INSTRUCTIONS TO MAKE SD-CARD AND USE FISH ARE BELOW
PLEASE HIT THE THANKS BUTTON
What sd card to use ??
SD - CARD SELECTION / PURCHASING GUIDE
STEP #1 GET THE BEST SD CARD YOU CAN
Since we are booting and running Android with the SD - Card a fast card is required. The card pictured is rated at
Please make sure that the SD Card you use has V30 or V60 or V90 on it. (See the pic below.)
Transfer speeds of up to 95 MB/s
Class 10, UHS speed class 3 (U3) and video speed class 30 (V30) ratings
{
"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 fastest cards on the marketWITH A CARD LIKE THIS YOUR DEVICE WILL RUN LIKE THE WIND ( THIS CARD HAS READ WRITE SPEEDS = TO THE INTERNAL EMMC )
https://www.amazon.com/Lexar-Profes...3212586&sr=8-13&keywords=UHS+ii+micro+sd+card
High-speed performance - leverages UHS-II technology (U3) for a read transfer speed up to 1800x (270MB/s)
Please note that I have not tested cards greater than 32GB. Anything greater than 32GB may need extra work to make operational.
Ultimately I plan to run a 128GB card with the capability of booting and running linux on The Phone. :victory:
How to make the card
Flashing the Image file to the SD-Card
STEP #1 Download and install Win32DiskImager
Program info -->> https://wiki.ubuntu.com/Win32DiskImager
Program Download -->> https://sourceforge.net/projects/win32diskimager/
STEP #2 Download the SD-Card Image and unzip the file
http://www.mediafire.com/file/c2h48ksguo2m8ja/HTC-526-Boot.zip
A) Put the SD Card in your computer. USB or standard Card Reader is Fine.
B) Open Win32DiskImager (SEE Screen shot below for Use)
C) Click on write and select YES at the warning. The SD Card will be made
THE BURN PROCESS AFTER COMPLETED
AFTER YOU HAVE USED DISK IMAGER TO MAKE THE CARD IF YOU RE-INSERT THE CARD IN WINDOWS IT WILL TELL YOU YOU NEED TO FORMAT IT. DO NOT FORMAT IT. WINDOWS CAN NOT READ THIS DISK PROPERLY. LINUX / UBUNTU CAN PROPERLY MOUNT / READ THE DISK.
POWER OFF PHONE :
INSERT SD-CARD INTO PHONE :
POWER ON PHONE:
ENJOY RUNNING ANDROID ON THE SD
Booting FisH to run TWRP
How to BOOT FisH and run TWRP with a LOCKED Boot Loader
After you have made the sd-card and it boots properly into system you will also be able to use FisH.
Follow these steps to boot into TWRP.
This is a special modified build of TWRP.
Please give thanks to @steadfasterX for developing FisH.
https://forum.xda-developers.com/an...locked-fish-hack-to-boot-want-device-t3578373
FOLLOW THESE STEPS EXACTLY - DO NOT DO ANYTHING DIFFERENT
Step #1 : Power the device off completely and UNPLUG the USB if the phone was connected
Step #2 : Press power button to turn on like normal [SDCARD MUST BE IN THE DEVICE]
Step #3 : Get used to the boot sequence.
When the device is booting up from the sd card you should have noticed some minor differences.
There is a musical chime that you do not have unless the sd card is booting.
There is a phone vibration at almost the same time as the chime.
There is a phone vibration several seconds after the chime.
The RED VERIZON logo NEVER appears.
After you are familiar with how the device boots you are ready to boot FisH.
Step #4 : As soon as you hear the musical chime and the phone vibrates
Press and hold in the VOLUME UP key until the phone vibrates again.
Step #5 : DON'T RUSH THE FISH OR it WILL SWIM AWAY
You have to be very patient here.
WHEN FISH IS BOOTING THE SCREEN WILL GO OFF AND HITTING BUTTONS WONT DO ANYTHING.
(YOUR PHONE IS NOT BRICKED )
A lot of things are going on behind the scenes, the sd-card boots a little slower to begin with initially.
We are killing everything that is running on the phone and re-setting the processor to Hi-Jack the Boot.
The processes are restarted and the TWRP ramdisk is getting loaded from the SD Card into RAM.
I'm pretty sure this is all going on wile only running 1 thread of the processor. ( ALL THIS IS VERY SLOW )
Step #5 : After the screen goes black !!
DO NOT TOUCH a SINGLE BUTTON or PLUG THE PHONE IN for 5 Minutes DO NOT TOUCH a SINGLE BUTTON or PLUG THE PHONE IN for 5 Minutes DO NOT TOUCH a SINGLE BUTTON or PLUG THE PHONE IN for 5 Minutes
Wait for 5 minutes. Longer is ok but do not touch anything for 5 minuets. This = 300 seconds.
If you get impatient don't worry, no damage will be done to the phone, :good: but there is a good chance that all of the processes may not initialize so some things could end up not working until you re-boot.
After the 5 minutes wait is over press the power button to turn on the screen. A quick short push.
You will be greeted by the TWRP Recovery.
If you want to use adb shell.
Once you are in TWRP go to Advanced and then Mounts.
Check the box next to system to mount the system partition.
Now adb shell and commands will work. You will have BusyBox commands available as well as all normal shell commands.
But what ???? Why is my shell not starting as root ???
When we boot into fish we are not booting in recovery mode. We are booting into Normal /System Boot Mode.
( THE DEVICE REALIZES THIS and starts shell as normal user. )
To get root access in TWRP.
Open the TWRP File Explorer.
In the root directory there is folder SuperSU.
Copy the file SU and paste it into /system/bin
Using the file explorer go to folder /system/bin
Change the permission of file SU to 777.
Now if you start adb shell.
Type
su
There is your root access. I will patch this in a future release.
Congratulations,
Your $35.00 chepo device can now do a hell of a lot more now than some of the High End Expensive ones.
TO RETURN TO NORMAL MODE JUST REBOOT LIKE NORMAL
OTHER THAN NOTED TWRP OPERATION IS AS USUAL
Do not FLASH a modified BOOT or RECOVERY if your Boot Loader is LOCKED
Unlock the BOOT Loader if you want to run TWRP through normal recovery or if you want to run a custom Boot.img
TWRP ONLY AFTER YOU HAVE UNLOCKED THE BOOT LOADER
Install TWRP by normal method.
Boot into download mode first then issue command.
Code:
fastboot flash recovery TWRP.img
http://www.mediafire.com/file/g3h14psl1m40wmi/TWRP.img <-- This one is patched so Touch Screen WORKS.
Very nice @BigCountry907 ! Your work is really appreciated and I'm glad to see this here
Just wondering which FIsH version do you use now? I have released a recent new one a while ago which should improve speed in many ways.. hopefully for your approach as well.
.
steadfasterX said:
Very nice @BigCountry907 ! Your work is really appreciated and I'm glad to see this here
Just wondering which FIsH version do you use now? I have released a recent new one a while ago which should improve speed in many ways.. hopefully for your approach as well.
.
Click to expand...
Click to collapse
@steadfasterX
I'm running the original release of FisH.
FisH will boot up faster than 5 min at times. But it depends on the SD Card Speed and other things.
During my test what i found was if I got in a hurry and didn't give enough time occasionally some things would not fully initialize.
Giving enough time for everything to initialize, always worked.
Thanks again for your work @steadfasterX .
Since you have released an updated version I will try it out.
This is one of the many benefits of the booting SD card.
All I have to do is pull the card out of the device and pop it in the computer running linux to have direct access to any of the partitions in my file explorer.
does this image just work for this type of model ? or how would you make it work for a galaxy J ?
Possible Port to Other Devices
Tonyg27 said:
does this image just work for this type of model ? or how would you make it work for a galaxy J ?
Click to expand...
Click to collapse
@Tonyg27
This is an interesting question ? There is some testing going on with other devices.
This image is good for the desire 526 ( FULL BOOT TO SYSTEM )
The image created for the 526 boot loader unlock will not produce a system boot but it will work in multiple devices to unlock the boot loader. This has been tested on a desire 526 desire 626s and a desire 530.
Confirmed working !
So heres the catch. All 3 of those / 526 626s and 530 are all msm8909 chipsets.
And they are all HTC.
@nailyk
Has reported to see minor differences in a Super-Soft Brick on a sony Xperia. -->> Bricked with no Signs of Life
There are many other reports of individuals running bricked devices simply by using a similar sd card method.
The common denominator is that they are all MSM -->> Qualcomm Chip Sets.
Depending on how the manufacturer compiled your aboot... Little Kernel
The Qualcomm chipset supports this by default provided the vendor like HTC or Sony or LG has not turned it off.
Now if you can run unsigned " Patched or Compiled " Aboot == Little Kernel then you can do this.
Normally or by default Q-comm has Little Kernel built so that if the device internal emmc dies hen it will boot the external sd card provided that the proper GPT and Partition Images exsist on the SD Card.
I believe this is a QComm alternative for the partition.xml and firehose.
Hard to say.
I am currently testing this with a couple lg devices.
I am positive that the same method to create the sd card could be used to create cards for other devices.
It will take porting and some work.
I will post a Universal tutorial in the dev section soon.
BigCountry907 said:
@Tonyg27
This is an interesting question ? There is some testing going on with other devices.
This image is good for the desire 526 ( FULL BOOT TO SYSTEM )
The image created for the 526 boot loader unlock will not produce a system boot but it will work in multiple devices to unlock the boot loader. This has been tested on a desire 526 desire 626s and a desire 530.
Confirmed working !
So heres the catch. All 3 of those / 526 626s and 530 are all msm8909 chipsets.
And they are all HTC.
@nailyk
Has reported to see minor differences in a Super-Soft Brick on a sony Xperia. -->> Bricked with no Signs of Life
There are many other reports of individuals running bricked devices simply by using a similar sd card method.
The common denominator is that they are all MSM -->> Qualcomm Chip Sets.
Depending on how the manufacturer compiled your aboot... Little Kernel
The Qualcomm chipset supports this by default provided the vendor like HTC or Sony or LG has not turned it off.
Now if you can run unsigned " Patched or Compiled " Aboot == Little Kernel then you can do this.
Normally or by default Q-comm has Little Kernel built so that if the device internal emmc dies hen it will boot the external sd card provided that the proper GPT and Partition Images exsist on the SD Card.
I believe this is a QComm alternative for the partition.xml and firehose.
Hard to say.
I am currently testing this with a couple lg devices.
I am positive that the same method to create the sd card could be used to create cards for other devices.
It will take porting and some work.
I will post a Universal tutorial in the dev section soon.
Click to expand...
Click to collapse
Many thanks.
I think the sdcard trick could work on Sony's too. I scheduled to work on this this weekend.
I will first try hammerhead (nexus 5) aboot and all partitions (except LCD panels and some other things device wont care to boot) they are the same device (same soc, same usb, same memory chip, etc...) so I have a bit of hope.
Then I will try your patched aboot + s1. If am able to build that aboot, maybe I should be able to customize it to fit Sony's cr*p requirements.
Making this Sony compatible will be pleasant for a lot of people
Anyway thanks a lot for the trick and keep up the good work :good:
I did all as the instructions said and my phone boot and after the htc logo it goes black and just sits there blank
agree with previous poster, doesn't work. Followed instructions exactly and phone just goes to blank screen after HTC logo on boot.
the boot zip is for the desire 626
@BigCountry907
I followed your directions to the tee, the phone boots up fine, however, I do not have wifi at all it's completely greyed out. Is there any way to fix it so I can use wifi?
Unsupported sandisk sd card
When I put the sd card into my HTC Desire 530 (verizon post-paid android 7.0), and turn it on, I immediately get the notification "unsupported sandisk sd card, this device doesn't support this sandisk sd card"
What if we don't have a top volume rocker?
My phone only has a decrease volume button that's functional.
Im having similar issues with the Wi-Fi network and the cellular data network being greyed out. Ive been trying all kinds of things for couple days. Nothing seems to work. Thanks for your help!
Can I get a new link to bootable image please?
Pretty much what the title said. LOL I have been searching for a good link for the bootable desire 526 image but they all seem to be dead on every thread. Can someone please provide me with a new link for this file?
**** working now! Thanks a lot!
Can i use it for my s8 active (g892u)?. My device has Snapdragon 835 (msm8998). It has locked bootloader and can not unlock. But it had rooted.
I have backup starting 150MB of sda partition.. get it from link, use class 10 SDCARD 16GB atleast i have tested, format sdcard with FAT32, open win32 disk imager, write unbrick img to sdcard. Remove battery, put sdcard in your dead xt1766, put battery, press volume down and insert usb cable.. you will see fastboot menu.. flash latest xt1766 from Motorola firmware.
That's all folks!
Link to debrick img..
https://mega.nz/#!NmwjWJ7a!shXGk8euTf000ehVsveRy0ZPVj3tyDxRV15m7NS_7dk
Hi Thanks For This Detailed How-To I Hope This Will Help A Lot Of People Since The Blank-Flash Dont Work.
---------- Post added at 04:33 PM ---------- Previous post was at 04:29 PM ----------
And How This Work The Sd Card Is Used Just To Bring Fastboot And Flash To the EMMC or Flash To The SD-Card And Use The System on it ?
Salik Iqbal said:
I have backup starting 150MB of sda partition.. get it from link, use class 10 SDCARD 16GB atleast i have tested, format sdcard with FAT32, open win32 disk imager, write unbrick img to sdcard. Remove battery, put sdcard in your dead xt1766, put battery, press volume down and insert usb cable.. you will see fastboot menu.. flash latest xt1766 from Motorola firmware.
That's all folks!
Link to debrick img..
https://mega.nz/#!NmwjWJ7a!shXGk8euTf000ehVsveRy0ZPVj3tyDxRV15m7NS_7dk
Click to expand...
Click to collapse
This is good stuff. Nice to know there's a working unbrick method for the xt1766. Nice work OP.
ozmage said:
Hi Thanks For This Detailed How-To I Hope This Will Help A Lot Of People Since The Blank-Flash Dont Work.
---------- Post added at 04:33 PM ---------- Previous post was at 04:29 PM ----------
And How This Work The Sd Card Is Used Just To Bring Fastboot And Flash To the EMMC or Flash To The SD-Card And Use The Systematic on it ?
Click to expand...
Click to collapse
When you see fastboot use ur finger nail to just slide sdcard little, it will deattach the sdcard from phone, flash phone using rsd lite will fixed it like it was before.
ozmage said:
Hi Thanks For This Detailed How-To I Hope This Will Help A Lot Of People Since The Blank-Flash Dont Work.
---------- Post added at 04:33 PM ---------- Previous post was at 04:29 PM ----------
And How This Work The Sd Card Is Used Just To Bring Fastboot And Flash To the EMMC or Flash To The SD-Card And Use The System on it ?
Click to expand...
Click to collapse
If downgrade SBL1 in Moto E4 by flashing older bootloader.img on (bootloader unlocked phone or by fastboot flash sbl1 old_sbl1) the phone becomes bricked and it goes to Emergency download mode (EDL / QHS_BULK 9008).
by writing a backup of mmcblk0 (with at least a few hundred MBs - that contains sbl1 and other bootloaders) on good quality SD card is enough to fetch phone to bootloader/fastboot on many qcom Motorola phone. I think it works this way: if bootloader is erased or old in phone and it goes to 9008 and you put SD card with latest bootloader in it, then eMMC tries to boot from SD card. It is kind of secondary option for eMMC to boot or something else.... I remember I used to repair Samsung qcom and exynos phones this way a few years back.
How to create a 256 MB debrick/unbrick/super magic file from a working Motorola phones:
1. rooted phone by any means or unlocked bootloader + twrp.
2. with terminal if rooted type su first then : dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1024 count=2621244
2a. with cmd if twrp: adb shell dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1024 count=2621244
This will make a 256mb debrick/unbrick/super magic file on your sdcard....
copy debrick.img from SD card to PC or pull using adb pull /sdcard/debrick.img - writing file to SD card I believe is explained in the first post.
How to create a debrick file from E4 Verizon phone that cannot bootloader unlock or root ???
Well, you could use Verizon Software Assistant Motorola for this and connect a working phone on fastboot mode, it will download most recent repair file that includes mbm and mbm-ci - that contains blank flash for many new Motorola phones.
Another way is by using MetroPCS /T-Mobile debrick file on Verizon phone (BB.32 bootloader is latest). Because both are MSM8917 CPU and both have BB.32 bootloader. Last time I repaired a Verizon phone with SD card method and using a debrick file from MetroPCS 64-6 version. If you need file, let me know. I can upload it tomorrow....
Cheers guys!
---------- Post added at 10:34 PM ---------- Previous post was at 10:23 PM ----------
Salik Iqbal said:
When you see fastboot use ur finger nail to just slide sdcard little, it will deattach the sdcard from phone, flash phone using rsd lite will fixed it like it was before.
Click to expand...
Click to collapse
There is no need for SD card to detach, because fastboot mode will not flash anything on SD card.... It just boots from SD card and nothing else
ozmage said:
Hi Thanks For This Detailed How-To I Hope This Will Help A Lot Of People Since The Blank-Flash Dont Work.
---------- Post added at 04:33 PM ---------- Previous post was at 04:29 PM ----------
And How This Work The Sd Card Is Used Just To Bring Fastboot And Flash To the EMMC or Flash To The SD-Card And Use The System on it ?
Click to expand...
Click to collapse
ALI12 said:
If downgrade SBL1 in Moto E4 by flashing older bootloader.img on (bootloader unlocked phone or by fastboot flash sbl1 old_sbl1) the phone becomes bricked and it goes to Emergency download mode (EDL / QHS_BULK 9008).
by writing a backup of mmcblk0 (with at least a few hundred MBs - that contains sbl1 and other bootloaders) on good quality SD card is enough to fetch phone to bootloader/fastboot on many qcom Motorola phone. I think it works this way: if bootloader is erased or old in phone and it goes to 9008 and you put SD card with latest bootloader in it, then eMMC tries to boot from SD card. It is kind of secondary option for eMMC to boot or something else.... I remember I used to repair Samsung qcom and exynos phones this way a few years back.
How to create a 256 MB debrick/unbrick/super magic file from a working Motorola phones:
1. rooted phone by any means or unlocked bootloader + twrp.
2. with terminal if rooted type su first then : dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1024 count=2621244
2a. with cmd if twrp: adb shell dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1024 count=2621244
This will make a 256mb debrick/unbrick/super magic file on your sdcard....
copy debrick.img from SD card to PC or pull using adb pull /sdcard/debrick.img - writing file to SD card I believe is explained in the first post.
How to create a debrick file from E4 Verizon phone that cannot bootloader unlock or root ???
Well, you could use Verizon Software Assistant Motorola for this and connect a working phone on fastboot mode, it will download most recent repair file that includes mbm and mbm-ci - that contains blank flash for many new Motorola phones.
Another way is by using MetroPCS /T-Mobile debrick file on Verizon phone (BB.32 bootloader is latest). Because both are MSM8917 CPU and both have BB.32 bootloader. Last time I repaired a Verizon phone with SD card method and using a debrick file from MetroPCS 64-6 version. If you need file, let me know. I can upload it tomorrow....
Cheers guys!
---------- Post added at 10:34 PM ---------- Previous post was at 10:23 PM ----------
There is no need for SD card to detach, because fastboot mode will not flash anything on SD card.... It just boots from SD card and nothing else
Click to expand...
Click to collapse
Good guide on unbrick for Motorola phones! Yes its not nessecary to remove sdcard but i don't know if old phones are used by sdcard as primary storage after bricked. Too avoid replying everyone's post for sdcard deattach i preferred saying yes deattach it
Salik Iqbal said:
Good guide on unbrick for Motorola phones! Yes its not nessecary to remove sdcard but i don't know if old phones are used by sdcard as primary storage after bricked. Too avoid replying everyone's post for sdcard deattach i preferred saying yes deattach it
Click to expand...
Click to collapse
one of the colleague confirmed it worked on Motorola Titan which I believe is MSM8226 / older phone. I haven't tested it myself, so....
Salik Iqbal said:
I have backup starting 150MB of sda partition.. get it from link, use class 10 SDCARD 16GB atleast i have tested, format sdcard with FAT32, open win32 disk imager, write unbrick img to sdcard. Remove battery, put sdcard in your dead xt1766, put battery, press volume down and insert usb cable.. you will see fastboot menu.. flash latest xt1766 from Motorola firmware.
That's all folks!
Link to debrick img..
https://mega.nz/#!NmwjWJ7a!shXGk8euTf000ehVsveRy0ZPVj3tyDxRV15m7NS_7dk
Click to expand...
Click to collapse
but after that phone is coming on NO SERVICE and Radio is OFF. how do i fix it?
skyrio said:
but after that phone is coming on NO SERVICE and Radio is OFF. how do i fix it?
Click to expand...
Click to collapse
Try this
fastboot oem config bootmode " "
fastboot oem fb_mode_set
fastboot -w
fastboot oem fb_mode_clear
fastboot reset
Moto E4 XT 1765 hard brick
Salik Iqbal said:
Good guide on unbrick for Motorola phones! Yes its not nessecary to remove sdcard but i don't know if old phones are used by sdcard as primary storage after bricked. Too avoid replying everyone's post for sdcard deattach i preferred saying yes deattach it
Click to expand...
Click to collapse
ALI12 said:
If downgrade SBL1 in Moto E4 by flashing older bootloader.img on (bootloader unlocked phone or by fastboot flash sbl1 old_sbl1) the phone becomes bricked and it goes to Emergency download mode (EDL / QHS_BULK 9008).
by writing a backup of mmcblk0 (with at least a few hundred MBs - that contains sbl1 and other bootloaders) on good quality SD card is enough to fetch phone to bootloader/fastboot on many qcom Motorola phone. I think it works this way: if bootloader is erased or old in phone and it goes to 9008 and you put SD card with latest bootloader in it, then eMMC tries to boot from SD card. It is kind of secondary option for eMMC to boot or something else.... I remember I used to repair Samsung qcom and exynos phones this way a few years back.
How to create a 256 MB debrick/unbrick/super magic file from a working Motorola phones:
1. rooted phone by any means or unlocked bootloader + twrp.
2. with terminal if rooted type su first then : dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1024 count=2621244
2a. with cmd if twrp: adb shell dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1024 count=2621244
This will make a 256mb debrick/unbrick/super magic file on your sdcard....
copy debrick.img from SD card to PC or pull using adb pull /sdcard/debrick.img - writing file to SD card I believe is explained in the first post.
How to create a debrick file from E4 Verizon phone that cannot bootloader unlock or root ???
Well, you could use Verizon Software Assistant Motorola for this and connect a working phone on fastboot mode, it will download most recent repair file that includes mbm and mbm-ci - that contains blank flash for many new Motorola phones.
Another way is by using MetroPCS /T-Mobile debrick file on Verizon phone (BB.32 bootloader is latest). Because both are MSM8917 CPU and both have BB.32 bootloader. Last time I repaired a Verizon phone with SD card method and using a debrick file from MetroPCS 64-6 version. If you need file, let me know. I can upload it tomorrow....
Cheers guys!
---------- Post added at 10:34 PM ---------- Previous post was at 10:23 PM ----------
There is no need for SD card to detach, because fastboot mode will not flash anything on SD card.... It just boots from SD card and nothing else
Click to expand...
Click to collapse
i have brick Moto E4 XT 1765
CPU MSM 8917
metropcs
please help me, flash.bat not work i have trying lots of methood but not success
can i try above methood on my brick device
or plz give me suitable debrick file for my device
ALI12 said:
If downgrade SBL1 in Moto E4 by flashing older bootloader.img on (bootloader unlocked phone or by fastboot flash sbl1 old_sbl1) the phone becomes bricked and it goes to Emergency download mode (EDL / QHS_BULK 9008).
by writing a backup of mmcblk0 (with at least a few hundred MBs - that contains sbl1 and other bootloaders) on good quality SD card is enough to fetch phone to bootloader/fastboot on many qcom Motorola phone. I think it works this way: if bootloader is erased or old in phone and it goes to 9008 and you put SD card with latest bootloader in it, then eMMC tries to boot from SD card. It is kind of secondary option for eMMC to boot or something else.... I remember I used to repair Samsung qcom and exynos phones this way a few years back.
How to create a 256 MB debrick/unbrick/super magic file from a working Motorola phones:
1. rooted phone by any means or unlocked bootloader + twrp.
2. with terminal if rooted type su first then : dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1024 count=2621244
2a. with cmd if twrp: adb shell dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1024 count=2621244
This will make a 256mb debrick/unbrick/super magic file on your sdcard....
copy debrick.img from SD card to PC or pull using adb pull /sdcard/debrick.img - writing file to SD card I believe is explained in the first post.
How to create a debrick file from E4 Verizon phone that cannot bootloader unlock or root ???
Well, you could use Verizon Software Assistant Motorola for this and connect a working phone on fastboot mode, it will download most recent repair file that includes mbm and mbm-ci - that contains blank flash for many new Motorola phones.
Another way is by using MetroPCS /T-Mobile debrick file on Verizon phone (BB.32 bootloader is latest). Because both are MSM8917 CPU and both have BB.32 bootloader. Last time I repaired a Verizon phone with SD card method and using a debrick file from MetroPCS 64-6 version. If you need file, let me know. I can upload it tomorrow....
Cheers guys!
---------- Post added at 10:34 PM ---------- Previous post was at 10:23 PM ----------
There is no need for SD card to detach, because fastboot mode will not flash anything on SD card.... It just boots from SD card and nothing else
Click to expand...
Click to collapse
I tried this procedure with the xt1768 and was unable to get it to boot to fastboot. That command generates a ~2gb file, I write to to the sdcard with the win32diskimager and place it in the disabled unit, put battery in and hold volume down and insert usb, and nothing happens. QHSUSB__BULK device shows in the device manager but that happens regardless of the volume down or the presence of the sdcard. Thining this might be because the xt1766 has a mediatek while the xt1768 has a qualcomm cpu?
Mirani said:
i have brick Moto E4 XT 1765
CPU MSM 8917
metropcs
please help me, flash.bat not work i have trying lots of methood but not success
can i try above methood on my brick device
or plz give me suitable debrick file for my device
Click to expand...
Click to collapse
Will upload on weekend..
Mirani said:
i have brick Moto E4 XT 1765
CPU MSM 8917
metropcs
please help me, flash.bat not work i have trying lots of methood but not success
can i try above methood on my brick device
or plz give me suitable debrick file for my device
Click to expand...
Click to collapse
xeropressence said:
I tried this procedure with the xt1768 and was unable to get it to boot to fastboot. That command generates a ~2gb file, I write to to the sdcard with the win32diskimager and place it in the disabled unit, put battery in and hold volume down and insert usb, and nothing happens. QHSUSB__BULK device shows in the device manager but that happens regardless of the volume down or the presence of the sdcard. Thining this might be because the xt1766 has a mediatek while the xt1768 has a qualcomm cpu?
Click to expand...
Click to collapse
Both are Qualcomm, processor's are different.. xt1765 will hopefully work will upload this weekend
Salik Iqbal said:
Both are Qualcomm, processor's are different.. xt1765 will hopefully work will upload this weekend
Click to expand...
Click to collapse
i have unlock boot loader working fine on stock firmware version 7.1.1
NCQ 26.69.46_cid22_subsidy-MPCS_regulatory. but not rooted working charm, after few day i have connected on wifi server suddenly i have received pop up OTA new security patch ready for install i have just installed this patch and my mobile going installing, then erasing after that now not showing anything i have hard brick my own phone with my little negligence.
when i connected to pc just tray icon show HS_USB_Qdloader 9008 and only detected by flash.bat and Qualcomm Snapdragon Flash Tool
plz help me out this headache
im waiting for your responce
Thanks sir
Mirani said:
i have brick Moto E4 XT 1765
CPU MSM 8917
metropcs
please help me, flash.bat not work i have trying lots of methood but not success
can i try above methood on my brick device
or plz give me suitable debrick file for my device
Click to expand...
Click to collapse
Hello, I have followed these directions with unlocked bootloader in TWRP on XT1765
Code:
How to create a 256 MB debrick/unbrick/super magic file from a working Motorola phones:
1. rooted phone by any means or unlocked bootloader + twrp.
2. with terminal if rooted type su first then : dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1024 count=2621244
2a. with cmd if twrp: adb shell dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1024 count=2621244
I am uploading it now as I type this. I will update post once its done. The file ended up being 446MB instead of 256MB however I hope that doesn't matter. I havent used the file just yet or had the chance. Pleases let me know if it works for you. I think my battery on dead phone is dead also, lol.
Device the .img was made from is as follows:
ROM: Slim-7.1.2.build.2.0-UNOFFICIAL-20180310-1717
Model: Moto E4 XT1765
Carrier: MetroPCS
Color: Gold
Posted it here:
https://forum.xda-developers.com/moto-e4/how-to/untested-moto-e4-xt1765-metropcs-t3843657
hi, do you have an image for xt1776 moto E4 Plus, sprint/boost
jamiedoe said:
hi, do you have an image for xt1776 moto E4 Plus, sprint/boost
Click to expand...
Click to collapse
This should be asked on the XDA Moto E4 Plus forum, but you can find a copy here. The one dated September 19, 2018 is right in the middle, and should be the newest.
hitokage004 said:
This should be asked on the XDA Moto E4 Plus forum, but you can find a copy here. The one dated September 19, 2018 is right in the middle, and should be the newest.
Click to expand...
Click to collapse
Hi.
Sorry, i meant the image for unbricking not the firmware
jamiedoe said:
Sorry, i meant the image for unbricking not the firmware
Click to expand...
Click to collapse
Partially my fault as well, I was scanning through threads and didn't realize that you probably meant an unbrick image - I've been seeing lots of firmware requests recently. If you ask in the E4 Plus forum though and reference this thread, you might be able to find someone willing to make you the bootloader image needed.
First......This is a work in progress meaning it is not a fully working solution yet.
So that's the bad news.
The good news is that this provides an opportunity to learn something.
Everything we learn should also apply to any of the newer Samsung Qualcomm Based Devices.
Lets investigate some of the past methods used to unbrick dead samsung devices.
Also please note that these methods are for Hard Bricked Devices. ( NO Download Mode / NO Recovery Mode / Unresponsive )
Any device that can boot into download mode can easily be fixed with ODIN.
#1) Methods of possible DeBrick That I know of.
A) Use Recovery SD Card.
B) Use Firehose to flash in QDL 9008 / 9006 mode.
C) Boxes - JavaCard - Hardware type solutions.
For now lets look at option A). Hopefully this option is still viable. Although I have tested this a little and so far I am still unable to get booted into download mode.
So in researching Debrick image or Debrick rom of samsung devices you will find some things.
This is what we are interested
https://www.scribd.com/document/272...de-Qualcomm-APQ8084-Includes-SM-N910F-Rev-3-0
Looking at that we should be able to use ODIN and select T-Flash to create the Boot-Recovery-Image.
Unfortunately I tried this and it did not work. The T-Flash just hangs and eventually errors out.
This could be due to the version of Odin i used.
I tried a couple of different Odin versions without any luck.
And also YES you have to do this on a working device.
Since the ODIN method didn't work I know from past experience how to make a bootable EMMC Clone onto a SD-Card.
You can do this in windows or in linux or in the device Terminal ( TWRP Terminal)
This command will make a byte for byte copy of the device EMMC onto a SD Card.
Here are the steps.
1) Insert Blank 16GB SD card into the working device. ( The sd card must be high quality Like V30 or U1 Class. " 95 to 100 mbs speed " )
2) The bootloader version of the device you are using to make the sd card has to match the version on the bricked device. (Flash good device with odin to match factory software before making sd card) <-- <-- <-- " Probable reason my Card is not working yet to boot my bricked device "
3) After that its pretty simple.
We know that the main EMMC of the Tablet is MMCBLK0
We know that the SD Card is assigned MMCBLK1
So executing the following command will clone the emmc to the sd card.
Code:
dd if=/dev/block/mmcblk0 of=/dev/block/mmcblk1
It will take between 30 min and a hour to copy.
I have created this image and tested it but no luck yet.
The image is of the factory T560NUUEU1CQK2_T560NUXAR1CQK2 firmware.
I bricked my tab by flashing the aboot.bin alone from COMBINATION_XAR_FA51_T560NUUEU1APH1.
I flashed just the aboot without flashing the rest of the booloaders from COMBINATION_XAR_FA51_T560NUUEU1APH1.
So what i need to do next is make a card that has the complete set of bootloaders from COMBINATION_XAR_FA51_T560NUUEU1APH1.
Once we have a clone of the emmc we can flash seperate partitions on the sd card just like if we did on the device.
I know for sure the bootloader versions have to match. This is a likly cause for my card not to bring my Tab back to life.
Another possibility is that the card has the whole emmc backup. Mirror of the device. Realistically it should be just the bootloaders.
I have looked at some of the boot-recovery images for other devices. Some have only the bootloaders. Some have all the partitions but only the bootloaders flashed. And even the fact that it is a direct copy of the emmc and not its own unique GPT could all factor into it not working at the moment.
All these different combinations of things could be the difference between the card working or not working.
I will upload the image for you if you want to test it.
You can also dump each partition to an individual backup image in case you need any of them.
Do it in linux using "dd" or do it on the device using "dd" and mmcblk1 rather than mmcblk0
If you don't know what i'm talking about don't worry. I will go over things like that at some point in time.
Here is a upload of the SD Card - EMMC Clone for 16GB T560NU
http://www.mediafire.com/file/5m0b7r11nc3nn5q/16GB-T560NU-.img.zip/file
Unzip the file.
Use win32diskimager to flash the image to the sdcard.
After win32diskimage is complete a bunch of file windows will pop up. On windows 10.
It will say disk must be formatted. Do NOT format the disks.
Close them all and remove the sd card from the computer.
Put sd card in bricked device.
Plug in usb.
Try to boot.
Try to boot into download mode.
Let it sit 5 or 10 min.
See if anything happens.
If you have any luck please let us know.
Unfortunately I think were gonna end up having to do it this way.
https://forum.xda-developers.com/galaxy-s8/help/s8-g950u-hardbrick-t3668572
But we need the .elf programmer for APQ8016.
If anyone can get me the firehose programmer I can build the service rom.
BigCountry907 said:
Unfortunately I think were gonna end up having to do it this way.
https://forum.xda-developers.com/galaxy-s8/help/s8-g950u-hardbrick-t3668572
But we need the .elf programmer for APQ8016.
If anyone can get me the firehose programmer I can build the service rom.
Click to expand...
Click to collapse
Did you ever figure yours out? I did the same thing you did (downgraded aboot and hard bricked). I've been able to create a debrick img using another identical device, but the bricked one still won't respond when the sd card is inserted
iBowToAndroid said:
Did you ever figure yours out? I did the same thing you did (downgraded aboot and hard bricked). I've been able to create a debrick img using another identical device, but the bricked one still won't respond when the sd card is inserted
Click to expand...
Click to collapse
I ended up changing the mainboard.
It was like $60 on amazon. Not sure how many are available.
I tried using a good device to T-Flash a sd card in odin.
The t-Flash never worked.
I also did a direct dump to a sdcard, Literally mirroring the emmc onto the sdcard.
dd if=/dev/block/mmcblk0 of=/dev/block/mmcblk1
The device did not respond to the sd card.
I have recently un-bricked a N950U Note 8 but in order to do that i needed things.
In order to get into edl mode there is a test point somewhere on the board.
You short the test point to ground and then plug in the usb and it will boot edl.
I do not know where the test point of the t560nu is at.
Second you will need the Firehose programmer for the t560nu specifically.
It needs to match the bootloader rev as well.
I don't think its revision that causes the brick but it could be.
I flashed the engineering aboot to a normal running device and that's how i bricked.
I believe you have to flash the whole bootloader set if your going to flash bootloaders.
Someone with a octoplus box got me the test point location.
Octoplus software has photos of the test points.
The edl package was from a different source.
It's possible someone with octoplus or medusa or similar boxes may be able to get the test point and the firehose.
I asked my guy for it but i don't think he looked yet.
I still have my bricked board so if you find the firehose and the testpoint let me know.
I will ask my guy again to check.
BigCountry907 said:
I believe you have to flash the whole bootloader set if your going to flash bootloaders
Click to expand...
Click to collapse
Correct, with qualcomm devices the revision of aboot needs to match the sbl.
Sbl checks the version of aboot if it doesn't match it refuses to boot.
Been there done that.
However I have yet to attempt a hardware repair. Debrick images unsuccessful, no response.
My next step(when I can be bothered to get around to it) is to use an sd card adapter wired directly to the emmc as both use the same protocols and an sd card controller should be able to communicate with an emmc.
As long I can get the partitions to show up on the EMMC, should hopefully be a case of flashing the correct aboot to the right partition.
BigCountry907 said:
I ended up changing the mainboard.
It was like $60 on amazon. Not sure how many are available.
I tried using a good device to T-Flash a sd card in odin.
The t-Flash never worked.
I also did a direct dump to a sdcard, Literally mirroring the emmc onto the sdcard.
dd if=/dev/block/mmcblk0 of=/dev/block/mmcblk1
The device did not respond to the sd card.
I have recently un-bricked a N950U Note 8 but in order to do that i needed things.
In order to get into edl mode there is a test point somewhere on the board.
You short the test point to ground and then plug in the usb and it will boot edl.
I do not know where the test point of the t560nu is at.
Second you will need the Firehose programmer for the t560nu specifically.
It needs to match the bootloader rev as well.
I don't think its revision that causes the brick but it could be.
I flashed the engineering aboot to a normal running device and that's how i bricked.
I believe you have to flash the whole bootloader set if your going to flash bootloaders.
Someone with a octoplus box got me the test point location.
Octoplus software has photos of the test points.
The edl package was from a different source.
It's possible someone with octoplus or medusa or similar boxes may be able to get the test point and the firehose.
I asked my guy for it but i don't think he looked yet.
I still have my bricked board so if you find the firehose and the testpoint let me know.
I will ask my guy again to check.
Click to expand...
Click to collapse
It's only ever been on bootloader rev 1, so i figured i was fine going back as far as possible with aboot, like how it is for sboot on Exynos. Obviously not correct though.
Yeah, I dumped to an SD, but only did the first 200MB, instead of an entire image. I have no idea if that even works on this model - I was just hoping it would, like it used to for the S3 and other devices.. I have no idea where i'd get the firehose so this might be SOL
respected brother plz give me your whatsap no# my tablte t560nu dead after flash
respected brother plz give me your whatsap no# my tablte t560nu dead after flash
My whatsap 03103615995
---------- Post added at 12:47 PM ---------- Previous post was at 12:39 PM ----------
respected brother plz give me your whatsap no# my tablte t560nu dead after flash
My whatsap 03103615995
SM-T560NU Does not Turn On After Software Flash
Hello All,
I have been told this is the right place to find a solution to this problem. I have a Galaxy Tab E (SM-T560NU) that had an attempt made to get around FRP using Odin and Sboot firmware. Unfortunately the thing has not been able to turn on since the flash was done & I am told it has been soft bricked. Is there a proven method of brining this thing back to life?
Datsys said:
Hello All,
I have been told this is the right place to find a solution to this problem. I have a Galaxy Tab E (SM-T560NU) that had an attempt made to get around FRP using Odin and Sboot firmware. Unfortunately the thing has not been able to turn on since the flash was done & I am told it has been soft bricked. Is there a proven method of brining this thing back to life?
Click to expand...
Click to collapse
If it won't even turn on, then it's hard bricked - not soft bricked. And no, no proven method to fix it
Datsys said:
Hello All,
I have been told this is the right place to find a solution to this problem. I have a Galaxy Tab E (SM-T560NU) that had an attempt made to get around FRP using Odin and Sboot firmware. Unfortunately the thing has not been able to turn on since the flash was done & I am told it has been soft bricked. Is there a proven method of brining this thing back to life?
Click to expand...
Click to collapse
How have you managed to flash firmware for Exynos to a Snapdragon device? Sboot is the Exynos boot loader.
ashyx said:
How have you managed to flash firmware for Exynos to a Snapdragon device? Sboot is the Exynos boot loader.
Click to expand...
Click to collapse
I'm sure he meant aboot
iBowToAndroid said:
I'm sure he meant aboot
Click to expand...
Click to collapse
Well if he flashed aboot without sbl then there's not much hope.
SBL checks the integrity of aboot and if it doesnt match it refuses to proceed.
Can't even use qualcomm low level tools.
The only way that may be possible which I have never tried is to wire the emmc direct to an sdcard adapter and hope the controller is able to boot it and see the partitions.
Then flash the correct aboot or sbl.