Related
hi all,
So, I've been a bit of a idiot.
In a nut shell I was trying to manually remove the flash count and followed the wrong tut.
I did dd if=/dev/zero of=/dev/block/mmcblk0 bs=1 count=1 seek=3145732 and now when i try to boot the note I dont get the Samsung logo splash screen, I get a screen full of static.
I can access the recovery partition, I can also access in download mode with odin.
If I try to flash the stock rom, it completes ok but doesn't auto restart and stays on the odin mode screen.
I do get E:\ unable to mount /efs when i wipe the cache's.
I have a 2nd note 10.1 (both n8010) so I'm hoping I can fix/copy/image from the 2nd working device.
Any ideas on how to fix? or is it now an expensive paper weight?
I have flashed the stock firmware and rom from samsung-mobile but no joy.
thanks,
http://forum.xda-developers.com/showthread.php?t=2087567
blastman said:
hi all,
So, I've been a bit of a idiot.
In a nut shell I was trying to manually remove the flash count and followed the wrong tut.
I did dd if=/dev/zero of=/dev/block/mmcblk0 bs=1 count=1 seek=3145732 and now when i try to boot the note I dont get the Samsung logo splash screen, I get a screen full of static.
I can access the recovery partition, I can also access in download mode with odin.
If I try to flash the stock rom, it completes ok but doesn't auto restart and stays on the odin mode screen.
I do get E:\ unable to mount /efs when i wipe the cache's.
I have a 2nd note 10.1 (both n8010) so I'm hoping I can fix/copy/image from the 2nd working device.
Any ideas on how to fix? or is it now an expensive paper weight?
I have flashed the stock firmware and rom from samsung-mobile but no joy.
thanks,
Click to expand...
Click to collapse
You are in a tough situation my friend
I think as long as the recovery and odin work there is a chance...
can you give me the link to that tutorial .. I think i may help
Or do you remember where that sector was??
Anyways you may try to backup both devices EFS (backup that of the non working device in case you need it for anything) .... (But i think the EFSPro wont work) (you may do that using EFSpro or i think it may be done through the shell by "dd if=dev/block/mmcblk0p? of=/sdcard/efs.img" where "?" is the number of EFS partition you can know that from shell command mount "i think its mmcblk0p3") .... then restore the EFS of the working device to the non-working one (EFS pro or using "dd if=/sdcard/efs.img of=/dev/block/mmcblk0p?" "i think its mmcblk0p3")
I hope this would succeed although i red that it contains MAC address data which may prevent both devices connecting to same network
(N8010 has no connection to cellular networks so i think no problem)
Scorpion_Ibm said:
I think as long as the recovery and odin work there is a chance...
can you give me the link to that tutorial .. I think i may help
Or do you remember where that sector was??
Anyways you may try to backup both devices EFS (backup that of the non working device in case you need it for anything) .... (But i think the EFSPro wont work) (you may do that using EFSpro or i think it may be done through the shell by "dd if=dev/block/mmcblk0p? of=/sdcard/efs.img" where "?" is the number of EFS partition you can know that from shell command mount "i think its mmcblk0p3") .... then restore the EFS of the working device to the non-working one (EFS pro or using "dd if=/sdcard/efs.img of=/dev/block/mmcblk0p?" "i think its mmcblk0p3")
I hope this would succeed although i red that it contains MAC address data which may prevent both devices connecting to same network
(N8010 has no connection to cellular networks so i think no problem)
Click to expand...
Click to collapse
this?
http://forum.xda-developers.com/showthread.php?p=37465299
jaydubbbbs said:
this?
http://forum.xda-developers.com/showthread.php?p=37465299
Click to expand...
Click to collapse
But before all these go to shell and try "dd if=/dev/block/mmcblk0p3 of=/sdcard/efs.img" and "tar -cvf /sdcard/EFS.tar /dev/block/mmcblk0p3"
if these commands succeed you would have a backup of old efs before changing any thing (keep it in a safe place)
Look you may try just backing up and then restoring the same EFS of the device
Try this first: use the tar command to copy the files of EFS "tar -cvf /sdcard/EFS.tar /dev/block/mmcblk0p3"
then do " mke2fs /dev/block/mmcblk0p3" the last thing is to restore the tar with "tar -xvzf /sdcard/EFS.tar -C /dev/block/mmcblk0p3"
I prefer you try what i said first as it's shorter and makes nearly the same thing except that it takes all files not just the nv_data.bin
You can then try that tutorial in the link i think it works and you can get the that file nv_data.bin from your other device or from the non-functioning one if you can extract it from the tar backup in the first step
Cheers for the replies guys.
I'll find the tut I followed and post a link.
I'll also look into the link and suggestions you've mentioned.
My main issue seems to be that I can't get a adb connection to the device as it won't boot.
Even with cwm 6.1 installed, I still can't connect. Bear in mind, I've flashed back to stock but not been able to boot it to put it into usb debugging mode. does this mean I'll never be able to get a shell open?
I have managed to create a efs.img from the working device but have no way to push to the broken one.
Any suggestions?
Thanks
blastman said:
Cheers for the replies guys.
I'll find the tut I followed and post a link.
I'll also look into the link and suggestions you've mentioned.
My main issue seems to be that I can't get a adb connection to the device as it won't boot.
Even with cwm 6.1 installed, I still can't connect. Bear in mind, I've flashed back to stock but not been able to boot it to put it into usb debugging mode. does this mean I'll never be able to get a shell open?
I have managed to create a efs.img from the working device but have no way to push to the broken one.
Any suggestions?
Thanks
Click to expand...
Click to collapse
You say that adb wont work even from CWM??
Try this and see if it works http://www.dominantwire.com/2012/11/how-to-solve-adb-device-not-found-error.html
yep, even when booted into cwm recovery i still can;t connect to adb
just downloading a custom rom now to see if it's the stock rom causing the issue.
although I am able to access adb in cmw recovery from the other working device, even with USB debugging turned off.
sadly that link is no good.
I'm able to connect to the working device on the same cwm recovery version, using the same cable, so setup and PC are ok.
I dont know if the roms are the same (maybe not) but I'll flash the broken one with a custom 'pre rooted' rom in case it helps.
blastman said:
yep, even when booted into cwm recovery i still can;t connect to adb
just downloading a custom rom now to see if it's the stock rom causing the issue.
although I am able to access adb in cmw recovery from the other working device, even with USB debugging turned off.
Click to expand...
Click to collapse
Ok try another rom as i think roms have diferences in adb !!
if not working also and If you know you can safely flash a new recovery .. try TWRP it has an inbuilt shell .. the keyboard is not that good but you can try it better than nothing
ok so....
I've flashed an different custom rom via cwm install from ext_sdcard. After a reboot I now have the samsung logo back!!!!
It's hung on the samsung logo for a wile now, 5 minutes or so, but I'll let it sit there for a good 30 minutes to be sure.
I'll see what happens from this rom flash, but failing this I'll stick TRWP on and have a go with the inbuilt shell. even if i can mount ext sd I should be able to restore the block i over wrote.
getting closer!!!
thanks so far,
blastman said:
ok so....
I've flashed an different custom rom via cwm install from ext_sdcard. After a reboot I now have the samsung logo back!!!!
It's hung on the samsung logo for a wile now, 5 minutes or so, but I'll let it sit there for a good 30 minutes to be sure.
I'll see what happens from this rom flash, but failing this I'll stick TRWP on and have a go with the inbuilt shell. even if i can mount ext sd I should be able to restore the block i over wrote.
getting closer!!!
thanks so far,
Click to expand...
Click to collapse
Good to hear .. i hope it finishes the problem .. but in case it fails before flashing TWRP try from adb .. adb kill-server then adb start-server and adb usb and see if it works
will do, thanks.
I've just noticed that the command i ran I outputted to mmcblk0 and your commands refer to mmcblk0p3.
Am i right in guessing the the 0 part lists the disk and the px part is referring to the partition on that disk (so to speak)?
so my original command which broke it basically wiped the internal storage? this would explain a lot about failed connections as well.
blastman said:
will do, thanks.
I've just noticed that the command i ran I outputted to mmcblk0 and your commands refer to mmcblk0p3.
Am i right in guessing the the 0 part lists the disk and the px part is referring to the partition on that disk (so to speak)?
so my original command which broke it basically wiped the internal storage? this would explain a lot about failed connections as well.
Click to expand...
Click to collapse
Did the device work or did you manage to get adb connection??
Anyways ... from what i read during searching is that if=/dev/zero and bs=1 count=1 seek=3145732 parts of your command writes zeros only to one byte, one time after seeking 3145732 blocks of the storage which seems to be in EFS partition which says cant mount ... So the commands i wrote are to take a backup of whatever files in there then format the drive and restore the files back to it ... after formating using mke2fs reboot the device before restore and see if it shows the cant mount message again
arh ok, that makes sense.
I've managed to tar the efs files form the working device.
I then opened the shell in twrp and did a mke2fs /dev/block/mmcblk0p3 which completed ok.
But when i try to tar -xvzf EFS.tar -C /dev/block/mmcblk0p3 (from the external sd dir, it tells me that the mmcblk0p3 isn;t a directory.
any ideas?
thanks again
how about doing a dd if=efs.img of=/dev/block/mmcblk0p3??
I got a efs.img from efs pro on the working device..
blastman said:
arh ok, that makes sense.
I've managed to tar the efs files form the working device.
I then opened the shell in twrp and did a mke2fs /dev/block/mmcblk0p3 which completed ok.
But when i try to tar -xvzf EFS.tar -C /dev/block/mmcblk0p3 (from the external sd dir, it tells me that the mmcblk0p3 isn;t a directory.
any ideas?
thanks again
Click to expand...
Click to collapse
try remove -C from the command it's for directory my mistake
and you can also try dd with (if=/"path of extsd"/EFS.img) but try the tar first .... after that see if it tells you cant't mount EFS by opening mount and select EFS and see if it becomes with an 'x' then going to the upper right corner of the screen and pressing the icon beside back and home and see if it shows cant mount EFS
sorry, before you replied i went and did a dd if=efs.img of=/dev/block/mmcblk0p3
I then flashed the stock ROM and BOOM!! im in!!
YEAH BABY!!!
only issue now is that the boot loader isn't quite right.
1 - it doesn't show the 'Samsung Galaxy Note 10.1" splash screen
2 - instead of above I get a screen showing the last thing i was doing, ie, download mode, but with static across it.
any ideas on how to correct this?
blastman said:
sorry, before you replied i went and did a dd if=efs.img of=/dev/block/mmcblk0p3
I then flashed the stock ROM and BOOM!! im in!!
YEAH BABY!!!
only issue now is that the boot loader isn't quite right.
1 - it doesn't show the 'Samsung Galaxy Note 10.1" splash screen
2 - instead of above I get a screen showing the last thing i was doing, ie, download mode, but with static across it.
any ideas on how to correct this?
Click to expand...
Click to collapse
Can you answer some questions??
what do you mean by you are in?? .. can you get to android or not yet?? ... what do you mean with getting download mode with static ??
would you try going to recovery and clear cache and dalvik cache to try??
sorry, by I'm in I mean that I can now boot to Android.
when i say download mode with static, image the download screen but fuzzy and punctuated with white nose.
I've done a cache format and a reset to factory but I still get the same issue.
Also, I'm still unable to get an adb connection to the device.
I have noticed that the serial number has now changed to the same as the working device but thats expected as we copied the efs contents from one to the other.
thanks for all your help. you saved my bacon
Hello everybody,
I'm new user on this forum please forgive me for my english as I am Belgian.
I try to make a backup of my Huawei G6-L11 with Android SDK.
I am on Xbuntu 14.04 (I am not a specialist but I use it for some months). I have installed the packages android-tools-adb and android-tools-fastboot and also android sdk.
My phone is connected to the PC via usb and the debug mode is active.
I followed the next steps in a terminal
[email protected]:~$ adb devices
List of devices attached
68a0f6753968 device
[email protected]:~$ adb backup -apk -shared -all -f backup.ab
Now unlock your device and confirm the backup operation.
[email protected]:~$
Click to expand...
Click to collapse
The problem is that I unlock the phone but the backup does not begin. Why? What can I do to begin it?
I really need to do this operation as I can not make any upgrade, any changes on my phone as the memory is full
Thanks a lot for your help
Use ADB, need root
Sent from my HUAWEI G6-L11 using XDA-Developers mobile app
persona78 said:
Use ADB, need root
Sent from my HUAWEI G6-L11 using XDA-Developers mobile app
Click to expand...
Click to collapse
Hello,
Thanks for your reply
I have tried with root and it does not function
I followed the steps I saw here https://memo-linux.com/android-utiliser-adb-pour-faire-une-sauvegarde-complete-de-son-smartphone-ou-tablette-sur-pc-sous-gnulinux/
And I can do the first steps, the problem is that the phone is not locked as it should be and the backup does not begin
Other solution?
Thanks a lot
Hello,
I become completely crazy with my problem :silly: I can't do it
I tried a lot of manipulations in order to do the backup and I found something interesting. In a file I had to create in /etc/udev.rules.d/ with the name 51-android.rules, I saw that the product ID seems change every time it is connected/disconnected of the PC. It was 1054, 1037 and also 1051. I suppose it make some trouble... Is it possible to blok it, ?
HTML:
ATTR{idVendor}=="12d1", ATTR{idProduct}=="1051", MODE=”0666"
Thanks a lot.
Hi!
With the phone ON, with root, plug USB, choose MTP, tuurn ON debug mode, it will pop up a window in phone requesting permissions to connect YOU MUST GIVE IT, need 2GB free in your sd card, use ADB and type this:
adb shell "su -c 'dd if=/dev/block/mmcblk0p4 of=/storage/sdcard1/rpm.img bs=4096; dd if=/dev/block/mmcblk0p5 of=/storage/sdcard1/tz.img bs=4096; dd if=/dev/block/mmcblk0p1 of=/storage/sdcard1/sbl1.img bs=4096; dd if=/dev/block/mmcblk0p11 of=/storage/sdcard1/modem.img bs=4096; dd if=/dev/block/mmcblk0p9 of=/storage/sdcard1/modemst1.img bs=4096; dd if=/dev/block/mmcblk0p10 of=/storage/sdcard1/modemst2.img bs=4096; dd if=/dev/block/mmcblk0p2 of=/storage/sdcard1/sdi.img bs=4096; dd if=/dev/block/mmcblk0p6 of=/storage/sdcard1/aboot.img bs=4096; dd if=/dev/block/mmcblk0p19 of=/storage/sdcard1/recovery.img bs=4096; dd if=/dev/block/mmcblk0p23 of=/storage/sdcard1/system.img bs=4096; dd if=/dev/block/mmcblk0p18 of=/storage/sdcard1/boot.img bs=4096; dd if=/dev/block/mmcblk0p24 of=/storage/sdcard1/userdata.img bs=4096; dd if=/dev/block/mmcblk0p21 of=/storage/sdcard1/cache.img bs=4096; dd if=/dev/block/mmcblk0p20 of=/storage/sdcard1/cust.img bs=4096; dd if=/dev/block/mmcblk0p12 of=/storage/sdcard1/fsg.img bs=4096'"
Now you have your ROM images in sd card. You will need a flash zip to flash it if you need it.
You can use this one, only need to paste the images inside.
RomBackup.zip
https://mega.nz/#!n5plABBT
Key:
!L5EVKRl6AnTyr24IrhwPacxU_DbO7t2moVVzw9gOOT4
Use TWRP to flash it: http://forum.xda-developers.com/ascend-g6/general/twrp-3-0-0-0-g6-lte-devices-t3378495
Hi Persona78,
Thanks a lot for your quick answer
As I understand what you explain in your answer, you proposed me to flash the ROM of the phone but that is not my aim. I only want to make a backup for after try to increase the internal memory. I do not want to root the phone so I found on Internet the ADB program.
I plug the phone which is ON, I plug it with the USB cable, choose MTP transfer protocol, turn it on debug mode and agree with the pop up on the phone. Everything is good until the time when a message should appear to UNLOCK the phone in order to backup. This message does not appear as the phone is already unlocked and as it get blocked, no message appears. Whatever, the backup does not begin!
Thanks a lot.
filipinne13 said:
Hi Persona78,
Thanks a lot for your quick answer
As I understand what you explain in your answer, you proposed me to flash the ROM of the phone but that is not my aim. I only want to make a backup for after try to increase the internal memory. I do not want to root the phone so I found on Internet the ADB program.
I plug the phone which is ON, I plug it with the USB cable, choose MTP transfer protocol, turn it on debug mode and agree with the pop up on the phone. Everything is good until the time when a message should appear to UNLOCK the phone in order to backup. This message does not appear as the phone is already unlocked and as it get blocked, no message appears. Whatever, the backup does not begin!
Thanks a lot.
Click to expand...
Click to collapse
Hmmm, all apps I know to do backup use root.
You can use CWM or TWRP to backup, but they don't backup cust, and I don't know if recover to images default size.
The only way I know is fashing default ROM.
---------- Post added at 09:54 AM ---------- Previous post was at 09:50 AM ----------
persona78 said:
Hmmm, all apps I know to do backup use root.
You can use CWM or TWRP to backup, but they don't backup cust, and I don't know if riecover to images default size.
The only way I know is fashing default ROM.
Click to expand...
Click to collapse
I have a L11 rom, modify by me, resided and if you create in sd card a primary ext4 partition it wil send the apps to sd card automatically.
Hello Persona78,
Hmmm, all apps I know to do backup use root.
You can use CWM or TWRP to backup, but they don't backup cust, and I don't know if recover to images default size.
The only way I know is fashing default ROM.
Click to expand...
Click to collapse
Finally, I made a manual backup by drag and drop and also with Mybackup which do not use root.
I have a L11 rom, modify by me, resided and if you create in sd card a primary ext4 partition it wil send the apps to sd card automatically.
Click to expand...
Click to collapse
I made a reset of the phone with the manufacturer's parameters but I would like to use one other rom as they do not have any update for this model but it seems to be complicated to do it. I do not know how to backup the manufacturer's rom as I met a problem after. I think I would not be possible for me to root, unlock, extend the sd card with Gparted (as I work under UBUNTU 14.04 LTS), and make the update with the new rom, as I am not so talented with computer science.
Thanks a lot.
I tried and finally I have used Gparted in order to split the sd card. I have now 4 partitions
- swap partition (29 mb),
- fat32 partition (6.35 Gb)
- ext4 partition (23.34Gb)
try one of my versions
You can try one of my versions.
Read first to know what you get if you flash it!
https://www.facebook.com/Huawei.Ascend.G6.L11.Kit.kat.B370/?ref=bookmarks
Hello guys, so now my mi4c is unlocked bootloader i want to backup first imei/nvram/efs partition before start to flashing twrp, since on my device before my imei gone after flashing twrp already restore from twrp backup/qpst tool/fastboot rom flash but still nothing work.
From now my local store refund the money since they cant fix it too and then i bought new one.
So, how i can backup those files directly from phone with root permission like terminal emulator or something?
Anyone can give me command for it..
Thanks. :fingers-crossed:
I'm searching over google and miui forum and find this thread on russian forum but its for minote pro does it same?
Correct me if i'm wrong please..
Take look link below
http://4pda.ru/forum/index.php?s=&showtopic=668750&view=findpost&p=45923244
http://4pda.ru/forum/index.php?s=&showtopic=657190&view=findpost&p=39377526
Might be usefull for everyone too before facing problem with imei.
bump
@ketut.kumajaya I need your advice please :crying:
Which is partition block number used on mi4c?
Degrinder said:
bump
@ketut.kumajaya I need your advice please :crying:
Which is partition block number used on mi4c?
Click to expand...
Click to collapse
https://github.com/kumajaya/android...-13.0-twrp/recovery/root/etc/twrp.fstab#L7-L8
You can use busybox's dd command:
Code:
busybox dd if=/dev/block/bootdevice/by-name/modemst1 of=/sdcard/modemst1.img bs=4096
busybox dd if=/dev/block/bootdevice/by-name/modemst2 of=/sdcard/modemst2.img bs=4096
Be careful with above commands.
ketut.kumajaya said:
https://github.com/kumajaya/android...-13.0-twrp/recovery/root/etc/twrp.fstab#L7-L8
You can use busybox's dd command:
Code:
busybox dd if=/dev/block/bootdevice/by-name/modemst1 of=/sdcard/modemst1.img bs=4096
busybox dd if=/dev/block/bootdevice/by-name/modemst2 of=/sdcard/modemst2.img bs=4096
Be careful with above commands.
Click to expand...
Click to collapse
I'm sorry but for me its new things for linux command so i dont know much about it :laugh:
And i'm affraid if my device got bricked too
Need to instal busybox first or i can do it instantly with terminal emulator?
Degrinder said:
I'm sorry but for me its new things for linux command so i dont know much about it :laugh:
And i'm affraid if my device got bricked too
Need to instal busybox first or i can do it instantly with terminal emulator?
Click to expand...
Click to collapse
Maybe yes, I'm not sure if 4c have a proper busybox binary preinstalled.
ketut.kumajaya said:
Maybe yes, I'm not sure if 4c have a proper busybox binary preinstalled.
Click to expand...
Click to collapse
So, which do you think is better using backup from this command or using 3rd apps like Partitions Backup & Restore(select raw .img files) ?
i thought that was crap that only happened with cheap mediatek based phones,
I've never made any backup of EFS on any phone...
#xiaomiMi4c
I hard bricked my phone and now i'm trying to make it work again.
Unfortunately motorola didn't released to us the progamming files for the Qualcomm HS-USB download mode, but searching i've found a diferent unbrick method that worked on other qualcomm phones, including one with the same SoC of merlin.
What i need is that someone with a working and rooted Merlin device run this command to copy the internal partitions and send me the file:
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1024 count=168960
Thanks a lot if anybody can help me
The sources of what i'm trying are here:
http://www.aryk.tech/2017/02/how-to-unbrick-debrick-qualcomm-android.html
https://forum.xda-developers.com/yureka/help/guide-unbrick-hard-bricked-yureka-t3303112
caiosilva96 said:
I hard bricked my phone and now i'm trying to make it work again.
Unfortunately motorola didn't released to us the progamming files for the Qualcomm HS-USB download mode, but searching i've found a diferent unbrick method that worked on other qualcomm phones, including one with the same SoC of merlin.
What i need is that someone with a working and rooted Merlin device run this command to copy the internal partitions and send me the file:
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1024 count=168960
Thanks a lot if anybody can help me
The sources of what i'm trying are here:
http://www.aryk.tech/2017/02/how-to-unbrick-debrick-qualcomm-android.html
https://forum.xda-developers.com/yureka/help/guide-unbrick-hard-bricked-yureka-t3303112
Click to expand...
Click to collapse
Faced the same problem about two weeks ago. Is there any hope?
https://drive.google.com/file/d/0B9le0tZGM2W7MTRUMkpiWkwzZEk/view?usp=drivesdk
Hope this helps you
himavanth.reddy925 said:
https://drive.google.com/file/d/0B9le0tZGM2W7MTRUMkpiWkwzZEk/view?usp=drivesdk
Hope this helps you
Click to expand...
Click to collapse
how to work this loader img i installed in sdcard but mobile not on how to fix
sathyabe said:
Thanks a lot if anybody can help me
The sources of what i'm trying are here:
http://www.aryk.tech/2017/02/how-to-unbrick-debrick-qualcomm-android.html
https://forum.xda-developers.com/yureka/help/guide-unbrick-hard-bricked-yureka-t3303112
Faced the same problem about two weeks ago. Is there any hope?
Click to expand...
Click to collapse
loader. img from Google link is helpful ?
please help me
surinder66 said:
loader. img from Google link is helpful ?
Click to expand...
Click to collapse
I am Also Try But Its not working my phone not working almost 2 week
please help me out how its work..
himavanth.reddy925 said:
https://drive.google.com/file/d/0B9le0tZGM2W7MTRUMkpiWkwzZEk/view?usp=drivesdk
Hope this helps you
Click to expand...
Click to collapse
I am really thankful and I greatly appreciated your effort. It seems the file is corrupted. Can you create the file one more time and upload once again?
sathyabe said:
I am really thankful and I greatly appreciated your effort. It seems the file is corrupted. Can you create the file one more time and upload once again?
Click to expand...
Click to collapse
this file is only 165mb in this zip. not system. img and userdata. 0mb make a full backup
himavanth.reddy925 said:
https://drive.google.com/file/d/0B9le0tZGM2W7MTRUMkpiWkwzZEk/view?usp=drivesdk
Hope this helps you
Click to expand...
Click to collapse
Sorry for the late reply and thanks for helping. Unfortunately it doesn't worked
Maybe the command i copied from the source website was wrong, because 165mb is of course so small.
This should make a full copy of internal memory, but will generate a huge file
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img
caiosilva96 said:
Sorry for the late reply and thanks for helping. Unfortunately it doesn't worked
Maybe the command i copied from the source website was wrong, because 165mb is of course so small.
This should make a full copy of internal memory, but will generate a huge file
Click to expand...
Click to collapse
yes, near about 14.5 gb when compressed then near about 2 gb
surinder66 said:
yes, near about 14.5 gb when compressed then near about 2 gb
Click to expand...
Click to collapse
The first uploaded loader.img file is corrupted. If someone would backup once again and upload it, we can try. Steps to create "Loader.img" file is as follows.
How to Create Bootable SD Card with Moto G Turbo Loader.img File On your PC
1. Get another exact variant of your device and INSERT an SD Card on it. The device chipset must be the same. Thus, if your device (bricked) is MSM8269, the required device CPU has to be MSM8269, too.
2. Root the working (exact variant) device and install Terminal Emulator on it.
3. Download and install Busybox on the device. You may download Busybox from here
4. Once BusyBox is installed, launch/open it and run/install its dependencies/files by clicking on the appropriate key.
5. Now, launch/open Terminal Emulator on the device and follow these procedures:
a. On Terminal EmulatorType:
su
and hit/tap the Enter key. You will be prompted to GRANT Terminal emulator a Root Access, click GRANT.
b. Then, type:
dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1024 count=168960
and hit/tap the Enter key.
6. Wait few minutes or until Terminal Emulator completes the process.
7. Now, check the Root Folder/Directory of the SD Card inserted on the phone. You will notice that a file named Loader.img has been created.
Qualcomm Device Unbrick .img File
GOOD! That's your Qualcomm device Unbrick file. Copy the file onto your PC and continue to the step two (2) below.
strong>NOTE: What we have done in the steps above is that; we have copied all the necessary partition required to boot your Qualcomm android device and compressed it in a .img file. -file format that is widely supported by fastboot commands and can be flashed on SD Card
Now, here is how to flash Loader.img file we created from the first step on your SD Card.
or
If you are able to pay through paypal, try buying from below site
http://www.aryk.store/2017/09/moto-g...ick-files.html
sathyabe said:
The first uploaded loader.img file is corrupted. If someone would backup once again and upload it, we can try. Steps to create "Loader.img" file is as follows.
How to Create Bootable SD Card with Moto G Turbo Loader.img File On your PC
1. Get another exact variant of your device and INSERT an SD Card on it. The device chipset must be the same. Thus, if your device (bricked) is MSM8269, the required device CPU has to be MSM8269, too.
2. Root the working (exact variant) device and install Terminal Emulator on it.
3. Download and install Busybox on the device. You may download Busybox from here
4. Once BusyBox is installed, launch/open it and run/install its dependencies/files by clicking on the appropriate key.
5. Now, launch/open Terminal Emulator on the device and follow these procedures:
a. On Terminal EmulatorType:
su
and hit/tap the Enter key. You will be prompted to GRANT Terminal emulator a Root Access, click GRANT.
b. Then, type:
dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1024 count=168960
and hit/tap the Enter key.
6. Wait few minutes or until Terminal Emulator completes the process.
7. Now, check the Root Folder/Directory of the SD Card inserted on the phone. You will notice that a file named Loader.img has been created.
Qualcomm Device Unbrick .img File
GOOD! That's your Qualcomm device Unbrick file. Copy the file onto your PC and continue to the step two (2) below.
strong>NOTE: What we have done in the steps above is that; we have copied all the necessary partition required to boot your Qualcomm android device and compressed it in a .img file. -file format that is widely supported by fastboot commands and can be flashed on SD Card
Now, here is how to flash Loader.img file we created from the first step on your SD Card.
or
If you are able to pay through paypal, try buying from below site
http://www.aryk.store/2017/09/moto-g...ick-files.html
Click to expand...
Click to collapse
I have yu yureka plus same cpu Moto g turbo can yureka backup work ?
surinder66 said:
I have yu yureka plus same cpu Moto g turbo can yureka backup work ?
Click to expand...
Click to collapse
I think it won't work. But you may try.
Moto g turbo hard bricked after installation of OTA update
My moto g turbo hard bricked after installation of 12 mb OTA update. Please help us with Blankflash fzip or loader.img for Moto g turbo 2015.
srinutheraj said:
My moto g turbo hard bricked after installation of 12 mb OTA update. Please help us with Blankflash fzip or loader.img for Moto g turbo 2015.
Click to expand...
Click to collapse
same for me
[/COLOR]
surinder66 said:
yes, near about 14.5 gb when compressed then near about 2 gb
Click to expand...
Click to collapse
Hey! Sasriyakaar.
Can you provide me a link attaching that file please?
caiosilva96 said:
I hard bricked my phone and now i'm trying to make it work again.
Unfortunately motorola didn't released to us the progamming files for the Qualcomm HS-USB download mode, but searching i've found a diferent unbrick method that worked on other qualcomm phones, including one with the same SoC of merlin.
What i need is that someone with a working and rooted Merlin device run this command to copy the internal partitions and send me the file:
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1024 count=168960
Thanks a lot if anybody can help me
The sources of what i'm trying are here:
http://www.aryk.tech/2017/02/how-to-unbrick-debrick-qualcomm-android.html
https://forum.xda-developers.com/yureka/help/guide-unbrick-hard-bricked-yureka-t3303112
Click to expand...
Click to collapse
Check this link It was not a solution for me xt1556.
http://forum.gsmhosting.com/vbb/13033054-post348.html
Please, let me know if it was useful for you.
So finally anyone with the loader.img??
dengupeye said:
Check this link It was not a solution for me xt1556.
http://forum.gsmhosting.com/vbb/13033054-post348.html
Please, let me know if it was useful for you.
Click to expand...
Click to collapse
news?
Any one with the whole 16gb sized file?
I have a device that has not been officially released yet so no images are available. I am trying to pull the boot and recovery images from the device so I can root and build twrp for it. That way when it is officially released it will be available. From there I would like to build a custom ROM or GSI.
I have read a lot of information and cannot seam to locate the correct location of the boot or recovery images. I have a prerooted GSI so I have root access to pull the images. The GSI with root has problems on my device. I have found a working GSI but I need my boot image to root it.
If someone could help me out pulling the boot and recovery images I would be greatly appreciative. I mostly figure out a lot of things on my own by searching and trying. I just cannot seam to figure this one out. Location of the images is the biggest problem.
Well, the boot and recovery partitions aren't mounted when Android is actually running.
The location of both the recovery.img and the boot.img is partition-layout dependent: possible partiton layouts are MTD ( read: Memory Technology Device ), EMMC ( read: Embedded Multimedia Card ) and MMC ( read: Multimedia Card ).
jwoegerbauer said:
Well, the boot and recovery partitions aren't mounted when Android is actually running.
The location of both the recovery.img and the boot.img is partition-layout dependent: possible partiton layouts are MTD ( read: Memory Technology Device ), EMMC ( read: Embedded Multimedia Card ) and MMC ( read: Multimedia Card ).
Click to expand...
Click to collapse
Thanks for your reply. I believe I have read about payload dumpers that can do this? I have not been able to figure it out though. What would be the easiest way to pull them?
Can anyone explain how to go about this?
Never have occupied with payload ...
FYI:
A phone's NAND-flash chip is parted into physical blocks what are called block devices: hence you have to find out the name of the block device where recovery and/or boot is located. Take note these names ( e.g. /dev/block/XXX ) are different on phones.
Once you got the names, and IF PHONE IS ROOTED, and phone's internal memory got mounted as RW, then you can extract these to your computer utilizing ADB commands:
Code:
adb devices
adb exec-out "dd if=/dev/block/<BOOT> of=C:\COPY-of-BOOT.img bs=4096"
jwoegerbauer said:
Never have occupied with payload ...
FYI:
A phone's NAND-flash chip is parted into physical blocks what are called block devices: hence you have to find out the name of the block device where recovery and/or boot is located. Take note these names ( e.g. /dev/block/XXX ) are different on phones.
Once you got the names, and IF PHONE IS ROOTED, and phone's internal memory got mounted as RW, then you can extract these to your computer utilizing ADB commands:
Code:
adb devices
adb exec-out "dd if=/dev/block/<BOOT> of=C:\COPY-of-BOOT.img bs=4096"
[/cod
[/QUOTE]
Click to expand...
Click to collapse
jwoegerbauer said:
Never have occupied with payload ...
FYI:
A phone's NAND-flash chip is parted into physical blocks what are called block devices: hence you have to find out the name of the block device where recovery and/or boot is located. Take note these names ( e.g. /dev/block/XXX ) are different on phones.
Once you got the names, and IF PHONE IS ROOTED, and phone's internal memory got mounted as RW, then you can extract these to your computer utilizing ADB commands:
Code:
adb devices
adb exec-out "dd if=/dev/block/<BOOT> of=C:\COPY-of-BOOT.img bs=4096"
Click to expand...
Click to collapse
Awesome thank you. When I installed a roasted gsi I seen them. I just did not know which one was recovery and which was the boot img. If I reinstall the rooted gsi and take a screenshot of the directory can you help me with the proper commands to copy them? This is just above my knowledge. Once I get them I can figure out how to use them.
Look also inside here:
[Guide] Dumping boot.img & recovery.img using dd (for complicated partitions)
Hi there! i am new to forums as well as in developing. i have recently taken interest in making cyanogenmod for my device. So, i have been searching web for hours to dump boot.img and recovery.img for my device. As my device is a mediatek device...
forum.xda-developers.com
jwoegerbauer said:
Look also inside here:
[Guide] Dumping boot.img & recovery.img using dd (for complicated partitions)
Hi there! i am new to forums as well as in developing. i have recently taken interest in making cyanogenmod for my device. So, i have been searching web for hours to dump boot.img and recovery.img for my device. As my device is a mediatek device...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you for all your help. I will give this a try and see if I can figure it out. I appreciate you taking the time to show me and help me.