Related
When I open up superSU, it says:
There is no SU binary installed, and super SU cannot install it.
If you just upgraded to android 4.3, you need to manually re-root.
If I turn the Nexus on in recovery mode, it still says it's unlocked.
So at this point, is there anything I can do to restore root status without factory resetting? I made a backup with titanium backup but it was a while ago so I would rather not use it if there is another way.
I've read somewhere that rooting it should mean OTA updates should no longer work but somehow, it still went through and I updated it without thinking too much.
Download the supersu zip file and flash it in recovery.
http://download.chainfire.eu/371/SuperSU/UPDATE-SuperSU-v1.85.zip
This will throw me back into rooted mode while keeping my phone as is?
BruceHsiang said:
This will throw me back into rooted mode while keeping my phone as is?
Click to expand...
Click to collapse
this will update the binaries and restore root. no data will be lost or formatted. simply flash the zip in twrp or cwm.
xBeerdroiDx said:
this will update the binaries and restore root. no data will be lost or formatted. simply flash the zip in twrp or cwm.
Click to expand...
Click to collapse
I don't have twrp or cwm installed yet. Which one is generally simpler/easier to install/use?
So I installed goomanager and tried to install twrp, but it all goes back to the same problem which was that I am now not in root mode anymore.
Also what do you mean by flashing the zip? Which options am I supposed to use?
BruceHsiang said:
I don't have twrp or cwm installed yet. Which one is generally simpler/easier to install/use?
Click to expand...
Click to collapse
I've been using TWRP with no problem and it's been awhile since I've used CWM. I've never used a toolkit or flashify but with adb it would probably take a couple minutes max to flash either one.
---------- Post added at 10:49 PM ---------- Previous post was at 10:46 PM ----------
BruceHsiang said:
So I installed goomanager and tried to install twrp, but it all goes back to the same problem which was that I am now not in root mode anymore.
Also what do you mean by flashing the zip? Which options am I supposed to use?
Click to expand...
Click to collapse
Choose "Install" in recovery, with either TWRP or CWM is flashing the zip.
wantabe said:
I've been using TWRP with no problem and it's been awhile since I've used CWM. I've never used a toolkit or flashify but with adb it would probably take a couple minutes max to flash either one.
---------- Post added at 10:49 PM ---------- Previous post was at 10:46 PM ----------
Choose "Install" in recovery, with either TWRP or CWM is flashing the zip.
Click to expand...
Click to collapse
Problem is, I didn't install twrp when I had root access before, and now when I try to use it, it says I need root to use it.
Can I flash the zip using adb in the fastboot recovery menu?
What should I do from here?
BruceHsiang said:
Problem is, I didn't install twrp when I had root access before, and now when I try to use it, it says I need root to use it.
Can I flash the zip using adb in the fastboot recovery menu?
What should I do from here?
Click to expand...
Click to collapse
Sorry I've never done that. I guess you could adb push superuser.apk to the system but you still need the binary wherever that goes. Honestly I would just flash TWRP using adb and use TWRP to flash the SuperSu zip.
---------- Post added at 11:11 PM ---------- Previous post was at 11:10 PM ----------
Do you have adb already working?
Not yet, I just saw it as an option while reading around.
How would I install twrp with that image file?
All tutorials I've found said I needed root to install it in the first place.
BruceHsiang said:
Not yet, I just saw it as an option while reading around.
How would I install twrp with that image file?
All tutorials I've found said I needed root to install it in the first place.
Click to expand...
Click to collapse
No.You do not need root to install a custom recovery. You need an unlocked bootloader. How did you get root in the first place? You must have used a toolkit of some kind? Use it again? I've only every used adb so I can't help with any toolkits but lots of people use them, I guess!
Download the latest TWRP or CWM recovery. Put it in the same folder as your adb and fastboot files. Open a command prompt and type adb reboot bootloader(you have to make sure developer settings are enabled and USB debugging is checked). Then flash recovery using fastboot by typing fastboot flash recovery name_of_file.img and then you can flash the supersu zip file.
Sent from my Nexus 5 using Tapatalk
Exactly! I'm thinking he doesn't have adb setup yet.
---------- Post added at 11:36 PM ---------- Previous post was at 11:28 PM ----------
This is a pretty decent video on how to setup adb, not the newest video out there probably but it should work!
I used chainfires autocf root file from here
http://forum.xda-developers.com/showthread.php?t=2507211
and followed a youtube tutorial.
When I try adb devices it shows my serial number followed by sideload.
I've tried sideloading both twrp and the superSU.zip, and they fail to verify and the installation aborts =\
So I have TWRP installed on my rooted Galaxy S3 (I535), and the 4.3 update just came out and was available to me.
I downloaded it, and tried to install it (I know that it will remove root), and when it finished downloading, it opened the TWRP boot menu.
Does anyone else who uses TWRP know how to install the new update? I couldn't find it and it wouldn't automatically install....
Carousser said:
So I have TWRP installed on my rooted Galaxy S3 (I535), and the 4.3 update just came out and was available to me.
I downloaded it, and tried to install it (I know that it will remove root), and when it finished downloading, it opened the TWRP boot menu.
Does anyone else who uses TWRP know how to install the new update? I couldn't find it and it wouldn't automatically install....
Click to expand...
Click to collapse
If your OK with the locked bootloder (no more twrp) that comes with 4.3 flash the Odin file. If you want to ota there are links some place on this forum to flash stock recovery
ThePagel said:
If your OK with the locked bootloder (no more twrp) that comes with 4.3 flash the Odin file. If you want to ota there are links some place on this forum to flash stock recovery
Click to expand...
Click to collapse
Well I don't plan on using a custom ROM, I was using just the stock ROM + root. How do I do this?
Carousser said:
Well I don't plan on using a custom ROM, I was using just the stock ROM + root. How do I do this?
Click to expand...
Click to collapse
What way do you want to go Odin firmware will wipe internal sd card but it will be a nice clean install. Or ota after the stock recovery has been flashed through Odin but you might have weird bugs with ota... Might
ThePagel said:
What way do you want to go Odin firmware will wipe internal sd card but it will be a nice clean install. Or ota after the stock recovery has been flashed through Odin but you might have weird bugs with ota... Might
Click to expand...
Click to collapse
I'd rather not wipe the internal SD card.. Isn't there just a way to install the update without all the hassle? I don't remember doing all this for rooting it... I'm fine with losing the root upon installing the new update as I can just root it again with safe root
Carousser said:
I'd rather not wipe the internal SD card.. Isn't there just a way to install the update without all the hassle? I don't remember doing all this for rooting it... I'm fine with losing the root upon installing the new update as I can just root it again with safe root
Click to expand...
Click to collapse
Find the. Stock recovery download it and flash through Odin. there are ways to do it through terminal but odin is the fastest to explain. After that you should beable to ota and keep your setup as is. It is odd that you cant ota I had twrp when i took the ota.
ThePagel said:
Find the. Stock recovery download it and flash through Odin. there are ways to do it through terminal but odin is the fastest to explain. After that you should beable to ota and keep your setup as is. It is odd that you cant ota I had twrp when i took the ota.
Click to expand...
Click to collapse
Well it just directs me to TWRP, and I have no idea where to go from there. I don't care about ever having TWRP again and I don't care about having a locked bootstrap, as I only need stock with root.
Never mind I was on stock recovery I forgot I was recovering from a soft brick when I decided to give it a shot.
---------- Post added at 03:26 PM ---------- Previous post was at 03:24 PM ----------
Carousser said:
Well it just directs me to TWRP, and I have no idea where to go from there. I don't care about ever having TWRP again and I don't care about having a locked bootstrap, as I only need stock with root.
Click to expand...
Click to collapse
Oh your stuck on twrp can't boot up to usable state?
ThePagel said:
Never mind I was on stock recovery I forgot I was recovering from a soft brick when I decided to give it a shot.
---------- Post added at 03:26 PM ---------- Previous post was at 03:24 PM ----------
Oh your stuck on twrp can't boot up to usable state?
Click to expand...
Click to collapse
It goes to a screen with options such as Install, Wipe, Backup, Restore, etc....
I don't know where the ota is downloaded and thus cannot install it
Carousser said:
It goes to a screen with options such as Install, Wipe, Backup, Restore, etc....
I don't know where the ota is downloaded and thus cannot install it
Click to expand...
Click to collapse
You kind of only have 2 options now. Attempt a "dirty" flash of a ROM so you can save your internal SD files then odin or do the full Odin wipe and forget about keeping the files. Either way unless anyone else has a idea you lose your current setup.
---------- Post added at 03:37 PM ---------- Previous post was at 03:33 PM ----------
I forgot the obvious. If you made a backup in twrp you can just recover with that.
ThePagel said:
You kind of only have 2 options now. Attempt a "dirty" flash of a ROM so you can save your internal SD files then odin or do the full Odin wipe and forget about keeping the files. Either way unless anyone else has a idea you lose your current setup.
---------- Post added at 03:37 PM ---------- Previous post was at 03:33 PM ----------
I forgot the obvious. If you made a backup in twrp you can just recover with that.
Click to expand...
Click to collapse
So let me get this straight.
There's no way for me to install the update unless I flash to another ROM? I don't see why I can;t just update and lose odin and TWRP or whatever
Edit-----
I found the zip file while browsing TWRP. Can I just install it?
Carousser said:
So let me get this straight.
There's no way for me to install the update unless I flash to another ROM? I don't see why I can;t just update and lose odin and TWRP or whatever
Click to expand...
Click to collapse
OK I'll explain what I think went bad.when you downloaded the update it was expecting factory stock recovery to finish the install. Since you had twrp it failed. FYI Odin is a program on the PC to communicate with the phone in download mode (Odin mode). try to do a factory reset before you go crazy with my other suggestions. I have a feeling one of the 3 options I gave you are your only options.
ThePagel said:
OK I'll explain what I think went bad.when you downloaded the update it was expecting factory stock recovery to finish the install. Since you had twrp it failed. FYI Odin is a program on the PC to communicate with the phone in download mode (Odin mode). try to do a factory reset before you go crazy with my other suggestions. I have a feeling one of thoughs 3 options are your only options.
Click to expand...
Click to collapse
I found the zip file while browsing TWRP. Can I just install it? It said it was a flash and that it may be incompatible
Carousser said:
I found the zip file while browsing TWRP. Can I just install it? It said it was a flash and that it may be incompatible
Click to expand...
Click to collapse
Sure you can try tell me if it works
ThePagel said:
Sure you can try tell me if it works
Click to expand...
Click to collapse
Is there a chance of me bricking my phone?
Carousser said:
Is there a chance of me bricking my phone?
Click to expand...
Click to collapse
Yeah but you already soft bricked it. Any brick you do you should be able to fix. just so you know you backed yourself into a corner. No matter what you do you have a chance of bricking. Its all part of being a power user. If your uncomfortable with that after you are on 4.3 you might not want to root.
ThePagel said:
Yeah but you already soft bricked it. Any brick you do you should be able to fix. just so you know you backed yourself into a corner. No matter what you do you have a chance of bricking. Its all part of being a power user. If your uncomfortable with that after you are on 4.3 you might not want to root.
Click to expand...
Click to collapse
Yeah I know there's always the chance of bricking, just wanted to know if that specific thing would do it. I've been into rooting since my Droid 1, Droid 2, and Droid X. But I'm always cautious.
If I do a factory reset and back up all my data, will it get rid of odin and TWRP and everything? Then just install the 4.3 update and root using safe root? Would that work?
Carousser said:
Yeah I know there's always the chance of bricking, just wanted to know if that specific thing would do it. I've been into rooting since my Droid 1, Droid 2, and Droid X. But I'm always cautious.
If I do a factory reset and back up all my data, will it get rid of odin and TWRP and everything? Then just install the 4.3 update and root using safe root? Would that work?
Click to expand...
Click to collapse
You would need to flash stock recovery completely replacing twrp. so if factory reset works and you can boot you should beable to flash stock recovery then redo the ota.
---------- Post added at 05:37 PM ---------- Previous post was at 05:34 PM ----------
If you have backups of stuff on your internal sd it would be much faster to just Odin to 4.3 right now.
ThePagel said:
You would need to flash stock recovery completely replacing twrp. so if factory reset works and you can boot you should beable to flash stock recovery then redo the ota.
Click to expand...
Click to collapse
Is there a chance that doing a factory reset wouldn't flash it back? What else would I have to do? Sorry I haven't dealt with flashing since i had my droid x
Carousser said:
Is there a chance that doing a factory reset wouldn't flash it back? What else would I have to do? Sorry I haven't dealt with flashing since i had my droid x
Click to expand...
Click to collapse
Factory reset deals with the rom. So no it will stay twrp.
---------- Post added at 05:45 PM ---------- Previous post was at 05:40 PM ----------
Using Odin is a lot like SBF'ing on the droid x (that was my last phone also). So if you can remember installing cyanogen mod 6 or 7 you probably always did a factory reset before first boot. Custom recovery stays intact the only way to get rid of it was to flash stock recovery with terminal emulator or sbf back to pure stock. Luckily Odin let's us flash the recover by its self so we have more options with Samsung.
Heya. I restored a full backup in TWRP, and I ended up bootlooping. I tried flashing stock firmware, and nothing has changed. I can access downloading mode, and I can flash TWRP and boot into that. Any help? I've tried everything I've came.
I used flashify to get twrp into recovery but it recovery looped and the only way i got out of it was to reflash root with odin. Hope that helps.
Is your device still rooted? I was getting set warranty bit: recovery. It just kept going back to twrp.
Sent from my SM-J700P using Tapatalk
Synz86 said:
I used flashify to get twrp into recovery but it recovery looped and the only way i got out of it was to reflash root with odin. Hope that helps.
Is your device still rooted? I was getting set warranty bit: recovery. It just kept going back to twrp.
Sent from my SM-J700P using Tapatalk
Click to expand...
Click to collapse
I'll try reflashing the root thing. Thanks.
EDIT: Does not work.
No problem, good luck. Let me know if it works, took me a couple times.
Sent from my SM-J700P using Tapatalk
I personally just had to reflash stock boot.img in odin when i got my bootloop and all was well
where can i download the stockl firmware for the boost mobile variant. I am in a bootloop here and have tried everything . I need the stock firmware so i can flash it via odin.
Having the same problem!
I rooted, flashed twrp, and Xposed successfully and made a complete backup. I got a little excessive with my debloating, so I tried to restore my nandroid backup with twrp.. Been bootlooped ever since. I tried flashing the stock boot, recovery, and rom with odin. Nothing works. The best result I can get is when I use Odin to flash stock firmware, then flash the chainfire autoroot. If I do that, it still bootloops, but it gets all the way to the "optimizing apps" screen... If I don't flash the autoroot, it loops after the virgin mobile logo. If I try to use stock rom, cf autoroot, and twrp, it goes all crazy at the initial Samsung screen and won't even loop. I've tried every combination I can think of. Maybe has something to do with the initial welcome/activation not being active? I would think the stock rom does have it enabled though.. HELP PLEASE! I have the 2016 variant from Virgin, 6.1.1
---------- Post added at 01:39 PM ---------- Previous post was at 01:35 PM ----------
DirtyPISTOLA said:
I personally just had to reflash stock boot.img in odin when i got my bootloop and all was well
Click to expand...
Click to collapse
Do you have the 2016 Virgin mobile variant? I know the 2015s have different firmware and seem to have no problems unbricking. Just curious
uberpyrit said:
I rooted, flashed twrp, and Xposed successfully and made a complete backup. I got a little excessive with my debloating, so I tried to restore my nandroid backup with twrp.. Been bootlooped ever since. I tried flashing the stock boot, recovery, and rom with odin. Nothing works. The best result I can get is when I use Odin to flash stock firmware, then flash the chainfire autoroot. If I do that, it still bootloops, but it gets all the way to the "optimizing apps" screen... If I don't flash the autoroot, it loops after the virgin mobile logo. If I try to use stock rom, cf autoroot, and twrp, it goes all crazy at the initial Samsung screen and won't even loop. I've tried every combination I can think of. Maybe has something to do with the initial welcome/activation not being active? I would think the stock rom does have it enabled though.. HELP PLEASE! I have the 2016 variant from Virgin, 6.1.1
---------- Post added at 01:39 PM ---------- Previous post was at 01:35 PM ----------
Do you have the 2016 Virgin mobile variant? I know the 2015s have different firmware and seem to have no problems unbricking. Just curious
Click to expand...
Click to collapse
You need an adb enabled boot.img and get a logcat on boot to know the reason of this problem
chucksaysblah said:
where can i download the stockl firmware for the boost mobile variant. I am in a bootloop here and have tried everything . I need the stock firmware so i can flash it via odin.
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-j7/how-to/sm-j700p-stock-recovery-stock-boot-t3423314
---------- Post added at 01:58 PM ---------- Previous post was at 01:52 PM ----------
messi2050 said:
You need an adb enabled boot.img and get a logcat on boot to know the reason of this problem
Click to expand...
Click to collapse
OK. Would the boot.img extracted from the stock rom be adb enabled? I'm on my way to work, so I'll have to wait till I get home to try.
uberpyrit said:
http://forum.xda-developers.com/galaxy-j7/how-to/sm-j700p-stock-recovery-stock-boot-t3423314
---------- Post added at 01:58 PM ---------- Previous post was at 01:52 PM ----------
OK. Would the boot.img extracted from the stock rom be adb enabled? I'm on my way to work, so I'll have to wait till I get home to try.
Click to expand...
Click to collapse
No It's not
uberpyrit said:
http://forum.xda-developers.com/galaxy-j7/how-to/sm-j700p-stock-recovery-stock-boot-t3423314
---------- Post added at 01:58 PM ---------- Previous post was at 01:52 PM ----------
OK. Would the boot.img extracted from the stock rom be adb enabled? I'm on my way to work, so I'll have to wait till I get home to try.
Click to expand...
Click to collapse
You need to go to CoffeeNAndroids thread here http://forum.xda-developers.com/galaxy-j7/development/adb-root-access-boot-image-custom-t3431590 to downkoad the adb enabled boot.img
DirtyPISTOLA said:
You need to go to CoffeeNAndroids thread here http://forum.xda-developers.com/galaxy-j7/development/adb-root-access-boot-image-custom-t3431590 to downkoad the adb enabled boot.img
Click to expand...
Click to collapse
Downloaded and flashed the adb-enabled boot.img, now doing the research on how to make it work so i can post my logcat output. ive never done this before so im having to research it(noob, sorry ) i dont want to waste anyones time, ill figure it out, but if someone has time and could post the steps to do it id be grateful. gonna read up on it till i figure out how to work it anyway, but in the meantime someone could be reading my logs.
uberpyrit said:
Downloaded and flashed the adb-enabled boot.img, now doing the research on how to make it work so i can post my logcat output. ive never done this before so im having to research it(noob, sorry ) i dont want to waste anyones time, ill figure it out, but if someone has time and could post the steps to do it id be grateful. gonna read up on it till i figure out how to work it anyway, but in the meantime someone could be reading my logs.
Click to expand...
Click to collapse
np we all were noobs in the beginning here are the steps
-connect your phone to pc
-download mini adb from here :
http://forum.xda-developers.com/showthread.php?t=2317790
-turn on your phone and while it's stuck at sam logo type in mini adb [adb logcat -v long > name of problem.txt}
-u will get a file in the mini adb folder upload it here so i can help you .
messi2050 said:
np we all were noobs in the beginning here are the steps
-connect your phone to pc
-download mini adb from here :
http://forum.xda-developers.com/showthread.php?t=2317790
-turn on your phone and while it's stuck at sam logo type in mini adb [adb logcat -v long > name of problem.txt}
-u will get a file in the mini adb folder upload it here so i can help you .
Click to expand...
Click to collapse
ok, so, every way i try this it isnt working. i flashed twrp so i could do a total wipe. then flashed the stock rom/firmware(J700PVPU1APB7.tar.md5). i flashed the adb-enabled boot.img and tried the logcat, it says waiting on device while the phone bootloops... when i flash cfautoroot and adb boot.img after rom flash, same thing. What am I doing wrong? Device drivers and adb drivers installed 2 weeks ago.
so, i just flashed stock rom:cfautoroot:adb boot.img:stock recovery, and it started to boot properly, ie: android updating apps to android starting, and a bunch of other stuff, then rebooted to bootloop.. farther than ive gotten so far.
---------- Post added at 11:07 PM ---------- Previous post was at 11:06 PM ----------
uberpyrit said:
ok, so, every way i try this it isnt working. i flashed twrp so i could do a total wipe. then flashed the stock rom/firmware(J700PVPU1APB7.tar.md5). i flashed the adb-enabled boot.img and tried the logcat, it says waiting on device while the phone bootloops... when i flash cfautoroot and adb boot.img after rom flash, same thing. What am I doing wrong? Device drivers and adb drivers installed 2 weeks ago.
so, i just flashed stock rom:cfautoroot:adb boot.img:stock recovery, and it started to boot properly, ie: android updating apps to android starting, and a bunch of other stuff, then rebooted to bootloop.. farther than ive gotten so far.
Click to expand...
Click to collapse
trying to recreate the process now...
uberpyrit said:
ok, so, every way i try this it isnt working. i flashed twrp so i could do a total wipe. then flashed the stock rom/firmware(J700PVPU1APB7.tar.md5). i flashed the adb-enabled boot.img and tried the logcat, it says waiting on device while the phone bootloops... when i flash cfautoroot and adb boot.img after rom flash, same thing. What am I doing wrong? Device drivers and adb drivers installed 2 weeks ago.
so, i just flashed stock rom:cfautoroot:adb boot.img:stock recovery, and it started to boot properly, ie: android updating apps to android starting, and a bunch of other stuff, then rebooted to bootloop.. farther than ive gotten so far.
---------- Post added at 11:07 PM ---------- Previous post was at 11:06 PM ----------
trying to recreate the process now...
Click to expand...
Click to collapse
You didn't did anything wrong , it's coffenandroid adb enabled is not working correctly , now try to flash stock recovery as i heard that twrp cause bootloop on j700p
messi2050 said:
No It's not
Click to expand...
Click to collapse
Hey messie,
I have somehow switched the variant of my boost j7 when I was rebuilding it with wifi tethering anyways since I did that my phone is on xas which is Australia I believe and it was working fine even on that variant until I put twrp on it and not even the stock boost firmware has fixed it I do have a backup before the variant was changed that was made with FlashFire but the twrp backup FlashFire makes by default doesn't work and all it does it boot loop over and over and sometimes it will say it is optimizing apps sometumes but doesn't ever load it just reboots and repeats the same thing I tried doing a complete wipe in twrp and tried ur debloated firmware which was very similar to the project I was working on as well as a cm port. I can't go any further on my projects until I can get functionality outta the phone again is there maybe a way I could load FlashFire in twrp as I have root and adb working fully or it there other stuff I could do in adb to fix this I even tried Making the csc only for BST instead of XAS but no go it had no effect
Starchild2k said:
Hey messie,
I have somehow switched the variant of my boost j7 when I was rebuilding it with wifi tethering anyways since I did that my phone is on xas which is Australia I believe and it was working fine even on that variant until I put twrp on it and not even the stock boost firmware has fixed it I do have a backup before the variant was changed that was made with FlashFire but the twrp backup FlashFire makes by default doesn't work and all it does it boot loop over and over and sometimes it will say it is optimizing apps sometumes but doesn't ever load it just reboots and repeats the same thing I tried doing a complete wipe in twrp and tried ur debloated firmware which was very similar to the project I was working on as well as a cm port. I can't go any further on my projects until I can get functionality outta the phone again is there maybe a way I could load FlashFire in twrp as I have root and adb working fully or it there other stuff I could do in adb to fix this I even tried Making the csc only for BST instead of XAS but no go it had no effect
Click to expand...
Click to collapse
Hi
Although a logcat is needed to solve the problem , i believe that this happens because of the kernel security , i think that a permissive kernel is included in this file
http://www.mediafire.com/?u6skqbc4x5bo73p
If it's there flash it and you should have successful boot proces , good luck!
messi2050 said:
Hi
Although a logcat is needed to solve the problem , i believe that this happens because of the kernel security , i think that a permissive kernel is included in this file
http://www.mediafire.com/?u6skqbc4x5bo73p
If it's there flash it and you should have successful boot proces , good luck!
Click to expand...
Click to collapse
Thanx Messi I am going to try it now
messi2050 said:
np we all were noobs in the beginning here are the steps
-connect your phone to pc
-download mini adb from here :
http://forum.xda-developers.com/showthread.php?t=2317790
-turn on your phone and while it's stuck at sam logo type in mini adb [adb logcat -v long > name of problem.txt}
-u will get a file in the mini adb folder upload it here so i can help you .
Click to expand...
Click to collapse
im still working on getting the logs, nothing seems to make the phone readable to logcat. it just says waiting for device..
Starchild2k said:
Thanx Messi I am going to try it now
Click to expand...
Click to collapse
np , tell me if it works for you
---------- Post added at 06:41 PM ---------- Previous post was at 06:39 PM ----------
uberpyrit said:
im still working on getting the logs, nothing seems to make the phone readable to logcat. it just says waiting for device..
Click to expand...
Click to collapse
I'm going to make one and upload it
Hello everyone.
As mentioned above, my HTC is stuck in a Bootloop (Unlocked warning, white HTC Icon, and again) after I uninstalled a Magisk Module via Magisk Manager. I have no TWRP Recovery installed. Any advise how to get the phone operational again? In case of a full reset of data and storage, i am not afraid to do so. Any help is much appreciated.
Greetings
Stefan
*Edit*
I just noticed that adb doesn't recognizes the Phone via command adb devices. Therefore I'm not able to flash a ruu for my phone. Now I have no idea left what to do
Stefan-Duisburg said:
Hello everyone.
As mentioned above, my HTC is stuck in a Bootloop (Unlocked warning, white HTC Icon, and again) after I uninstalled a Magisk Module via Magisk Manager. I have no TWRP Recovery installed. Any advise how to get the phone operational again? In case of a full reset of data and storage, i am not afraid to do so. Any help is much appreciated.
Greetings
Stefan
*Edit*
I just noticed that adb doesn't recognizes the Phone via command adb devices. Therefore I'm not able to flash a ruu for my phone. Now I have no idea left what to do
Click to expand...
Click to collapse
you can flash from sd card
---------- Post added at 11:29 AM ---------- Previous post was at 11:26 AM ----------
tolgazorba said:
you can flash from sd card
Click to expand...
Click to collapse
You can find the same software number at the top of the device or the numbered software in the android file host ziand folder
Hello @tolgazorba.
Thank you for your answer. Right now I'm heading to work, but I will try your Advise this evening. Fortunately i downloaded a ruu zip matching with my firmware (2.55.bla bla) and matching with my cid as well. I will report if everything worked, or, hopefully not, not.
Thanks again
Stefan
hello
no problem I would like to explain in detail but my english is very bad
Hi there. That advice was great, everything works now fine again. I guess I let my hands off rooting for now, at least there's an official LOS for this device lol
Thanks again
En joy
You're welcome
I have little similar problem. I bricked phone after updating magisk.
Then I tried to flash original boot.img but didn't know which slot A or B so flashed both. Unfortunately, it doesn't help.
Please help me
Merhaba
are you serious
---------- Post added at 06:49 PM ---------- Previous post was at 06:48 PM ----------
lulonen said:
I have little similar problem. I bricked phone after updating magisk.
Then I tried to flash original boot.img but didn't know which slot A or B so flashed both. Unfortunately, it doesn't help.
Please help me
Click to expand...
Click to collapse
because I need help with something
---------- Post added at 06:55 PM ---------- Previous post was at 06:49 PM ----------
my problem is that i can't assign custom rom to your device why do you think
I thinked that's because of slots
Hi
buddy what exactly is the problem
completely don't know how to solve it.
bootimg flashed over TWRP, now i have original boot.img and cant start temporary recovery.
lulonen said:
completely don't know how to solve it.
bootimg flashed over TWRP, now i have original boot.img and cant start temporary recovery.
Click to expand...
Click to collapse
Maybe just flash actual firmware.zip with sdcard as i have done? With that you are back on full stock and you can root again etc...
Thx. unfortunately, I don't have a backup of one important app which is more important than the whole phone so I want to find every possibility without losing data.
hi
lulonen said:
Thx. unfortunately, I don't have a backup of one important app which is more important than the whole phone so I want to find every possibility without losing data.
Click to expand...
Click to collapse
You are a very old user, I think you know how to do it
Hi
full rom viper twrp with temporary rom flash without wipe i not temporary to permanent summer device
can't boot TWRP and dont have stock rom without wipe.
Don't you know why I can't boot temporary TWRP? download mode always stuck at booting
so find a backup of the auto and load it with adb sideload, whichever version you have is the backup of that version
---------- Post added at 04:09 PM ---------- Previous post was at 04:03 PM ----------
https://androidfilehost.com/?fid=6006931924117931578
isn't full wipe?
don't remember but EU version (043). I am on LeeDrOiD U12 V1.3
re-install the same rum without deleting or update it with adb sideload
tolgazorba said:
so find a backup of the auto and load it with adb sideload, whichever version you have is the backup of that version
---------- Post added at 04:09 PM ---------- Previous post was at 04:03 PM ----------
https://androidfilehost.com/?fid=6006931924117931578
Click to expand...
Click to collapse
If I only had a backup different to TWRP.... ;-(
Hi everyone, my dad has been using the oneplus one since it came out. he has been mentioning lately the phone is really slow, so i decided to try and root the phone and get a newer OS for him in hope it runs more smooth.
here where the trouble began, so i had to root the phone in order to get a new OS, so i got as far as installing supersu, which came up with a binary error so i went back out to TWRP and flashed a newer version, when i rebooted phone when in to a loop at the cyonegenmod, it just wont load. so i rebooted back in to TWRP and thats when i went stupid and deleted everything ( with out making a backup ).
So I am now stuck with no OS installed, with out an OS i have been able to adb push files to the internal storage for the roms i have down loaded, i try using sideload to install the roms i have downloaded, which has always failed, with the sideload error executing updater zip / xxxxx/ xxxx/ etc.
questions i have
-the error is due to the wrong ROM i have sideloaded? ( what is the stock version? some say 4.4.2 kitkat? some say cm-13.1.2-ZNH2KAS3P0-bacon-signed-fastboot )
-if i am using adb sideload, which file should i be using? cm-13.1.2-ZNH2KAS3P0-bacon-signed-fastboot or cm-13.1.2-ZNH2KAS3P0-bacon-signed ?
- to my understanding ( whihc isnt much ) i just need to find the right stock ROM zip file and sideload it in and it should run again right?
or am i totally wrong and the phone is pretty much dead?
any help would be great
Thanks in advance
I'm replying since no one is. I'm not sure about the error but did you factory reset prior to flashing?
You can restore stock rom using the method in this thread https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541.
Other than sideloading, you can use an OTG adapter + thumbdrive. Even in recovery, OTG storage is still detected.
Hopefully you are able to solve your issue.
---------- Post added 10-08-2020 at 12:07 AM ---------- Previous post was 09-08-2020 at 11:59 PM ----------
Also, supersu/superuser is outdated. Magisk is the current way to root now.
risay07 said:
I'm replying since no one is. I'm not sure about the error but did you factory reset prior to flashing?
You can restore stock rom using the method in this thread https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541.
Other than sideloading, you can use an OTG adapter + thumbdrive. Even in recovery, OTG storage is still detected.
Hopefully you are able to solve your issue.
---------- Post added 10-08-2020 at 12:07 AM ---------- Previous post was 09-08-2020 at 11:59 PM ----------
Also, supersu/superuser is outdated. Magisk is the current way to root now.
Click to expand...
Click to collapse
Thanks for your reply
yeah i did do a factory reset, i then wiped everything including the system
so i am now stuck with NO OS i believe, i did read that post you linked, but i cant access fastboot mode
all i can access is TWRP, so i can push files in the storage, but when ever i sideload or install the Stock roms and reboot the phone nothing is happening just stuck at the one plus logo
any suggestions from this point??
Thanks in advance
Did you try to boot to fastboot by plugging the usb cable while volume up button is pressed? What android version are you on before you wiped? And what is your current TWRP version.
---------- Post added at 03:16 AM ---------- Previous post was at 02:51 AM ----------
IMO, since fastboot and adb sideload not working for you, try going the thumbdrive+OTG cable method. Download any Pie or Q rom and open gapps pico and copy them to the thumbdrive. Connect the thumbdrive to your phone using the OTG cable and flashed it in TWRP.