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
:crying:Last night, I installed the Android 8 update package on the forum.
Halfway through, an error is displayed and then exit.
I tried eRecovery and Hisuite, but all failed.
I tried it and found that the original recovery partition became recovery_ramdisk. It looks like the partition has changed.
What can I do to be able to return to emui5?
I have imagined "fastboot flashall", but I do not know how? Forgive my lame English
zzkeier said:
:crying:Last night, I installed the Android 8 update package on the forum.
Halfway through, an error is displayed and then exit.
I tried eRecovery and Hisuite, but all failed.
I tried it and found that the original recovery partition became recovery_ramdisk. It looks like the partition has changed.
What can I do to be able to return to emui5?
I have imagined "fastboot flashall", but I do not know how? Forgive my lame English
Click to expand...
Click to collapse
recovery_ramdisk. is the new name of recovery partition. EMUI8/Oreo flashing has started means the partitions etc have changed already so right now you can't go back to EMUI 5 as rollback images are not available yet. You can try to flash again properly with proper download for your specific model. I guess you are missing some echo commands.
thank you very much
SVR said:
recovery_ramdisk. is the new name of recovery partition. EMUI8/Oreo flashing has started means the partitions etc have changed already so right now you can't go back to EMUI 5 as rollback images are not available yet. You can try to flash again properly with proper download for your specific model. I guess you are missing some echo commands.
Click to expand...
Click to collapse
I extract the update.app(oreo) file and then i flash the system.img. Now it works..Thank you
hey how did you did that?
zzkeier said:
I extract the update.app(oreo) file and then i flash the system.img. Now it works..Thank you
Click to expand...
Click to collapse
I also have similar problem I installed different model rom using firmware finder and now I can only use my phone when I unlock bootloader when I lock it it will not open directly go into the erecovery and nothing is working I tried everything twrp,erecovery,force updating nothing worked all failed.please help
shrey2204 said:
I also have similar problem I installed different model rom using firmware finder and now I can only use my phone when I unlock bootloader when I lock it it will not open directly go into the erecovery and nothing is working I tried everything twrp,erecovery,force updating nothing worked all failed.please help
Click to expand...
Click to collapse
well,I flash the system.img by fastboot,and then make a factory reset.Bootloader unlock needed.
i have the same problem
I tried to upgrade phone to Oreo after unlock, in update progress it got error and restart phone! Now it shows:
Code:
Error Mode
Attention!
Please update system again
Error!
Func No : 11 (recovery image)
Error No : 2 ( load failed )
I just have access to fastboot
i did flash system.img and tried install twrp on ramdisk recovery. but always same
:crying::crying::crying::crying:
I upgraded my phone to android EMUI8 and tried to install the RR 8.1 ROM but my device wouldn't boot up. Then I tried to reflash the stock system.img but it won't let me. I don't have TWRP on my phone but I can acces fastboot. Does anyone know what to do? Thanks in advance :^l
jetzecazemier said:
I upgraded my phone to android EMUI8 and tried to install the RR 8.1 ROM but my device wouldn't boot up. Then I tried to reflash the stock system.img but it won't let me. I don't have TWRP on my phone but I can acces fastboot. Does anyone know what to do? Thanks in advance :^l
Click to expand...
Click to collapse
What is it you mean , it won't let you. Does it give a message. Failed?
Are you at frp locked?
mrmazak said:
What is it you mean , it won't let you. Does it give a message. Failed?
Are you at frp locked?
Click to expand...
Click to collapse
Well when I try to flash the stock 8.0 system.img it gives me a "Invalid sparse file format at header magi" and when I try to flash TWRP it gives me a "FAILED (remote: partition length get error) I am frp unlocked by the way.
jetzecazemier said:
Well when I try to flash the stock 8.0 system.img it gives me a "Invalid sparse file format at header magi" and when I try to flash TWRP it gives me a "FAILED (remote: partition length get error)
Click to expand...
Click to collapse
Ok, that does not seem too bad, yet.
I suppose you are using system.img downloaded from web.
That image has given many that same error.
Best to use your system.img.
And the error flashing twrp, is common when using the nougat command or nougat recovery on Oreo.
Solutions.
Find your firmware on pro-teammt
http://pro-teammt.ru/firmware-database/?firmware_model=Bnd-&firmware_page=0
Then download update.zip
Extract files.
Get hauwei update extractor.
https://www.google.com/url?sa=t&sou...FjAAegQIARAB&usg=AOvVaw0xkKEyI85nY9x4Fjr1AWJl
Extract the system.img
Then fastboot flash it.
Recovery:
Oreo command== fastboot flash recovery_ramdisk twrp_ramdisk
Twrp name depends on version used. I use build 4 from here
https://forum.xda-developers.com/p10-lite/development/recovery-twrp-3-2-1-0-t3783447
mrmazak said:
Ok, that does not seem too bad, yet.
I suppose you are using system.img downloaded from web.
That image has given many that same error.
Best to use your system.img.
And the error flashing twrp, is common when using the nougat command or nougat recovery on Oreo.
Solutions.
Find your firmware on pro-teammt
http://pro-teammt.ru/firmware-database/?firmware_model=Bnd-&firmware_page=0
Then download update.zip
Extract files.
Get hauwei update extractor.
https://www.google.com/url?sa=t&sou...FjAAegQIARAB&usg=AOvVaw0xkKEyI85nY9x4Fjr1AWJl
Extract the system.img
Then fastboot flash it.
Recovery:
Oreo command== fastboot flash recovery_ramdisk twrp_ramdisk
Twrp name depends on version used. I use build 4 from here
https://forum.xda-developers.com/p10-lite/development/recovery-twrp-3-2-1-0-t3783447
Click to expand...
Click to collapse
Okay so I've downloaded the latest firmware for my model but when I try to extract the update.app inside of the update.zip file the huawei zip extractor gives me "RECOVERY_RAMDIS.img: Invalid header crc - Expected: 15200 Got: 44917
jetzecazemier said:
Okay so I've downloaded the latest firmware for my model but when I try to extract the update.app inside of the update.zip file the huawei zip extractor gives me "RECOVERY_RAMDIS.img: Invalid header crc - Expected: 15200 Got: 44917
Click to expand...
Click to collapse
yes there is a bug either in the extractor or the update files. they all do it. Go to the settings tab and take check mark off verify header.
mrmazak said:
yes there is a bug either in the extractor or the update files. they all do it. Go to the settings tab and take check mark off verify header.
Click to expand...
Click to collapse
I flashed the system.img but now the phone bootloops. It could be possible I got the wrong system.img because I don't know exactly what firmware my phone was on before I messed up. I only know it was EMUI8. Is there a way to completely reflash everything?
jetzecazemier said:
I flashed the system.img but now the phone bootloops. It could be possible I got the wrong system.img because I don't know exactly what firmware my phone was on before I messed up. I only know it was EMUI8. Is there a way to completely reflash everything?
Click to expand...
Click to collapse
Yes. I have guide thread here for that.
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
But also wipe in factory reset from stock recovery may solve the bootloop.
mrmazak said:
Yes. I have guide thread here for that.
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
But also wipe in factory reset from stock recovery may solve the bootloop.
Click to expand...
Click to collapse
Alright, I'll try that before I have a look at that thread
mrmazak said:
Yes. I have guide thread here for that.
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
But also wipe in factory reset from stock recovery may solve the bootloop.
Click to expand...
Click to collapse
I tried rebooting to stock recovery in order to factory reset but it only shows me the update, power off and reboot options so no factory reset possibility. I read through the entire thread you linked here but I'm very confused as to what to do with the full OTA file. I'm on a broken EMUI8 that bootloops and I'd like to clean flash EMUI8 again so I can flash an AOSP Oreo rom after that. What do I do?
jetzecazemier said:
I tried rebooting to stock recovery in order to factory reset but it only shows me the update, power off and reboot options so no factory reset possibility. I read through the entire thread you linked here but I'm very confused as to what to do with the full OTA file. I'm on a broken EMUI8 that bootloops and I'd like to clean flash EMUI8 again so I can flash an AOSP Oreo rom after that. What do I do?
Click to expand...
Click to collapse
Just made updates to guide last night. I think it is worded simple now.
Download my update "package" from step E
Extract it to a folder on your PC.
You are on emui8, so copy the HWOTA folder from the extracted zip to your sdcard
Also put hwota-update-7-8-auto.zip on sdcard.
Put the three (3) update files from pro-teammt.ru in the HWOTA8 folder on your sdcard
Put card into phone
Boot into twrp
Select install
Choose sdcard as source
Install hwota-update-7-8-auto.zip
mrmazak said:
Just made updates to guide last night. I think it is worded simple now.
Download my update "package" from step E
Extract it to a folder on your PC.
You are on emui8, so copy the HWOTA folder from the extracted zip to your sdcard
Also put hwota-update-7-8-auto.zip on sdcard.
Put the three (3) update files from pro-teammt.ru in the HWOTA8 folder on your sdcard
Put card into phone
Boot into twrp
Select install
Choose sdcard as source
Install hwota-update-7-8-auto.zip
Click to expand...
Click to collapse
So far so good but the FULLOTA update file I got from that website only has one file (update.zip) Do I need to extract that? And if so, what 3 files do I put on my sdcard?
jetzecazemier said:
So far so good but the FULLOTA update file I got from that website only has one file (update.zip) Do I need to extract that? And if so, what 3 files do I put on my sdcard?
Click to expand...
Click to collapse
No do not extract it.
On that site, next to link for update file, is "file list"
Click this. It gives links for all three files.
Put those three zip files into hwota folder
mrmazak said:
No do not extract it.
On that site, next to link for update file, is "file list"
Click this. It gives links for all three files.
Put those three zip files into hwota folder
Click to expand...
Click to collapse
Alright, I got it! Now I need to flash TWRP but the executable to install TWRP says my adb drivers are outdated. I have the minimal fastboot and adb installation from XDA.
jetzecazemier said:
Alright, I got it! Now I need to flash TWRP but the executable to install TWRP says my adb drivers are outdated. I have the minimal fastboot and adb installation from XDA.
Click to expand...
Click to collapse
That should be fine.
Usually means you have other adb also , probably from other tool.
If you have twrp , not need to use the terp recovery installer
mrmazak said:
That should be fine.
Usually means you have other adb also , probably from other tool.
If you have twrp , not need to use the terp recovery installer
Click to expand...
Click to collapse
Well the problem is I don't have TWRP and none of the versions i've tried to install work. The installer doesn't work either, it says closing adb daemon and stays on that.
jetzecazemier said:
Well the problem is I don't have TWRP and none of the versions i've tried to install work. The installer doesn't work either, it says closing adb daemon and stays on that.
Click to expand...
Click to collapse
Each step of the tool I put pause.
So it stopped on command and not closed.
Press spacebar
mrmazak said:
Each step of the tool I put pause.
So it stopped on command and not closed.
Press spacebar
Click to expand...
Click to collapse
Dude, you're the man! I got my device up and running again. I'll probably stay on EMUI8 since it's more stable than the current AOSP rom. I wanna root it tho so can I just use the lazy recovery tool to install twrp and simply install magisk?
jetzecazemier said:
Dude, you're the man! I got my device up and running again. I'll probably stay on EMUI8 since it's more stable than the current AOSP rom. I wanna root it tho so can I just use the lazy recovery tool to install twrp and simply install magisk?
Click to expand...
Click to collapse
Yes.
The lazy tool has recovery with encryption working
I got it working on EMUI8 but I decided to flash the aosp rom cuz i prefer stock android. Can't seem to get twrp to install tho. I keep getting "1 was unexpected at this time"
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Click to expand...
Click to collapse
Doing the update second time is fine, and best way to restore full stock. But you needed to use Oreo version of no-check recovery and the Oreo partition to flash it to.
So if still able to get into twrp, can try with correct no-check recovery and correct partition it's flashed to.
Also
With multi tool , make sure you put check mark on emui 8. Up in upper right corner. That way it uses Oreo partition names and file not nougat.
The partition length over message usually means nougat file or partition name used on Oreo system
mrmazak said:
Doing the update second time is fine, and best way to restore full stock. But you needed to use Oreo version of no-check recovery and the Oreo partition to flash it to.
So if still able to get into twrp, can try with correct no-check recovery and correct partition it's flashed to.
Also
With multi tool , make sure you put check mark on emui 8. Up in upper right corner. That way it uses Oreo partition names and file not nougat.
The partition length over message usually means nougat file or partition name used on Oreo system
Click to expand...
Click to collapse
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Mohammadreza76646 said:
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Click to expand...
Click to collapse
I give my phone to a friend to work on it. If he can't fix it I try new multi tools version to flash phone.
Mohammadreza76646 said:
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Click to expand...
Click to collapse
On the extractor app. On options tab uncheck the verify header option, it should extract then.
Then perhaps first do these three partitions.
Kernel.img
Ramdisk.img
Then
twrp_ramdisk or for stock use recovery_ramdisk
Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Click to expand...
Click to collapse
I ever have similiar problem with you dude, but it's solved now, if you always stuck on " its OK but when my phone want to start its stuck on google page "just a sec...", its call google accont verification, i'll by bypass with this script, save as to .bat and put on adb folder
adb devices
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
adb shell am start -n com.google.android.gsf.login/
adb shell am start -n com.google.android.gsf.login.LoginActivity
pause
in fastboot type:
fastboot -w
after all it's works to me to bypass google account verification
and if now your problem is
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
i solve with re-flash system from this
https://androidfilehost.com/?fid=673956719939830152
fastboot flash system system.img
and doing TWRP Flashing
https://forum.xda-developers.com/devdb/project/?id=25826#downloads
fastboot flash recovery_ramdisk complete_twrp_ramdisk.img
and voila my problem solved..
mrmazak said:
On the extractor app. On options tab uncheck the verify header option, it should extract then.
Then perhaps first do these three partitions.
Kernel.img
Ramdisk.img
Then
twrp_ramdisk or for stock use recovery_ramdisk
Click to expand...
Click to collapse
Hello again dude.
Finally I flashed my phone and I got the system installed.
But now my phones IMEI is lost. and I cant put sim on it!!!
what should I do now???
FRP is locked! (
Mohammadreza76646 said:
Hello again dude.
Finally I flashed my phone and I got the system installed.
But now my phones IMEI is lost. and I cant put sim on it!!!
what should I do now???
FRP is locked! (
Click to expand...
Click to collapse
So now is locked frp. Does phone have twrp or stock now.?
I think when you tried to install the oreo update for second time, you followed same tutorial as the first time. And that made you problem worse. The tutorial has you flash no-check recovery to 2 partition by block number. 22 & 29. On nougat that is "recovery" and "recovery2". On Oreo partion table it is "reserved2" & "erecovery_vendor"
I don't know how to fix imei. Have hope that if to ucan have a full ota install , maybe can be fixed.
There is available a "service rom" (used to fix most all problem) for Europe region with l21.
I can share link to site with service rom if you want , but I have not used it myself so not gonna be much help with it.
Link is to rusian language page. Google should translate for you.
https://4pda.ru/forum/index.php?showtopic=879524&view=findpost&p=73818595
mrmazak said:
So now is locked frp. Does phone have twrp or stock now.?
I think when you tried to install the oreo update for second time, you followed same tutorial as the first time. And that made you problem worse. The tutorial has you flash no-check recovery to 2 partition by block number. 22 & 29. On nougat that is "recovery" and "recovery2". On Oreo partion table it is "reserved2" & "erecovery_vendor"
I don't know how to fix imei. Have hope that if to ucan have a full ota install , maybe can be fixed.
There is available a "service rom" (used to fix most all problem) for Europe region with l21.
I can share link to site with service rom if you want , but I have not used it myself so not gonna be much help with it.
Link is to rusian language page. Google should translate for you.
https://4pda.ru/forum/index.php?showtopic=879524&view=findpost&p=73818595
Click to expand...
Click to collapse
It have stock recovery.
Mohammadreza76646 said:
It have stock recovery.
Click to expand...
Click to collapse
in summery. because i have been going back and forth in multiple different groups, multiple problem, i cant remember it all.
you have broken system, from failed root attempt, followed by failed update.
device condition is as follows.
--system not booting
--stock recovery loads
--fastboot/bootloader loads, but is in frp lock status
options are limited, at best.
I think "dload" method with service rom is best.
other option is maybe paid service like dc-unlock. But I can recall some note on there service about frp-unlock, that can only be used on device with working system. (of course if was working system, wouldn't need dc-unlock)
mrmazak said:
in summery. because i have been going back and forth in multiple different groups, multiple problem, i cant remember it all.
you have broken system, from failed root attempt, followed by failed update.
device condition is as follows.
--system not booting
--stock recovery loads
--fastboot/bootloader loads, but is in frp lock status
options are limited, at best.
I think "dload" method with service rom is best.
other option is maybe paid service like dc-unlock. But I can recall some note on there service about frp-unlock, that can only be used on device with working system. (of course if was working system, wouldn't need dc-unlock)
Click to expand...
Click to collapse
No. System boot successfully!
I will send you screenshot:
Mohammadreza76646 said:
No. System boot successfully!
I will send you screenshot:
Click to expand...
Click to collapse
here you are
Mohammadreza76646 said:
here you are
Click to expand...
Click to collapse
what about the "about phone" screen
what does it show for version?
If is all stock you should be able to go into deveolper options and enable "oem unlock". If it is greyed out and cannot switch it. Try First to remove google account (all accounts ). and reboot. See if can change then. If not, try Second to do "fastboot oem relock [enter your bootloader code here]
after relock and rebooted oem switch should be enabled again.
****RELOCK IS ONLY ADVISED IF 100% STOCK ROM****
otherwise relock could make more trouble.
Still not sure how to get IMEI back even if unlocked frp though.
**And please stop posting in other threads , the same problem , because you are getting help here.
your post in recovery thread is off topic to that thread and just makes the forum harder to maintain.
mrmazak said:
what about the "about phone" screen
what does it show for version?
If is all stock you should be able to go into deveolper options and enable "oem unlock". If it is greyed out and cannot switch it. Try First to remove google account (all accounts ). and reboot. See if can change then. If not, try Second to do "fastboot oem relock [enter your bootloader code here]
after relock and rebooted oem switch should be enabled again.
****RELOCK IS ONLY ADVISED IF 100% STOCK ROM****
otherwise relock could make more trouble.
Still not sure how to get IMEI back even if unlocked frp though.
**And please stop posting in other threads , the same problem , because you are getting help here.
your post in recovery thread is off topic to that thread and just makes the forum harder to maintain.
Click to expand...
Click to collapse
Thanks )
I'm so sorry for my posts, it's because I don't have a stable connection and I can't see notification of my thread.
I gave my phone to friend an he fix IMEI (I don't know how)
But OEM is steel lock.
I think he did it with using special box.
Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!![/QUOTE
Are u able.to boot into twrp ?
Click to expand...
Click to collapse
Hello I have a Huawei Mate-SE (with bootloader unlocked and rooted with magisk v16). I have been using the android custom rom RRO v6 (RR-O-v6.0.0-20180401-bnd-OpenKirin) for around a month now. I got this exact same problem about the White Screen saying "ERROR MODE Attention...." since I updated the Magisk to latest version (from the installed application) and rebooted my phone. SInce I rebooted I am getting that same error which makes the phone loops into it for a few times and then it loads the Huawei eRecovery that offers me some options that I am not sure what would do to my phone.
I have been trying to connect to adb tools/fastboot but it doesn't detect the phone and im pretty sure I have the device drivers installed on my computer since nothing have changed in my pc for a month now since I flashed RRO on it.
Is there any other mode besides recovery that would allow me to connect adb/fastboot to it? Or does anyone knows how should I proceed?
IonDEfeso said:
Hello I have a Huawei Mate-SE (with bootloader unlocked and rooted with magisk v16). I have been using the android custom rom RRO v6 (RR-O-v6.0.0-20180401-bnd-OpenKirin) for around a month now. I got this exact same problem about the White Screen saying "ERROR MODE Attention...." since I updated the Magisk to latest version (from the installed application) and rebooted my phone. SInce I rebooted I am getting that same error which makes the phone loops into it for a few times and then it loads the Huawei eRecovery that offers me some options that I am not sure what would do to my phone.
I have been trying to connect to adb tools/fastboot but it doesn't detect the phone and im pretty sure I have the device drivers installed on my computer since nothing have changed in my pc for a month now since I flashed RRO on it.
Is there any other mode besides recovery that would allow me to connect adb/fastboot to it? Or does anyone knows how should I proceed?
Click to expand...
Click to collapse
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
mrmazak said:
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
Click to expand...
Click to collapse
Hi thank you I was able to finally detect the device now. I am unsure about the kernel is that the recovery.img or system.img files I downloaded (i saved every file i used when I installed the rom) or do I need to look for the kernel somewhere else? I do have the complete_twrp_ramdisk.img file though.
Edit, I did more research and found the stock kernel is withing the boot.img file which I dont have so I looked up for the official BND-L34 oreo update and im currently downloading to extract the stock boot.img from the update.zip and flash it. Since that download was going to take me a while anyway i tried flashing the twrp recovery file without success (didn't changed anything) so i guess I should follow the instructions you gave me by flashing the kernel first then the twrp recovery.
mrmazak said:
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
Click to expand...
Click to collapse
Do you know what the boot.img files name is after extraction?
I have extracted all 3 update zips and cannot find anything called boot.img
By the way, thank you.. After updating magisk I have been dealing with failed recovery and failed boot for over a week and this is the first reply anywhere that looks promising
IonDEfeso said:
Hi thank you I was able to finally detect the device now. I am unsure about the kernel is that the recovery.img or system.img files I downloaded (i saved every file i used when I installed the rom) or do I need to look for the kernel somewhere else? I do have the complete_twrp_ramdisk.img file though.
Edit, I did more research and found the stock kernel is withing the boot.img file which I dont have so I looked up for the official BND-L34 oreo update and im currently downloading to extract the stock boot.img from the update.zip and flash it. Since that download was going to take me a while anyway i tried flashing the twrp recovery file without success (didn't changed anything) so i guess I should follow the instructions you gave me by flashing the kernel first then the twrp recovery.
Click to expand...
Click to collapse
if you were on oreo. then there is not a boot.img, instaed there is seperate ramdisk.img and kernel.img.
i have all the files already extracted for oreo and a backup from nougat as well.
https://androidfilehost.com/?w=files&flid=265998
make sure you know what you are doing before flashing.
for example. on oreo the boot and recovery share one kernel image. SO if kernel is messed up you will not be able to boot "boot" or "recovery"
A lot of people rooted are having issues with DEX with either systemUI closing, systemuidex closing or the app only staying open on PC pr TV for a few seconds.
Please can anyone who is rooted please let me know if they can access DEX and if so - is it working for you?
Please show a pic of magisk front screen with version number and state your exact rooting procedure
Hopefully we can then find out what is breaking dex
UNLESS anyone knows what sort of log may diagnose the issue? I have a dumpstate/logcat but not sure what part im looking at
exocetdj said:
A lot of people rooted are having issues with DEX with either systemUI closing, systemuidex closing or the app only staying open on PC pr TV for a few seconds.
Please can anyone who is rooted please let me know if they can access DEX and if so - is it working for you?
Please show a pic of magisk front screen with version number and state your exact rooting procedure
Hopefully we can then find out what is breaking dex
UNLESS anyone knows what sort of log may diagnose the issue? I have a dumpstate/logcat but not sure what part im looking at
Click to expand...
Click to collapse
We're do I get root how to for the u version
The only version that is rooted is the B version. The international, European, and North American versions are not able to be rooted.
We have root on the B variant
I believe the issue is related to having the "Data" folder being decrypted - This "Decrypting" process is on step # 4 under the 2nd process "PROCESS IF COMING FROM STOCK A12"
I have tried the process without the "Formatting the data" step which allows me to boot with root + Dex working. The only issue is that I'm limited to storage, It's fixed to 32gb out of the original size(512gb). Is there a way to resolve the limited storage issue?
Note: If we decrypt the data(Format data via twrp), we are restricted to:
- Cannot share pics in Samsung Gallary
- Dex's system ui constantly crashes
- Cannot install apps such as games that requires external downloads from installing an apk
- GMail cannot download embed files from an email
- ETC anything related to storage within the data, we cannot access/delete/edit when the data is decrypted
lilplanet said:
I believe the issue is related to having the "Data" folder being decrypted - This "Decrypting" process is on step # 4 under the 2nd process "PROCESS IF COMING FROM STOCK A12"
I have tried the process without the "Formatting the data" step which allows me to boot with root + Dex working. The only issue is that I'm limited to storage, It's fixed to 32gb out of the original size(512gb). Is there a way to resolve the limited storage issue?
Note: If we decrypt the data(Format data via twrp), we are restricted to:
- Cannot share pics in Samsung Gallary
- Dex's system ui constantly crashes
- Cannot install apps such as games that requires external downloads from installing an apk
- GMail cannot download embed files from an email
- ETC anything related to storage within the data, we cannot access/delete/edit when the data is decrypted
Click to expand...
Click to collapse
Thats some great info thanks very much
although that would also effect the download and install of Magisk potentially and that works - do you have an example of an app or game doing this so i can test?
i can confirm i cannot share pics directly from gallery but can within apps such as telegram
Downloading docs from Gmail is buggered
Dex is RIP.
@ianmacd do you think there is something we could be missing - we are effectively doing the disabler's job manually on F926B and its not unreasonable to think we may have missed something - could running the multidisabler be useful to see if it picks something up (even if it completely breaks things) so that we can then do the required modification manually?
exocetdj said:
Thats some great info thanks very much
although that would also effect the download and install of Magisk potentially and that works - do you have an example of an app or game doing this so i can test?
i can confirm i cannot share pics directly from gallery but can within apps such as telegram
Downloading docs from Gmail is buggered
Dex is RIP.
@ianmacd do you think there is something we could be missing - we are effectively doing the disabler's job manually on F926B and its not unreasonable to think we may have missed something - could running the multidisabler be useful to see if it picks something up (even if it completely breaks things) so that we can then do the required modification manually?
Click to expand...
Click to collapse
Me again
BVA9 STOCKRooted !
No sharing issues , and 100% working DEX
I used your BL file , extracted recovery from your AP File to make an Odin flashable TWRP.tar to sideload and flash your app-debug.zip
pvillasuso said:
Me again
BVA9 STOCKRooted !
No sharing issues , and 100% working DEX
I used your BL file , extracted recovery from your AP File to make an Odin flashable TWRP.tar to sideload and flash your app-debug.zip
Click to expand...
Click to collapse
whats your internal storage size? and have you reset device since you last managed to get this working?
Yes , I have reseted the phone.
When flashing to stock I used CSC ( the one that wipes data )
Did a stock recovery factory reset and also format data when I used the twrp recovery .
There is something with wrong with your AP file Bro , because I first used that file , and I tried the camera and had the sharing issue . Same happened with your older build , So I think the problem is there.
I Have the 256gb version
pvillasuso said:
Yes , I have reseted the phone.
When flashing to stock I used CSC ( the one that wipes data )
Did a stock recovery factory reset and also format data when I used the twrp recovery .
There is something with wrong with your AP file Bro , because I first used that file , and I tried the camera and had the sharing issue . Same happened with your older build , So I think the problem is there.
I Have the 256gb version
Click to expand...
Click to collapse
Ok sounds promising
Please can you provide a step by step procedure here and if i can replicate it i will amend the first post and files in the rooting thread
looks like formatting in TWRP could be the issue then - and we need to format at a different stage? (please still provide full process)
exocetdj said:
looks like formatting in TWRP could be the issue then - and we need to format at a different stage? (please still provide full process)
Click to expand...
Click to collapse
Yes , do that factory reset from stock recovery .
I also think the twrp format is not working as expected
edit : about the full process...
I ended again in a mess , and did several random stuff (as I got stuck some times in Download mode)
But .. If you ask me what I think that works , it would be like this:
1. Flash odin to stock , NOT using HOME_CSC
2. Do the initial setup (usb debugging and OEM status ( if shown ) checked
3. Flash odin the BL file , and TWRP.tar
4. TWRP , format ( I think nothing happened in this step ), reboot to TWRP , sideload and flash app-debug.zip
5. Reboot to download mode and flash stock recovery , and do the factory reset there ( at this step I tought I woud lose the previously flashed magisk stuff , but that didnt happen, and I got booted & rooted )
******
So I'm sure the BL file helped me to flash TWRP , because I tried it alone (TWRP) and it didn't work ( got bootloops ending in download mode ).
What I didn't try , now that Im reading myself , was to do a factory reset from stock , after doing that initial setup , and tried to flash that TWRP file right after that.
links to files :
AP_twrp_F926B_A12_BVA9
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
AP_stockrecovery_F926B_A12_BVA9
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
pvillasuso said:
Yes , do that factory reset from stock recovery .
I also think the twrp format is not working as expected
edit : about the full process...
I ended again in a mess , and did several random stuff (as I got stuck some times in Download mode)
But .. If you ask me what I think that works , it would be like this:
1. Flash odin to stock , NOT using HOME_CSC
2. Do the initial setup (usb debugging and OEM status ( if shown ) checked
3. Flash odin the BL file , and TWRP.tar
4. TWRP , format ( I think nothing happened in this step ), reboot to TWRP , sideload and flash app-debug.zip
5. Reboot to download mode and flash stock recovery , and do the factory reset there ( at this step I tought I woud lose the previously flashed magisk stuff , but that didnt happen, and I got booted & rooted )
******
So I'm sure the BL file helped me to flash TWRP , because I tried it alone (TWRP) and it didn't work ( got bootloops ending in download mode ).
What I didn't try , now that Im reading myself , was to do a factory reset from stock , after doing that initial setup , and tried to flash that TWRP file right after that.
links to files :
AP_twrp_F926B_A12_BVA9
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
AP_stockrecovery_F926B_A12_BVA9
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Click to expand...
Click to collapse
do you have stock recovery or TWRP installed now you have root?
exocetdj said:
do you have stock recovery or TWRP installed now you have root?
Click to expand...
Click to collapse
Stock recovery now
I can try to flash twrp , and can go back to stock recovery if it doesnt work
exocetdj said:
do you have stock recovery or TWRP installed now you have root?
Click to expand...
Click to collapse
the key is that if you install TWRP now and dex and file sharing etc etc is still working then i need to look at these files
As far as im aware = the DEX issues are a result of having TWRP installed
exocetdj said:
the key is that if you install TWRP now and dex and file sharing etc etc is still working then i need to look at these files
As far as im aware = the DEX issues are a result of having TWRP installed
Click to expand...
Click to collapse
Well, then I can try to install twrp , and launch DEX to see how it goes
Be right back and let you know
edit :
Flashed TWRP successfully !
No sharing issues , Dex working fine !
pvillasuso said:
Well, then I can try to install twrp , and launch DEX to see how it goes
Be right back and let you know
edit :
Flashed TWRP successfully !
No sharing issues , Dex working fine !
Click to expand...
Click to collapse
ok so i am now rooted with stock recovery and everything is working - Dex, sharing etc etc
so i am missing TWRP
please can you go into finer detail into what you then did to install TWRP i need to have as much information as possible - please also confirm if you can mount data and flash files in TWRP if not then there is not really much point in having TWRP installed - i am thinking this is unlikely as you have not disabled forcencryption
I have managed to follow this far
1. Flash odin to stock , NOT using HOME_CSC
2. Do the initial setup (usb debugging and OEM status ( if shown ) checked
3. Flash odin the BL file , and TWRP.tar
4. TWRP , format ( I think nothing happened in this step ), reboot to TWRP , sideload and flash app-debug.zip
5. Reboot to download mode and flash stock recovery , and do the factory reset there ( at this step I tought I woud lose the previously flashed magisk stuff , but that didnt happen, and I got booted & rooted )
I am now rooted with stock recovery - i find it hard to see how we can just install TWRP and use it normally and mount /data without having to at least destroy user data each boot as forcencrypt has NOT been disabled
what is making things far too hard is a process that follows things like this:
"
edit : about the full process...
I ended again in a mess , and did several random stuff (as I got stuck some times in Download mode)
But .. If you ask me what I think that works , it would be like this: "
there are just too many variables - for instance, forceencryption could have been disabled without you realizing when doing the random bits - did you reflash my AP files at any point?
exocetdj said:
ok so i am now rooted with stock recovery and everything is working - Dex, sharing etc etc
so i am missing TWRP
please can you go into finer detail into what you then did to install TWRP i need to have as much information as possible - please also confirm if you can mount data and flash files in TWRP if not then there is not really much point in having TWRP installed - i am thinking this is unlikely as you have not disabled forcencryption
I have managed to follow this far
1. Flash odin to stock , NOT using HOME_CSC
2. Do the initial setup (usb debugging and OEM status ( if shown ) checked
3. Flash odin the BL file , and TWRP.tar
4. TWRP , format ( I think nothing happened in this step ), reboot to TWRP , sideload and flash app-debug.zip
5. Reboot to download mode and flash stock recovery , and do the factory reset there ( at this step I tought I woud lose the previously flashed magisk stuff , but that didnt happen, and I got booted & rooted )
I am now rooted with stock recovery - i find it hard to see how we can just install TWRP and use it normally and mount /data without having to at least destroy user data each boot as forcencrypt has NOT been disabled
what is making things far too hard is a process that follows things like this:
"
edit : about the full process...
I ended again in a mess , and did several random stuff (as I got stuck some times in Download mode)
But .. If you ask me what I think that works , it would be like this: "
there are just too many variables - for instance, forceencryption could have been disabled without you realizing when doing the random bits - did you reflash my AP files at any point?
Click to expand...
Click to collapse
I agree with you about the variables
In short
I was rooted with stock BL6 and twrp
So I flashed to this newest stock , and tried to keep my setup and get rooted again
I flashed HOMECSC and after that gave a shot with newest twrp ( to flash newest app-debug.zip )
I ended with a download mode bootloop
So I used your guide with your files , everything went fine .. except for the sharing and dex issues
This is when the forceencryption could have been disabled , exactly !
Then , I did the steps above , back to 100% stock ( steps above ) , without your AP File this time .
TWRP , is useless at this point , it cant mount data , it is the same behaviour as with BL6 version
Edit : Nice that you could replicate it !
"ok so i am now rooted with stock recovery and everything is working - Dex, sharing etc etc "
pvillasuso said:
I agree with you about the variables
In short
I was rooted with stock BL6 and twrp
So I flashed to this newest stock , and tried to keep my setup and get rooted again
I flashed HOMECSC and after that gave a shot with newest twrp ( to flash newest app-debug.zip )
I ended with a download mode bootloop
So I used your guide with your files , everything went fine .. except for the sharing and dex issues
This is when the forceencryption could have been disabled , exactly !
Then , I did the steps above , back to 100% stock ( steps above ) , without your AP File this time .
TWRP , is useless at this point , it cant mount data , it is the same behaviour as with BL6 version
Click to expand...
Click to collapse
Thanks for the info
looks like using TWRP at a starting point is the only way thats going to be of any use - rooted stock is the way forward!!!
exocetdj said:
Thanks for the info
looks like using TWRP at a starting point is the only way thats going to be of any use - rooted stock is the way forward!!!
Click to expand...
Click to collapse
Sure Bro , no problem