Related
Hi all,
I'm new here and very frustrated , i cant find a solution to the issues i have
mistakenly wiped everything on my kindle fire including firmware ,
i wanted to recover the stock firmware back v6.3.1 , i installed TWRP 2.2.0 and followed the steps properly and carefully
the stock firmware is a zip file that for some reason the device cant see .
when i click on install , all i see folders and sub folders and i cant see the firmware zip where i put which is at root level
why the Kindle fire using TWRP 2.2.0 cant see any zip files , its like the support of it was wiped along with the firmware
is there other way to recover the stock firmware , the problem is that no backups was made too
Please anyone i need help
Update to the latest version of TWRP and follow these directions to revert back to stock...
http://forum.xda-developers.com/showthread.php?t=1638452
If you still can't see the zip archive, USB mount the sdcard onto your computer and see if the file exists there.
Hi,
I need serious help.
I tried to install Vanilla RootBox rom on my Ace 2 NFC (i8160P) CZ.
So i did wipe data, cache, dalvik.
Then i add my Tee folder into rom (tee hack for P version) and i deleted the device model verification from updater-script because it is for non P version.
But when i try to flash the rom via cwm temporary, i stuck at this errors:
cant format unknown volume: /external_sd
cant partition unsafe device: /dev/block/mmcblk0p8
Click to expand...
Click to collapse
But my sdcard is working good (adata microsdhc class10 32GB)
Any solutions?
EDIT: I am using this http://forum.xda-developers.com/showthread.php?t=2389395 patch but not Version 2, but V1 flashed from CWM. This could be the problem. Or not?
EDIT2: I am doing downgrade with repartition to GB an then flash JB... Nicely Done.. but when i try to flash other ROM, still gets the error. OMFG.
EDIT3: So it looks like i need to repartition or do something with mmcblk0p8 partition but what? OMFG, help me please!!!
...
it seem great problem ask from rom creater i thinck they can help you
majid92 said:
it seem great problem ask from rom creater i thinck they can help you
Click to expand...
Click to collapse
Supposedly the mmcblk0p8p partition is the internal storage, named UMS --> Usb Mass Storage
So best check if that reads properly in android (file explorer) and/or when u connect it to your computer.
Seeing as your external SD works good and it complains about that too tho, I don't expect your internal SD to be faulty either.
As for the memory fix you flashed, when u reverted back to GB and then re upgraded to JB, was there a param.lfs.md5 file present in the package (assuming u used odin, u should be able to verify this by opening the tar.md5 in 7zip or winrar)
If yes, then any harm caused by the memory fix will have been undone and that isn't the cause either.
Carpe-Dimi said:
Supposedly the mmcblk0p8p partition is the internal storage, named UMS --> Usb Mass Storage
So best check if that reads properly in android (file explorer) and/or when u connect it to your computer.
Seeing as your external SD works good and it complains about that too tho, I don't expect your internal SD to be faulty either.
As for the memory fix you flashed, when u reverted back to GB and then re upgraded to JB, was there a param.lfs.md5 file present in the package (assuming u used odin, u should be able to verify this by opening the tar.md5 in 7zip or winrar)
If yes, then any harm caused by the memory fix will have been undone and that isn't the cause either.
Click to expand...
Click to collapse
So, yes it is the USB storage, and its working well too. param.lfs.md5 was there. I dont know what to do now.
you are using the temporary CWM tho right? which needs to be flashed via stock recovery? and stock recovery doesn't complain about your mmcblk0p8 partition?
if this is the case, then you can root the stock rom via stock recovery --> http://forum.xda-developers.com/showthread.php?t=2139263
download this kernel for stock rom --> http://forum.xda-developers.com/showthread.php?t=2171054 -extract the zip and place the kernel.bin.md5 file on the root of your internal sdcard
install any terminal emulator, open it and and enter/type su -click accept when prompted for superuser permissions
with that all done enter "dd if=/sdcard/kernel.bin.md5 of=/dev/block/mmcblk0p15" make no typo's on that one, it's lethal.
If done right, it will replace stock kernel with D kernel. which will contain the same version of cwm as in the temporary cwm zip, but with a bit of luck it will not return the error anymore then
if the problem does persist tho, you can also try both touch and regular versions of this kernel -> http://forum.xda-developers.com/showthread.php?t=2424964
extract and rename to kernel.bin.md5, place on internal sd and flash them the same way again via terminal emulator.
there is more hope for this kernel as both versions run different versions of cwm than D-kernel (and eachother), but if this does not solve the problem, you will not be able to boot as that kernel is incompatible with stock rom and you will have to reflash via odin.
Carpe-Dimi said:
you are using the temporary CWM tho right? which needs to be flashed via stock recovery? and stock recovery doesn't complain about your mmcblk0p8 partition?
if this is the case, then you can root the stock rom via stock recovery --> http://forum.xda-developers.com/showthread.php?t=2139263
download this kernel for stock rom --> http://forum.xda-developers.com/showthread.php?t=2171054 -extract the zip and place the kernel.bin.md5 file on the root of your internal sdcard
install any terminal emulator, open it and and enter/type su -click accept when prompted for superuser permissions
with that all done enter "dd if=/sdcard/kernel.bin.md5 of=/dev/block/mmcblk0p15" make no typo's on that one, it's lethal.
If done right, it will replace stock kernel with D kernel. which will contain the same version of cwm as in the temporary cwm zip, but with a bit of luck it will not return the error anymore then
if the problem does persist tho, you can also try both touch and regular versions of this kernel -> http://forum.xda-developers.com/showthread.php?t=2424964
extract and rename to kernel.bin.md5, place on internal sd and flash them the same way again via terminal emulator.
there is more hope for this kernel as both versions run different versions of cwm than D-kernel (and eachother), but if this does not solve the problem, you will not be able to boot as that kernel is incompatible with stock rom and you will have to reflash via odin.
Click to expand...
Click to collapse
Ok, Yes I have rooted stock ROM and temporary CWM, so i am going to try the D-kernel. Hope is compatible with P version.
EDIT:I did the steps, and now, succesfully hardbricked Lol Checksum was ok, command too. OMFG
PC is showing "U8500 USB ROM" in device manager when I connect the USB cable so.. thanks
mybe there is problem that the kernel is build on the me7 or mf1 software.
Guys for everyone who has P version Never flash normal version officiel fw like me7 mf1 via odin on P version of ace 2 it will hardbrick you device that they have to change the motherboard so be carefully
Click to expand...
Click to collapse
EDIT2: LOL i putted battery out for a while and now can go to download mode. But i am at school so now i´ll go home and try odin... AGAIN
EDIT3: I am online again, phone is running well on the stock rooted JB again.. still cannot flash roms, but whatever...
Heya, sorry for the lack of response I've been a lil busy.
I thought that kernel would work on P version as well tho, sorry about that :crying:
Glad to see that you recovered your phone from that atleast.
Last thing i can think of then is to use this kernel --> http://forum.xda-developers.com/showthread.php?t=2072872
It's built for gingerbread, so your phone will again not boot after flashing, but the 8160Pxxlk3 version will for sure be compatible with your phone, and it has yet another version of CWM you might be able to use for flashing
If that doesn't work tho, I really am out of options
gapps-jb-20131011
Hi. I am using Sony Xperia NEO L and managed to upgrade to JB. I followed the steps until i hot a noticed saying that the Installation aborted. What went wrong? Please help! I'm stuck here and cannot going anywhere :crying:
Latest TWRP recovery and root for Lenovo a7000 marshmallow firmware.
Download and unzip TWRP and SP Flash tool on PC.
Copy the SuperSU.-v71zip in your phone which you will find in the TWRP .zip file.
Run SP flash tool and In the menu Option tab, go to Download, and put a tick in the DA DL All with Checksum".
choose scatter in the TWRP folder and then select "Download only" and click download.
Now power off the phone and connect the USB cable.
The process will start and after completion, a box will appear with done written on it.
Then Boot into recovery (Power + half a second the two volume buttons).
Now you are on TWRP RECOVERY.
For Rooting: Now select install zip and then navigate to SuperSU-v2.71.zip
reboot.
Download TWRP Recovery 3.0.2-1:click here
Download Latest SP Flash Tool: click here
NOTE: IF YOU ARE USING THIS FOR CUSTOM ROM THEN UNTICK THE BOOT.img IN SPFLASH TOOL WHILE FLASHING THE TWRP OTHERWISE YOUR DEVICE COULD BE IN BOOT LOOP STATE. (FLASH STOCK ROM TO FIX)
FOR STOCK ROM NO NEED TO UNCHECK
Yeah! ☺ Will be trying it later. Thanks for the link.
What about 'CWM Recovery' ?
If one succeeds with this TWRP and rooting, then I think one can change TWRP to CWM using flashify or Rashr, provided he/she should confirm that the 'CWM Recovery' will work on Lenovo A 7000 a with android 6.0 OS. But I do not know if the 'CWM' recovery thatwas used earlier when we were on android 5.0, will still work with android 6.0 or not. Can anybody confirm?
this is working men thanks:angel:
Like a charm
Sent from my Lenovo A7000-a using XDA-Developers mobile app
Lenovo A7000 Marshmallow STOCK FIRMWARE
Flash via spflash tool
http://forum.xda-developers.com/android/development/lenovo-a7000-as223160405-row-andoid-6-0-t3360467/post66404777#post66404777
Does backup and restore works on this twrp?
milankumarn said:
Does backup and restore works on this twrp?
Click to expand...
Click to collapse
Yes it support backup and restore.
Worked for me. Thanks a lot!
I have a big problem ...
Few days ago My phone give me option to update to android 6.0 .(Lenovo a7000)
Downloading update package and press update.
When i press update ,phone is immediatly reboot to twrp and thats it .... That all
Nothing happening... rebooting phone and then get message ,update failing and update package automaticaly erased from phone.
Is anything i doing wrong ?
Thanks ,
Regards from Slovenia
Flashed the recovery as instructed, but when I boot into recovery and select Install, Supersu. Zip does not show up even though it is on the phone.
Please help
chabot said:
I have a big problem ...
Few days ago My phone give me option to update to android 6.0 .(Lenovo a7000)
Downloading update package and press update.
When i press update ,phone is immediatly reboot to twrp and thats it .... That all
Nothing happening... rebooting phone and then get message ,update failing and update package automaticaly erased from phone.
Is anything i doing wrong ?
Thanks ,
Regards from Slovenia
Click to expand...
Click to collapse
Use the stock rom found here to go back to factory settings using the stock marshmallow rom. Make sure that you flash using SP Flash Tool as instructed in the link. This will replace TWRP with stock recovery.
Afterwards, you can reinstall TWRP and root,etc.
Sent from my Lenovo K50-t5 using XDA-Developers mobile app
after flashing and rooting i format my sdcard as internal and i notice that no zip/img file appear on twrp. has anyone encounter the same problem?
Unable to Root!
Flashed the recovery as instructed, but when I boot into recovery and select Install, Supersu. Zip does not show up even though it is on the phone. It shows the folder but not as a Zip file.
Please help
dan_daniel04 said:
Flashed the recovery as instructed, but when I boot into recovery and select Install, Supersu. Zip does not show up even though it is on the phone. It shows the folder but not as a Zip file.
Please help
Click to expand...
Click to collapse
I think you have place the supersu zip in external and locating in internal.
I have tested the recovery and it's working fine
Thanks :good::good::good::good:
Hello any way to root without flashing twrp?
PB1974 said:
Flashed the recovery as instructed, but when I boot into recovery and select Install, Supersu. Zip does not show up even though it is on the phone.
Please help
Click to expand...
Click to collapse
I think you have copied the SuperSU-v71.zip in external storage and in TWRP you are searching in internal storage.If it is so the paste it in internal or change storage selection at the time of installing zip.
And paste the zip in root of the storage not in any folder.
As i can see this is your 1st post.
I think this will help you.
Mounting issue with TWRP
After switching sdcard as internal storage. The file manager only shows the ext. Sdcard so from where we can access the internal Sdcard to put that Supersu.zip.And the TWRP only mount only internal Sdcard. Not able to mount ext. Sdcard plz. Help!
Hey can i flash this supersu.zip via twrp 3.02-1?
Couple hours ago i flashed supersu.zip from lenovo a7000 indonesia group, and all i got was bootloop. Is it possible that with this supersu i could get another bootloop? Thanks
I am having a problem it happened after I finally got to flash latest CosmicOS and set up a new password on my OP3. So, here’s what basically happened;
Once I got it up and running I noticed that home button and fingerprint sensor was completely disabled, then I tried to set up a new password (completely same password I used to decrypt my storage in TWRP 3.0.2-0) and fingerprint just in case but it didn’t react to me calibrating the fingerprint so I was like, ”alright, gladly I got a backup in TWRP”.
Once I rebooted to recovery it asked for a password as usually, once I typed that exact same password as before it just said wrong password, I tried it twice in case if I made a typo but still invalid password. And then I was panicing and pressed cancel and just rebooted back to OS.
I then removed all passwords there and booted back to recovery again, TWRP doesn’t ask for a password anymore but there’s a slider which says allow modifications or something similar and also there’s read only mode. When I slided the modification thing it just doesn’t show any of my files in sdcard folder when I go to ’Install’ tab but (0mb) instead. I even was able to browse and add files from my pc while phone was plugged in and in recovery mode, not anymore though.
Can anyone give me advice or help to get my oneplus 3 back in use? I have all the important files moved to my pc so I don’t mind losing files I have left in internal storage that much. Not if it’s necessary or easier workaround. thanks for reading this long-ass text :fingers-crossed:
EDIT: Issue SOLVED thanks to @AkR2014. I switched data partition from EXT4 to F2FS and then one more time back to EXT4 in TWRP's Wipe tab. (I was using latest blue_spark's TWRP-3.2.1-x version) and I was able to wipe data, system and both caches afterwards. After that I managed to flash new rom via USB-C to A with mounted USB flash drive on the other end and you know rest of the story. Do note that it WILL clear your internal storage so back up all the necessary files you need. And if you want to stay on F2FS data partition be sure to flash a ROM which supports it
EDIT2: There might be another way to mount your storage in TWRP but this is probably fail-proof method and worked for me
Oh and I couldn’t flash the Gapps in recovery after flashing the CosmicOs and nor I can’t now because of this haha. I can use my email though and send files through it from my another email if that helps
Vaahtopahvi said:
Oh and I couldn’t flash the Gapps in recovery after flashing the CosmicOs and nor I can’t now because of this haha. I can use my email though and send files through it from my another email if that helps
Click to expand...
Click to collapse
Try eng.stk's TWRP and clean flash ROM and Gapps.
tnsmani said:
Try eng.stk's TWRP and clean flash ROM and Gapps.
Click to expand...
Click to collapse
I couldnt find link for eng.stk TWRP, only people talking of it it. and what am I supposed to do with it once I get if you could explain? sorry for nooby questions
tnsmani said:
Try eng.stk's TWRP and clean flash ROM and Gapps.
Click to expand...
Click to collapse
Wait, I think I found it. But the question is can and do I need to update the latest eng.stk’s TWRP through fastboot? And if so, is there instructions topic somewhere?
So here's the latest update: I flashed twrp-3.1.1-2 via fastboot but once I go to recovery it still doesn't let me browse files in /sdcard and if I put new password in OS it doesn't match in TWRP. I have a OS where I can boot to but no Gapps installed.
People say formatting data in TWRP would work, I'm just scared if that doesn't work and won't let me boot to OS anymore (even though I have a TWRP back up which I made before wiping my OxygenOS system data and caches in my pc as well in my phone's storage atm) and I can't flash anything in recovery mode, is there anything I could do? I'm in desperate need of help right now.
In this CosmicOS i am using Android 8.1.0 and I'm afraid something isn't supporting it or so.
Vaahtopahvi said:
So here's the latest update: I flashed twrp-3.1.1-2 via fastboot but once I go to recovery it still doesn't let me browse files in /sdcard and if I put new password in OS it doesn't match in TWRP. I have a OS where I can boot to but no Gapps installed.
People say formatting data in TWRP would work, I'm just scared if that doesn't work and won't let me boot to OS anymore (even though I have a TWRP back up which I made before wiping my OxygenOS system data and caches in my pc as well in my phone's storage atm) and I can't flash anything in recovery mode, is there anything I could do? I'm in desperate need of help right now.
In this CosmicOS i am using Android 8.1.0 and I'm afraid something isn't supporting it or so.
Click to expand...
Click to collapse
As I said, flash eng.stk's TWRP. Simply flash the image to Recovery partition using the TWRP you already have. After that, wipe everything and clean flash the ROM. If anything goes wrong, you can use the Mega Unbrick guide method 2.
Here's the link to TWRP: https://forum.xda-developers.com/devdb/project/?id=15934#downloads
tnsmani said:
As I said, flash eng.stk's TWRP. Simply flash the image to Recovery partition using the TWRP you already have. After that, wipe everything and clean flash the ROM. If anything goes wrong, you can use the Mega Unbrick guide method 2.
Here's the link to TWRP: https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Click to expand...
Click to collapse
Thanks for the reply and link. I understood most of the parts except flashing the image to Recovery partition. Am I supposed to find the eng.stk’s TWRP from my Install tab in my current TWRP? Because it doesn’t show any files there. Also do I download the latest 3.2.1-x TWRP from the link you provided?
Vaahtopahvi said:
Thanks for the reply and link. I understood most of the parts except flashing the image to Recovery partition. Am I supposed to find the eng.stk’s TWRP from my Install tab in my current TWRP? Because it doesn’t show any files there. Also do I download the latest 3.2.1-x TWRP from the link you provided?
Click to expand...
Click to collapse
You will find TWRP 3.2.1-x v8.61 in the link I provided. Download that to your phone and save it. Restart your phone in recovery mode and in the current TWRP that you have, click the 'Install' button. By default, you will be shown zip files,if any. TWRP comes as an img file. So click the 'show img files' button at bottom right in TWRP and navigate to where you saved it and select it. Slide the bottom bar to install, you will be asked where to install it to. Select 'Recovery' and again slide the bar. It will be installed. To confirm, restart in recovery mode and check the version number of TWRP.
eng.stk's TWRP is compatible with OOS and custom ROMS. The offficial one doesn't work with some custom ROMs.
tnsmani said:
You will find TWRP 3.2.1-x v8.61 in the link I provided. Download that to your phone and save it. Restart your phone in recovery mode and in the current TWRP that you have, click the 'Install' button. By default, you will be shown zip files,if any. TWRP comes as an img file. So click the 'show img files' button at bottom right in TWRP and navigate to where you saved it and select it. Slide the bottom bar to install, you will be asked where to install it to. Select 'Recovery' and again slide the bar. It will be installed. To confirm, restart in recovery mode and check the version number of TWRP.
eng.stk's TWRP is compatible with OOS and custom ROMS. The offficial one doesn't work with some custom ROMs.
Click to expand...
Click to collapse
he is unable to mount storage via twrp , i have the sol but it will format your whole data / internal storage if your wiling to .
1 ) Go to twrp
2 ) wipe - > Advance wipe > change system file partation
3) if your on F2FS change to ext 4 or vice versa .
4 ) you will be able to mount sdcard
and dont flash this rom again , faceed same issue while flashing some oreo rom .
P.S : do it at your own risk .
AkR2014 said:
he is unable to mount storage via twrp , i have the sol but it will format your whole data / internal storage if your wiling to .
1 ) Go to twrp
2 ) wipe - > Advance wipe > change system file partation
3) if your on F2FS change to ext 4 or vice versa .
4 ) you will be able to mount sdcard
and dont flash this rom again , faceed same issue while flashing some oreo rom .
P.S : do it at your own risk .
Click to expand...
Click to collapse
Thanks man :highfive: I have really nothing to lose anyways so I gotta try that lol. How can I know whether I am on F2FS or EXT 4 though? And once it’s done can I access to my phone storage while it’s in recovery mode and just paste new rom to internal storage? Or do I need to push the rom via adb while in fastboot mode? Thinking to try out Paranoid rom which is based on Nougat, right?
tnsmani said:
You will find TWRP 3.2.1-x v8.61 in the link I provided. Download that to your phone and save it. Restart your phone in recovery mode and in the current TWRP that you have, click the 'Install' button. By default, you will be shown zip files,if any. TWRP comes as an img file. So click the 'show img files' button at bottom right in TWRP and navigate to where you saved it and select it. Slide the bottom bar to install, you will be asked where to install it to. Select 'Recovery' and again slide the bar. It will be installed. To confirm, restart in recovery mode and check the version number of TWRP.
eng.stk's TWRP is compatible with OOS and custom ROMS. The offficial one doesn't work with some custom ROMs.
Click to expand...
Click to collapse
Thanks for clarification tnsmani, appreciate the time you put into it. But as the person who replied to your text, I cannot mount the storage in TWRP which would prevent me of flashing pretty much anything on phone in TWRP.
Vaahtopahvi said:
Thanks man :highfive: I have really nothing to lose anyways so I gotta try that lol. How can I know whether I am on F2FS or EXT 4 though? And once it’s done can I access to my phone storage while it’s in recovery mode and just paste new rom to internal storage? Or do I need to push the rom via adb while in fastboot mode? Thinking to try out Paranoid rom which is based on Nougat, right?
Click to expand...
Click to collapse
yap you will be able to access your internal storage as well flash any thing you want from internal storage , no need to push via adb , use deskinfo app from playstore to check
the format of your data partition. yah try Omni 8.1.0 really awsome rom i am currently using. :laugh:
Vaahtopahvi said:
Thanks for clarification tnsmani, appreciate the time you put into it. But as the person who replied to your text, I cannot mount the storage in TWRP which would prevent me of flashing pretty much anything on phone in TWRP.
Click to expand...
Click to collapse
If you are able to boot into fastboot mode, you can install TWRP through ADB.
But you can not copy, paste in TWRP.
AkR2014 said:
yap you will be able to access your internal storage as well flash any thing you want from internal storage , no need to push via adb , use deskinfo app from playstore to check
the format of your data partition. yah try Omni 8.1.0 really awsome rom i am currently using. :laugh:
Click to expand...
Click to collapse
Great to hear that. Though I don’t have Gapps installed. Accidentally tried to flash the wrong one before the mounting problem occurred and now you know rest of the story :laugh:
I’ll try to find another way to check it though. Oh and as well as the ROM
Test version of custom Team Win Recovery Project version 3.5.2_11.0 for OnePlus Nord N100 (Android 11 Only).
Everything works, except for:
MTP, .img firmware (for this you need to flash the full super.img image) and decryption of the Data section.
If anyone can modify this version of the recovery, we are very grateful to the future.
In the meantime, whoever wants to test or try it out, an image will be attached to the post. You can both boot (fastboot boot twrp.img) and flash (fastboot flash recovery_a twrp.img and fastboot flash recovery_b twrp.img).
I ask you to answer about all the problems found and write either to me personally or in this topic.
Is there any newer version of this? i find this one freezes the phone a lot. thanks
I ran this TWRP for the OnePlus N100 in fastboot and it worked but I can't see any files. I've installed Android 11.
I'm trying to install Magisk zip but in TWRP I only see the folder tree and no files.
Do I need to install TWRP and not just run it from fastboot?
If I need to install it do I pick slot a or b or both?
Thanks for any help.
onlycash said:
I ran this TWRP for the OnePlus N100 in fastboot and it worked but I can't see any files. I've installed Android 11.
I'm trying to install Magisk zip but in TWRP I only see the folder tree and no files.
Do I need to install TWRP and not just run it from fastboot?
If I need to install it do I pick slot a or b or both?
Thanks for any help.
Click to expand...
Click to collapse
do not install it. I installed it and it bricked my device. I needed to flash the stock recovery.
Halphix said:
do not install it. I installed it and it bricked my device. I needed to flash the stock recovery.
Click to expand...
Click to collapse
It installed fine on my BE2013. Not extremely useful without the missing features though.
thomaskmaagaard said:
It installed fine on my BE2013. Not extremely useful without the missing features though.
Click to expand...
Click to collapse
Can you install Magisk zip with this TWRP on your BE2013?
.
onlycash said:
Can you install Magisk zip with this TWRP on your BE2013?
Click to expand...
Click to collapse
Honestly I haven't even tried flashing anything because I already have magisk and i had some issues with safety net that I didn't want to risk having to fix again.
thomaskmaagaard said:
Honestly I haven't even tried flashing anything because I already have magisk and i had some issues with safety net that I didn't want to risk having to fix again.
Click to expand...
Click to collapse
How did you install the Magisk zip file?
.
onlycash said:
How did you install the Magisk zip file?
Click to expand...
Click to collapse
I didn't. I patched firmware boot image and flashed through bootloader. However I just tried flashing from TWRP.
I put the zip on external SD because this version doesn't support decryption of data partition. I then entered the "mount" menu in TWRP and mounted external SD and then tapped "select storage" and selected external SD.
You should be able to flash it now. It didn't give any errors, but i didn't uninstall magisk first so don't know how well it actually worked.
I also don't know if you can do anything without external SD or without root access already.
thomaskmaagaard said:
I didn't. I patched firmware boot image and flashed through bootloader. However I just tried flashing from TWRP.
I put the zip on external SD because this version doesn't support decryption of data partition. I then entered the "mount" menu in TWRP and mounted external SD and then tapped "select storage" and selected external SD.
You should be able to flash it now. It didn't give any errors, but i didn't uninstall magisk first so don't know how well it actually worked.
I also don't know if you can do anything without external SD or without root access already.
Click to expand...
Click to collapse
Thanks.
That's very interesting...
You've given me a few good ideas.
I'll report back and let you know if it worked.
.
onlycash said:
Thanks.
That's very interesting...
You've given me a few good ideas.
I'll report back and let you know if it worked.
.
Click to expand...
Click to collapse
If you go with the boot image method I wouldn't mind helping you out.
thomaskmaagaard said:
I didn't. I patched firmware boot image and flashed through bootloader. However I just tried flashing from TWRP.
I put the zip on external SD because this version doesn't support decryption of data partition. I then entered the "mount" menu in TWRP and mounted external SD and then tapped "select storage" and selected external SD.
You should be able to flash it now. It didn't give any errors, but i didn't uninstall magisk first so don't know how well it actually worked.
I also don't know if you can do anything without external SD or without root access already.
Click to expand...
Click to collapse
I had high hopes...
I fastbooted the TWRP, I didn't install it but I don't think that would make a difference.
I put the Magisk zip on the external SD card and from within TWRP I had no problem mounting the SD card but I still couldn't see any files, just a folder tree, and every folder empty.
When you run TWRP and mount the SD card can you see the files within the folders on the card?
.
onlycash said:
When you run TWRP and mount the SD card can you see the files within the folders on the card?
Click to expand...
Click to collapse
Yes. It is important that you tap "select storage" and select "micro sd". After i did that i entered "flash" and immediately saw folders and zips on my external sd. In file manager i could see all files and even deleted some from there.
From root directory it's in /external_sd not in /storage.
Edit: Even though i also don't think installing TWRP makes a difference, i don't know if that's the case.
I should mention i used "fastboot flash recovery xxx.img" not "... recovery_a" or "... recovery_b".
I don't know if this changes something with access
Honestly patching boot image is probably less of a headache. I can even send the images pre-patched if you want. Just one fastboot command
I'd need to know your phone variant and update version.
thomaskmaagaard said:
Honestly patching boot image is probably less of a headache. I can even send the images pre-patched if you want. Just one fastboot command
I'd need to know your phone variant and update version.
Click to expand...
Click to collapse
Well, I don't think you have the file I need.
My N100 is a model BE2015, build number 11.0.1BE82CF
I just fastbooted TWRP again and I'm mounting and selecting external_sd but still zero files.
If I flash the TWRP with "fastboot flash recovery xxx.img" is there a way to reverse it if I ever need to?
Again thanks for the help.
.
onlycash said:
My N100 is a model BE2015, build number 11.0.1BE82CF
Click to expand...
Click to collapse
Well that might be the problem. That's a carrier locked phone, right? I'm not really familiar with those. I just know they are complicated to mod.
Not sure if you'll even be able to flash recovery and I'm surprised you can fastboot boot. But in theory, (at least on unlocked phones) if you can flash TWRP, you can flash stock recovery from firmware package.
I saw a quite extensive and fairly complicated guide to fully unlock a carrier phone here on XDA, but don't know how well it works or if you have followed any of these steps.
Edit: Also found this, looks like it works with your device: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4245499/
thomaskmaagaard said:
Well that might be the problem. That's a carrier locked phone, right? I'm not really familiar with those. I just know they are complicated to mod.
Not sure if you'll even be able to flash recovery and I'm surprised you can fastboot boot. But in theory, (at least on unlocked phones) if you can flash TWRP, you can flash stock recovery from firmware package.
I saw a quite extensive and fairly complicated guide to fully unlock a carrier phone here on XDA, but don't know how well it works or if you have followed any of these steps.
Edit: Also found this, looks like it works with your device: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4245499/
Click to expand...
Click to collapse
Let me start by saying my phone is both SIM unlocked and bootloader unlocked.
The post you linked is talking about the same phone as me but the last post in that thread has an ominous post from someone on Android 11 bricking after trying that. I'm not sure if that works if you're already on 11.
I still can't understand why the TWRP can't see files on my SD card. I think the two missing elements are the fact that you have TWRP flashed to your phone and you're rooted already.
I really can't understand why being rooted would have anything to do with TWRP seeing the files on the SD card so I'm leaning toward it being flashed that's the difference.
I would like to try flashing TWRP but I'm still unsure how, plus I'm guessing I have no recovery if that goes awry.
If I could just get the zip fashed it should patch my boot.img and give me root fairly easily.
Does anyone have any suggestions as to ways back if the TWRP flash goes bad plus just what command do I use to flash it and what happens to the other slot?
.
Okay, so...
I have now tried flashing stock boot and stock recovery on both a and b, verified no root access, then trying "boot twrp.img"
Still able to see files on micro sd.
I then attempted to flash magisk zip to verify this method working.
Didn't seem to work at first, but i think this was due to me messing something up with active slot. Fastbooted into twrp again and flashed magisk again and it works.
So, in short; This absolutely works on a BE2013, but this recovery might not play well with your BE2015.
OP asks about potential problems so maybe you'll have luck messaging him and you could investigate together? Just a suggestion.
I'm sorry, but I really don't know how to help with that model. It's problematic that there's no firmware payload available. If you find one or if you can somehow dump the boot image from the phone then I'd be optimistic and happy to help any way I can.
onlycash said:
How did you install the Magisk zip file?
.
Click to expand...
Click to collapse
I have the BE2011 model. Useful on this variant?