Related
Hello there,
Today I will teach you how to make a full backup of your Spreadtrum phone !
This tutorial may also work on several other phones.
CWM can make a nearly full backup of your Spreadtrum, but it's not enough unfortunately.
Android is compartmented in 4 main partitions. You have theses partition:
* boot - It contains the Linux kernel
* System - It contains Android
* Recovery - It contains the recovery system, CWM if you installed it.
* DATA - It contain your personal datas, and should not be published online if you share your backup online.
But Android is one thing, your phone also have a lot of bios, firmwares, and bootloaders. Theses are not saved by traditional backup utilities such as CWM.
Theses partitions includes:
* UBoot - Very important, this thing is the low level bootloader. It starts Linux !
* Modem Firmware - used to dial with your GSM provider
* DSP Firmware - Make video playback smoother using DSP resources.
* NV - It's some kind of encryption key with some low levels parameters. Very important !
* Lots of misc stuffs - Like the boot logo, the kernel panics logs (record the boot-up errors to help the debugging process), etc ...
* Lots of important misc stuffs - For example what start-up the device even before handing the phone to Uboot.
This thread will cover a new way to backup your device, working "only" on rooted Spreadtrum devices.
With this you can recreate your original firmware file, and then rescue your phone even on the worst case you can find. (And help those with the same phone as you but have made a big flashing mistake)
So first, you will need to root your device. It may be simple or difficult, it all depends of the device you have. The instructions on how to root your device are here: http://forum.xda-developers.com/showthread.php?t=2165554
When you are rooted, you will have to install the Spreadtrum drivers if it's not already the case and log into your device with ADB.
You can download the drivers here:
http://www.mediafire.com/download.php?c5nf3rlhxmxhu4x
http://www.mediafire.com/download.php?2tyg0k2xp3ejgyg
You can download ADB and learn how it work here: http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/
Then you will have to tell adb what phone to use. By that I mean adding the PCI ID to a text file to tell adb that this peripheral is compatible.
The Spreadtrum PCI ID is 0x1782
add this line to "Your user directory/.android/adb_usb.ini"
Code:
0x1782
So when you are ready to go, you have to download this file: http://www.mediafire.com/download.php?y6wmegkc22gkr97
Then with adb, push it on your device with this command:
Code:
adb push backuptools.tar /data/local/tmp
Now we will extract the tools with this command:
Code:
adb shell su -c "tar -xvpf /data/local/tmp/backuptools.tar"
And now, let's start the backup process:
Code:
adb shell su -c "./mkbackup.sh"
and here we go, just wait a while and every partitions on your phone will be saved in the backup directory on the sd card !
You will never have to backup this way again as those partitions are read only, if you don't do crazy things they will never change. But if you want to make another backup I suggest you go with CWM (read this page if you don't have it: http://forum.xda-developers.com/showthread.php?t=2165554).
Please do another backup with CWM even if everything as gone right with this method. Just to double check !
PS: if CWM does not work for you, you just have to send me your boot.img file from your backup and I will make one compatible with your phone.
To restore your backups you will also need to have CWM, you also can use ResearchDownload if you manage to entirely brick your phone or if any attempts to make a CWM recovery fails. I will have to do a tutorial about that too.
Thanks a lot :good:
this is my boot.img after a full backup :www .mediafire.com/?gmnm65rn65b28c3
i need a CWM image for my GT-I9300 clone.
all the best.
monster-exodia said:
Thanks a lot :good:
this is my boot.img after a full backup :www .mediafire.com/?gmnm65rn65b28c3
i need a CWM image for my GT-I9300 clone.
all the best.
Click to expand...
Click to collapse
Hi,
Can I have the exact name of your device ? (it must be in the battery compartment)
Did you tried all the CWM already in the rooting tutorial ? (I added one this morning)
If none of them work, I made this recovery with the boot.img you provided: http://www.mediafire.com/download.php?aj2nman38j5cfip
Please don't forget to tell me what CWM work for you so I can add the name of your phone on the tutorial.
@ElectronikHear
phone model (in battery) : N9300
phone model : (system info) GT-I9300
Build number : MT6515M_C909_HT_V14
cpu hardware : SP6820A
..........
I never tried ... firslty how to to flash CMW recovery ?
thanks in advance.
deleted
monster-exodia said:
how to to flash CMW recovery ?
Click to expand...
Click to collapse
Well it's explained in the rooting tutorial.
If your phone have Fastboot you can flash using it. If you don't you can use the Spreadtrum flash utility called ResearchDownload.
Everything is here:
http://forum.xda-developers.com/showthread.php?t=2165554
As your phone is already rooted it will be a lot more simple to flash using "dd" or some android flashing utilities. Actually it doesn't work that way on theses phones, sorry ... So just do as the rooting tutorial explains.
Hi, I'm succesfully rooted my phone with the "rooted system partition image" method, but none of the CWM images work, so I would be grateful if you can send me the recovery image.
Device Info:
Phone model (in battery) : S6500-TV
Phone model : (system info) S560
Android Version: 4.0.3
Baseband Version: DM_BASE_12A_W12.32|sc8810_modem|08-9-2012 16:47:10
Kernel Version: 2.6.35.7 [email protected] #3
Software Version: T162_JYY_G2_P2_1_W1220P12_DNY_V0.8.1_20121015
Hardware Version: 1.1.0
boot.img : www .dropbox.com/s/ka43sd45em9lu9k/mtd9.boot.img
Thanks in advance.
monster-exodia said:
I never tried ... firslty how to to flash CMW recovery ?
thanks in advance.
Click to expand...
Click to collapse
Don't even try!
Backup first.
janzlev said:
Hi, I'm succesfully rooted my phone with the "rooted system partition image" method, but none of the CWM images work, so I would be grateful if you can send me the recovery image.
Device Info:
Phone model (in battery) : S6500-TV
Phone model : (system info) S560
Android Version: 4.0.3
Baseband Version: DM_BASE_12A_W12.32|sc8810_modem|08-9-2012 16:47:10
Kernel Version: 2.6.35.7 [email protected] #3
Software Version: T162_JYY_G2_P2_1_W1220P12_DNY_V0.8.1_20121015
Hardware Version: 1.1.0
boot.img : www .dropbox.com/s/ka43sd45em9lu9k/mtd9.boot.img
Thanks in advance.
Click to expand...
Click to collapse
Hi there,
Here is your new recovery: http://www.mediafire.com/download.php?iahnncpjhm44etn
Please tell me if it works so I can add it to the rooting tutorial ^^
Thank you very much !
Not working, after flashing the recovery, the phone enters into a boot loop.
Anyway thank you.
janzlev said:
Not working, after flashing the recovery, the phone enters into a boot loop.
Anyway thank you.
Click to expand...
Click to collapse
A boot loop ?
You mean the recovery is looping ? and if you try to boot as normal everything working ok ?
I don't know what has gone wrong ... Where did you find your boot.img ? Did you extract it from the rom as the tutorial said or extracted from a .pac file ?
Have you flashed it with fastboot or with ResearchDownload ?
ElectronikHeart said:
A boot loop ?
You mean the recovery is looping ? and if you try to boot as normal everything working ok ?
I don't know what has gone wrong ... Where did you find your boot.img ? Did you extract it from the rom as the tutorial said or extracted from a .pac file ?
Have you flashed it with fastboot or with ResearchDownload ?
Click to expand...
Click to collapse
Recovery does not start, normal boot enters into a boot loop, the boot.img is extracted from the rom as in the tutorial.
Flashed with ResearchDownload.
janzlev said:
Recovery does not start, normal boot enters into a boot loop, the boot.img is extracted from the rom as in the tutorial.
Flashed with ResearchDownload.
Click to expand...
Click to collapse
That's weird, really weird. Because the recovery partition is not involved in the normal boot procedure. So flashing a new recovery should not harm in any way the normal boot procedure.
I really don't know what have brought your phone in such state I'm afraid.
Maybe you should try to flash the recovery again. and see if everything is the same.
As the recovery is not involved in the normal boot process, it surely will not change anything, but as you have tried the over ones (CWM I mean), and that have not screwed your booting process, you may try to flash one of the non working ones again (but known for sure to not harm the boot process) to see if it work again.
Have you used the same FDL set as when you flashed the system partition and the over CWM ?
It's a good thing you have the full backup on your hand. Because you may surely be able to recover from that. I just have to make a tutorial about flashing the backup with ResearchDownload and explaining what file goes where from the backup.
ElectronikHeart said:
That's weird, really weird. Because the recovery partition is not involved in the normal boot procedure. So flashing a new recovery should not harm in any way the normal boot procedure.
I really don't know what have brought your phone in such state I'm afraid.
Maybe you should try to flash the recovery again. and see if everything is the same.
As the recovery is not involved in the normal boot process, it surely will not change anything, but as you have tried the over ones (CWM I mean), and that have not screwed your booting process, you may try to flash one of the non working ones again (but known for sure to not harm the boot process) to see if it work again.
Have you used the same FDL set as when you flashed the system partition and the over CWM ?
It's a good thing you have the full backup on your hand. Because you may surely be able to recover from that. I just have to make a tutorial about flashing the backup with ResearchDownload and explaining what file goes where from the backup.
Click to expand...
Click to collapse
Thanks would be really helpful, and yes I used the same FDL.
janzlev said:
Thanks would be really helpful, and yes I used the same FDL.
Click to expand...
Click to collapse
I made another CWM recovery for your phone, please try it: http://www.mediafire.com/download.php?lg7m6v49efzpnjk
Apparently was an error of ResearchDownload (It seems was flashing recovery.img into boot.), so I tried with another copy of ResearchDownload and FDL files and now works like a charm.
Thank you very much!
janzlev said:
Apparently was an error of ResearchDownload (It seems was flashing recovery.img into boot.), so I tried with another copy of ResearchDownload and FDL files and now works like a charm.
Thank you very much!
Click to expand...
Click to collapse
Can you tell me what version of ResearchDownload have this bug. It's a pretty scary one. I have to be sure I don't have it on my computer ...
By the way what CWM image is working ? The first or the second one ? (the two should work but I want to be sure before adding it to the main tutorial)
Thank you very much ! That's one more phone to the list of easily rootable Spreadtrums thanks to you !
Edit: And what FDLs you use precisely so I can rename the folder to reflect the use of this set for this phone (Is this the ones on the .pac firmware you've uploaded on the over topic ?)
RESEARCHDOWNLOAD R2.9.6010, with the R2.9.7002 everything's fine. Respect to the CWM images, after the error I tried with the second one, so maybe the first one also works, the FDLs that I used was extracted from the .pac dropbox.com/s/69yl8hn9361qpy5/FDLs-S6500-TV.tar
That's it, if I can help more, let me know.
janzlev said:
RESEARCHDOWNLOAD R2.9.6010, with the R2.9.7002 everything's fine. Respect to the CWM images, after the error I tried with the second one, so maybe the first one also works, the FDLs that I used was extracted from the .pac dropbox.com/s/69yl8hn9361qpy5/FDLs-S6500-TV.tar
That's it, if I can help more, let me know.
Click to expand...
Click to collapse
I think I have every informations I need ^^
I have added the recovery for S6500-TV to the main tutorial and will add in a short while the fdls to the FDL pack file.
Thanks again !
Backup
attached is my boot.img
to follow: entire backup
Good morning,
I tried to revert back to stock as I had to send my 10 to service.
So, I took an old NAND (which was working fine when updating firmware) and restored it in TWRP. I'm S-On with unlocked bootloader.
NAND went through but then I was stuck on boot screen.....
Power + Vol down brought me back to "stock!!!recovery. From there to bootloader and then back to TWRP.
Getvar all showed me nothing, just lines without any values.
I finally flashed the MM Viper rom with a full wipe and it booted again.........with all apps and setting.
I have no clue what happened. I only want to get back to stock.
same problem as you, no idea why
Glad, I'm not the only one facing that issue. Sad we don't know what it caused.
Maybe the NAND backup does not harmonize with the newer firmware? No clue.
But now I can't handle that chaotic system.
nerodarknight said:
same problem as you, no idea why
Click to expand...
Click to collapse
Prinz069 said:
Glad, I'm not the only one facing that issue. Sad we don't know what it caused.
Maybe the NAND backup does not harmonize with the newer firmware? No clue.
But now I can't handle that chaotic system.
Click to expand...
Click to collapse
Are you on N firmware, or MM firmware?
Try find RUU for your firmware, flash that, it will clean reset your phone back to everything stock.
Btw the "stock recovery" you found by pressing power + vol down, is not recovery at all. It is download mode (same thing as fastboot mode.)
Newer HTC devices will have this enhanced Download mode from now on.
If you can find an RUU zip then just place it in SDcard and reboot to Download mode and you can easily flash the RUU without needing to run a program on your computer.
I prefer this because I use Linux at home, and RUU.exe won't work on linux.
MM firmware, but Im s-on
Prinz069 said:
MM firmware, but Im s-on
Click to expand...
Click to collapse
Perfect, it will be very straight forward then...
Find RUU for your firmware, make sure mid and cid match.
Once you flash that, relock your bootloader and send it back to HTC for service.
Your warranty won't be void.
Cant read out cid as getvar shows now values
Prinz069 said:
Cant read out cid as getvar shows now values
Click to expand...
Click to collapse
Then make an estimated guess.
You are from germany, so your phone would probably be an european variant right?
Could be a GSM unlocked variant, or a carrier unit.
Find what version your phone is, and find the RUU for that version and hope that the CID/MID matches.
What about the non working getvar command? Ill post a screenshot later.
Prinz069 said:
What about the non working getvar command? Ill post a screenshot later.
Click to expand...
Click to collapse
That i do not know, i just hope your phone is not hard-bricked.
Try to RUU until something happens.
Good luck haha
You can check your CID onscreen when in download mode.
To get there Start device with Power + Vol- pressed.
As far as I know you then could try a CID/MIP matching RUU, that has to be same or newer version then the one you're running to flash that with S-ON. But don't nail me on that.
When you say "stuck on boot screen", what, exactly, does that mean? For how long? First boot can take 20+ mins easy before hitting the "configuring app X of Y" screen.
Download mode tells you your CID, MID, firmware version, etc.
Since you're sending it back in for service, yes, RUU it (via SD card zip). It's easy and thorough.
Boot into download mode and read your firmware. If you are MM/Germany you probably have 1.95.401.X firmware (same as mine - MM/Ger/Unlocked).
Go to RUU thread and download RUU zip that is exactly or higher firmware as yours.
Rename as instructed in that thread (2PS6IMG.zip or something like that) and put it on your SDcard.
Reboot Download mode, it will detect the zip and ask if you want to flash it.
Confirm and let it reboot.
Thank you guys, you're all awesome...wish we could have a couple of drinks together:good:
Prinz069 said:
Thank you guys, you're all awesome...wish we could have a couple of drinks together:good:
Click to expand...
Click to collapse
Perfect, you have a ".401" phone.
It's an unlocked version, same as mine. (and most lol).
You could try running RUU.exe...if it doesn't work, use TWRP to mount the sdcard (internal, not the external one) and transfer the RUU.zip to your phone.
Go back into download mode and flash RUU there.
There's an RUU decrypter tool to extract the zip elsewhere in this forum.
[RESTORE STARTED]
Restore folder: '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup'
Skipping MD5 check based on user setting.
Calculating restore details...
I:InfoManager file '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup/boot.info' not found.
I:Restore file system is: 'emmc'.
I:InfoManager file '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup/system_image.info' not found.
I:Restore file system is: 'emmc'.
Restoring 2 partitions...
Total restore size is 4784MB
I:Restore filename is: boot.emmc.win
I:Restore file system is: 'emmc'.
Restoring Boot...
I:Reading '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup/boot.emmc.win', writing '/dev/block/mmcblk0p59'
[Boot done (2 seconds)]
I:Restore filename is: system_image.emmc.win
I:Restore file system is: 'emmc'.
Restoring System Image...
I:Reading '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup/system_image.emmc.win', writing '/dev/block/mmcblk0p62'
Truncating string cache entries.
Truncating string cache entries.
I:Error writing destination fd (No space left on device)
This is the error I got for restoring the backup, can some explain the error for me?
nerodarknight said:
I:Error writing destination fd (No space left on device)
Click to expand...
Click to collapse
Could it be that?
dj_chapz said:
you probably have 1.95.401.X firmware
Click to expand...
Click to collapse
My Build is 1.95.401 when I check in Settings, But Downloade Mode says OS is 1.30.401.
Prinz069 said:
My Build is 1.95.401 when I check in Settings, But Downloade Mode says OS is 1.30.401.
Click to expand...
Click to collapse
Then you can flash pretty much any RUU zip to go back. Best bet would be the first newer RUU than 1.30.
I've noticed that many in this forum for the Honor 7x / Mate SE want to try a few ROMS, and then eventually go back to stock - Some just want to go back to stock. I had my own issues and thankfully there were others to help along the way. This method does not use fastboot to flash partitions, it uses TWRP, so the assumption is you have a working TWRP. Also I am not responsible for any bricks, I am just explaining what I did to get back to stock (And based on all the issues people are having, I'm staying there)
If you've tried a Treble ROM or others, the route I took to get back to stock was as follows:
1.) Download your firmware from Firmware finder or the Pro-TeamMT website:
http://pro-teammt.ru/firmware-database/?firmware_model=bnd-l34&firmware_page=0
In this example, mine is the Mate SE..
You should have downloaded 3 files. The important one we want right now is the Update.zip - Extract this file. You should see UPDATE.APP within this folder.
2.) Download the Huawei extractor software by worstenbrood:
https://forum.xda-developers.com/showthread.php?t=2433454
3.) Use this software to extract the files from the Update.App - You may need to disable the Checksum checks under "Settings". When you select the UPDATE.APP file, you should get a list of the files that are compiled or compressed into the app. The main 4 files you want are Ramdisk, Vendor, System, and if you'd like the Stock recovery (Recovey_Ramdisk). Copy these files to your SD card.
4.) Assuming you still have the functioning TWRP, reboot into TWRP and wipe everything but the SD card.
5.) Flash the images to the appropriate partition, Ramdisk = Ramdisk, Vendor = Vendor Image, and System = System Image - Ensure you're flashing the image partitions. Ramdisk is necessary if you've ever rooted or used Magisk.
At this point you should be able to reboot and get back into stock...But you'll notice Themes do not work properly..That's because you've wiped / formatted data at some point in TWRP, and now the Data/hw_int has been wiped. You can fix this by flashing the update on top of itself by the instructions in this thread (Thanks to mrmazak):
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
See the "Flash update while on Oreo"...This has worked twice now to get me back my themes after wiping /data.
I counted on my TWRP backup to get me back to stock after trying a Treble ROM, and I ended up bricked. So hopefully this helps someone!
PS, if anyone has more to add this this, the more help the better.
Wait, wouldn't the recovery be the file "RECOVERY_RAMDIS.img"
???
crayonicle said:
Wait, wouldn't the recovery be the file "RECOVERY_RAMDIS.img"
???
Click to expand...
Click to collapse
You are correct...That is the name of the actual image in the UPDATE.APP, but I was basing the name off of the actual partition.
Corrections, please add to original post
smokinjoe2122 said:
You are correct...That is the name of the actual image in the UPDATE.APP, but I was basing the name off of the actual partition.
Click to expand...
Click to collapse
Just learned today that you can't flash Vendor through Fastboot, so you have to copy all the necessary files onto a SD card or USD OTG.
The files needed are: "SYSTEM.img" "RECOVERY_RAMDIS.img" and "VENDOR.img"
Flash them through twrp in the required partitions, the partition names are literally the file names.
TWRP: https://forum.xda-developers.com/devdb/project/dl/?id=28883
crayonicle said:
Just learned today that you can't flash Vendor through Fastboot, so you have to copy all the necessary files onto a SD card or USD OTG.
The files needed are: "SYSTEM.img" "RECOVERY_RAMDIS.img" and "VENDOR.img"
Flash them through twrp in the required partitions, the partition names are literally the file names.
TWRP: https://forum.xda-developers.com/devdb/project/dl/?id=28883
Click to expand...
Click to collapse
System image can fail too...that's why I said to flash everything in TWRP...Plus, flashing the update on-top of itself will not only give you theming back, but stock recovery.
crayonicle said:
Just learned today that you can't flash Vendor through Fastboot, so you have to copy all the necessary files onto a SD card or USD OTG.
The files needed are: "SYSTEM.img" "RECOVERY_RAMDIS.img" and "VENDOR.img"
Flash them through twrp in the required partitions, the partition names are literally the file names.
TWRP: https://forum.xda-developers.com/devdb/project/dl/?id=28883
Click to expand...
Click to collapse
Is this working ? Did you try ? I'm on RR ROM and couldn't get adb recognize my device. This is my only hope to return to stock as of now.
Adithya Krishnakumar said:
Is this working ? Did you try ? I'm on RR ROM and couldn't get adb recognize my device. This is my only hope to return to stock as of now.
Click to expand...
Click to collapse
Yes, I tried it. It works flawlessly.
How can I get themes to work? I don't understand the original post, it makes no sense when explaining how to get themes to work properly. I do not know what to do with the link provided in the original post.
crayonicle said:
How can I get themes to work? I don't understand the original post, it makes no sense when explaining how to get themes to work properly. I do not know what to do with the link provided in the original post.
Click to expand...
Click to collapse
What part are you stuck on?
Essentially mrmazak created a flashable file that will take the 3 firmware files you download and flash them on top of your current firmware. This is helpful for doing an update or just reloading the firmware completely (Which is what you're trying to do)...
I'd follow the exact instructions that he's put out on that thread, but the 10,000 ft overview:
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
1.) Download files from link for your device
2.) Create a correctly named folder on your SD card, along with those files properly named in that folder (Ensure these files are named properly also.)
3.) Ensure you have the stock recovery on the SD card also.
4.) Copy the "xxx_Update.zip" he created onto your SD
5.) Flash the "xxx_Update.zip"...It will will flash the stock recovery, then boot into update mode and update with the 3 files you downloaded and put into that folder. This will basically "reflash" the firmware and give you back themes.
I would go step by step on his action list and follow them to a "T". I've verified it works perfectly. He also has a "Basic-Instructions" write up in the zip also.
My device build number was BND-L21C185, I bricked my device once but I managed to get it back. Since then I have strange build number which is system 8.0.0.046(063f). Does this method fix it?
This info helped me bring my phone back to life,thank you sir for the step by step instructions.
Found a way to get back to stock without all this hassle lol
So I thought this was the only way to get back to stock... turns out there is a much easier way
This method also enables themes, I checked myself.
https://forum.xda-developers.com/honor-7x/how-to/getting-to-stock-emui-super-easily-t3804722
Is it possible to flash all of the partitions from fastboot?
I have the BND-L34 and I am unsure as to what happened.
I have been running the RROS surdu_petru posted for about 3 weeks now and it was running fine.
2 days ago I grab my phone and it was booted into error mode. Now when I try to boot into twrp I get an error code for my recovery. When I try to boot into the system it throws a different error code for boot image.
I have a twrp backup stored on an sd card, and all 3 OTA's I saved back during the June update. I have the Pro-TeamMT app on my pc and have found/extracted every file for the brick method only get the same errors, 1 right after the other.
I am no noob, (although I am not a Senior Member with a giant banner either ) but I have been rooting android devices going on 8 years now, and have never completely bricked any of them.
My last 2 phones were Oneplus 1 and Oneplus 3, so I am familiar with flashing all the partitions using fastboot. But with those phones there were about 9 different individual flashes that needed to be done in a particular order.
Any help or advice would be greatly appreciated.
I am suddenly faced with glitching on splash screen, while the SAMSUNG GALAXY TAB displays when you switch on, it dims a bit, glitches ( shows lines on the screen ) and reboots continuously. I have reflashed stock firmware, cleared cache and wiped everything with no results. On TWRP recovery, the device works with no problem. I am currently charging it to 100% since I've heard it can be battery related.
Any help would be appreciated.
Regards to all.
in recovery, connect USB cable and do from PC:
adb shell cat /proc/last_kmsg > last_kmsg.txt
Click to expand...
Click to collapse
and send it here via attachment
gellmar said:
in recovery, connect USB cable and do from PC:
and send it here via attachment
Click to expand...
Click to collapse
Sorry to sound stupid, but can it be done from stock recovery or do I have to flash TWRP ? Also, is it run from CMD from Windows 10 ?
Ok got the file....how do I attach it? I've been a member here for years and never been able to attach files
@gellmar
Is this any good ?
https://drive.google.com/open?id=1nbL8TjLwm9fPPkG3a1yXSNbGzhteFZak
drowsy1982 said:
@gellmar
Is this any good ?
https://drive.google.com/open?id=1nbL8TjLwm9fPPkG3a1yXSNbGzhteFZak
Click to expand...
Click to collapse
Your EFS filesystem is corrupted, causing a reboot. You must try nandroid backuping it as is and extract all the data you can from it.
gellmar said:
Your EFS filesystem is corrupted, causing a reboot. You must try nandroid backuping it as is and extract all the data you can from it.
Click to expand...
Click to collapse
I can do Nandroid Back up from TWRP, but what's the next step ?
Found this EFS-Fix-regalstreak.tar.md5, to flash with Odin for currupted EFS.
Would it help ?
drowsy1982 said:
Found this EFS-Fix-regalstreak.tar.md5, to flash with Odin for currupted EFS.
Would it help ?
Click to expand...
Click to collapse
Probably not, but send me your EFS backup in PM - I can try restoring tge useful info from it and send you back the tar file and instructions.
gellmar said:
Probably not, but send me your EFS backup in PM - I can try restoring tge useful info from it and send you back the tar file and instructions.
Click to expand...
Click to collapse
As you said, the files mentioned didn't fix the problem. I managed to solve this however. I was flashing a single file stock firmware containing only the AP file. I tried another firmware containing AP, BL and CSC files with ODIN and booted without problems. Does the BL and CSC have anything to do with the corrupted EFS ?
drowsy1982 said:
As you said, the files mentioned didn't fix the problem. I managed to solve this however. I was flashing a single file stock firmware containing only the AP file. I tried another firmware containing AP, BL and CSC files with ODIN and booted without problems. Does the BL and CSC have anything to do with the corrupted EFS ?
Click to expand...
Click to collapse
BL is BootLoader aka S-BOOT. Usually, if this one becomes corrupted, your only option is to replace the NAND flash and flash the correct BL with JIG. Luckily this is not the case.
CSC is the carrier related info. Since you have T800, flashing this may have fixed the problem. Now chevk your device serial number in About Phone settings.
gellmar said:
BL is BootLoader aka S-BOOT. Usually, if this one becomes corrupted, your only option is to replace the NAND flash and flash the correct BL with JIG. Luckily this is not the case.
CSC is the carrier related info. Since you have T800, flashing this may have fixed the problem. Now chevk your device serial number in About Phone settings.
Click to expand...
Click to collapse
Still not botting fully.
In recovery now i'm getting failed to mount /efs (invalid argument)
The firmware I flashed was missing the CP file.
drowsy1982 said:
Still not botting fully.
In recovery now i'm getting failed to mount /efs (invalid argument)
The firmware I flashed was missing the CP file.
Click to expand...
Click to collapse
This is a dying NAND flash. Given that TWRP dumps efs as raw image, this is not a just filesystem issue.
I told you what to do in PM.
FIXED !
Followed the below guide, creates a generic EFS folder and then install an stock firmware.....ta daaaaaaaaa !!
http://zidroid.com/how-to-fix-failed-to-mount-efs-for-galaxy-s3-gt-i9300/
I deleted all the partitions on my g8 using qfil, now the phone has nothing but an edl mode. If someone could share a backup of the partitions that would get download mode working, I could flash a kdz I have with lgup.
Help would be appreciated
leopard_fist said:
I deleted all the partitions on my g8 using qfil, now the phone has nothing but an edl mode. If someone could share a backup of the partitions that would get download mode working, I could flash a kdz I have with lgup.
Help would be appreciated
Click to expand...
Click to collapse
So when u bring up 'manage partitions' in qfil, what do u see? Nothing? If that's the case u need the backed up partitions and the xml which has offsets etc of where to flash the images, not just the specific partitions.
cheers
AsItLies said:
So when u bring up 'manage partitions' in qfil, what do u see? Nothing? If that's the case u need the backed up partitions and the xml which has offsets etc of where to flash the images, not just the specific partitions.
cheers
Click to expand...
Click to collapse
there's nothin there in qfil, so I guess i'd need the xml also, anyone have this and could share?
i figure i can put a little work in before i throw in the cards and return the phone to amazon
leopard_fist said:
I deleted all the partitions on my g8 using qfil, now the phone has nothing but an edl mode. If someone could share a backup of the partitions that would get download mode working, I could flash a kdz I have with lgup.
Help would be appreciated
Click to expand...
Click to collapse
So I put together something that might help, but you'll probably have to make modifications to the xml to get it to work.
I don't know what the xml should look like for it to work with qfil. This is the xml generated by bkerler edl backup python scripts (with the bkerler scripts, you indicate, on the command line, where the bin files are, so it's not in the xml. But, I think the qfil interface needs that info to be in the xml. I could be wrong about that, you'll have to look at qfil and make changes to the xml if needed).
Also, the xml for luns 1 and 2 files are accurate, but not the xml for lun4. You would also need to edit out all the xml restore in rawprogram4 to only include the files for that lun (to get lgup - boot, abl, laf, and gpt*4).
Lastly, this is from a sprint backup, not sure that matters much except in that there is no kdz for sprint, so not sure how your device will respond in lgup if u use these and then try to lgup a vzw kdz (or any kdz), since there's no totc file to 'ID mismatch' with...
good luck
leopard_fist said:
there's nothin there in qfil, so I guess i'd need the xml also, anyone have this and could share?
i figure i can put a little work in before i throw in the cards and return the phone to amazon
Click to expand...
Click to collapse
wow, return the phone 'in the condition it was in when received' is usually a prerequisite right? In other words... not bricked?
good luck with that too.
AsItLies said:
wow, return the phone 'in the condition it was in when received' is usually a prerequisite right? In other words... not bricked?
good luck with that too.
Click to expand...
Click to collapse
thanks for your time - i'll give it a try when i get home from work this evening, even though it looks to be over my head maybe i can figure it out.
it's actually a sprint phone, though i know a way to crossflash anyway.
you figure i can't return the phone? i just spent 200 bucks on this phone a few days ago, i hope thats not the case
the thing is - my jobs getting ready to send me out of state for a new position. my present phones old, slow, and the screens cracked, so i thought id start things off by getting myself a decent phone and working on setting it up - at present though ive just got an unresponsive piece of plastic.
ive rooted many phones in my day, but this one got me, what can i say
leopard_fist said:
the thing is - my jobs getting ready to send me out of state for a new position. my present phones old, slow, and the screens cracked, so i thought id start things off by getting myself a decent phone and working on setting it up - at present though ive just got an unresponsive piece of plastic.
ive rooted many phones in my day, but this one got me, what can i say
Click to expand...
Click to collapse
Hey it's not my place to tell you what to do. But I can tell you, personally, if I screw up, I take responsibility for it.
leopard_fist said:
I deleted all the partitions on my g8 using qfil, now the phone has nothing but an edl mode. If someone could share a backup of the partitions that would get download mode working, I could flash a kdz I have with lgup.
Help would be appreciated
Click to expand...
Click to collapse
Just follow this thread.
netmsm said:
Just follow this thread.
Click to expand...
Click to collapse
netmsm, thanks for the reply - if I follow the instructions in the thread you linked, is it true that i'll have no imei and serial number on the phone after the process?
thanks again
leopard_fist said:
netmsm, thanks for the reply - if I follow the instructions in the thread you linked, is it true that i'll have no imei and serial number on the phone after the process?
thanks again
Click to expand...
Click to collapse
That's true. You lose IMEI when you erase all partitions. Except, you have crated a backup of Modemst(1 or 2) or FSG partitions so you can restore them, but after recovering from hard brick. So first recover phone following instructions then restore Modemst 1 and 2 or just the FSG.
If your phone is factory unlocked version and you have no backup maybe we can repair IMEI, maybe! Just recover the phone for now.
netmsm said:
That's true. You lose IMEI when you erase all partitions. Except, you have crated a backup of Modemst(1 or 2) or FSG partitions so you can restore them, but after recovering from hard brick. So first recover phone following instructions then restore Modemst 1 and 2 or just the FSG.
If your phone is factory unlocked version and you have no backup maybe we can repair IMEI, maybe! Just recover the phone for now.
Click to expand...
Click to collapse
I have backups of the following files - would the imei/serial info be contained in any of these?
thank you
ftm
modem_a
modem_b
op_a
op_b
sid_a
sid_b
abl_a
abl_b
boot_a
boot_b
leopard_fist said:
I have backups of the following files - would the imei/serial info be contained in any of these?
thank you
ftm
modem_a
modem_b
op_a
op_b
sid_a
sid_b
abl_a
abl_b
boot_a
boot_b
Click to expand...
Click to collapse
Nope, sorry to say. FTM keeps identity data as a temp place from which IMEI cannot be restored. However, you can find the original IMEI from FTM. You need a box to repair the IMEI. The only tool that can repair LG SDM855 phones' IMEI is Octopus. So, you know what to do, I guess ^_^