absurdly stupid move by me.3113wTWRPv2.6.3.0 only left - Galaxy Tab 2 Q&A, Help & Troubleshooting

I was doing fine with my PAC-4.3.1. I backed everything up. Then I erased all ... yep... no OS. And trying to install something like the MicroDelta-P3110-4.2.2xxx... says its unable to open the zip file. So I probably messed up my root also.
I have very limited access to XP. I run Linux. Ubuntu, Debian ... but I can not find a working way to salvage my tab2.7 this way. odin for XP was how I got to 4.1.2.
I believe I need help in knowing what is the actual correct next step. I read the forum and have failed so far. So would someone be able to point me to the correct link knowing my situation?
I think I was on 4.2.2. Then PAC 4.3.1
I used to have Philz installed. Recently went to TWRP because I was getting very unreliable bootloops and switching helped in the short term...

try flashing PhilZ Touch using adb sideload, reboot into philz touch and try the rom again.... maybe flash the rom using sideload
---------- Post added at 11:27 PM ---------- Previous post was at 11:26 PM ----------
Read this: http://teamw.in/ADBSideload
---------- Post added at 11:28 PM ---------- Previous post was at 11:27 PM ----------
You can also try flashing any other Rom using adb sideload

canezila said:
I was doing fine with my PAC-4.3.1. I backed everything up. Then I erased all ... yep... no OS. And trying to install something like the MicroDelta-P3110-4.2.2xxx... says its unable to open the zip file. So I probably messed up my root also.
I have very limited access to XP. I run Linux. Ubuntu, Debian ... but I can not find a working way to salvage my tab2.7 this way. odin for XP was how I got to 4.1.2.
I believe I need help in knowing what is the actual correct next step. I read the forum and have failed so far. So would someone be able to point me to the correct link knowing my situation?
I think I was on 4.2.2. Then PAC 4.3.1
I used to have Philz installed. Recently went to TWRP because I was getting very unreliable bootloops and switching helped in the short term...
Click to expand...
Click to collapse
Now what do you mean by you erased everything? Even wiping system, user data and both caches won't break root. Was there something else you wiped that you probably shouldn't have? What you could do is set up a virtual machine for XP, or even dual boot. It's a little time consuming, but in the end I do believe it would be worth it If you can't even flash a zip I don't really know what else you could do. Hopefully someone else will chime in with a less exhausting solution. But dual booting or using a virtual machine is certainly option. That way you can easily odin back to stock.
---------- Post added at 05:35 PM ---------- Previous post was at 05:33 PM ----------
Android-Andi said:
try flashing PhilZ Touch using adb sideload, reboot into philz touch and try the rom again.... maybe flash the rom using sideload
---------- Post added at 11:27 PM ---------- Previous post was at 11:26 PM ----------
Read this: http://teamw.in/ADBSideload
---------- Post added at 11:28 PM ---------- Previous post was at 11:27 PM ----------
You can also try flashing any other Rom using adb sideload
Click to expand...
Click to collapse
I thought about that, but he said he broke root and can't flash a zip? Would sideloading work around that?

Sure Sideload should work, i think root is not broken (can access to storage be broken in recovery? i don´t think so ) - maybe bad download of the rom or he can only flash signed zip´s ? maybe he can try disable zip-verification (?)

Android-Andi said:
Sure Sideload should work, i think root is not broken (can access to storage be broken in recovery? i don´t think so ) - maybe bad download of the rom or he can only flash signed zip´s ? maybe he can try disable zip-verification (?)
Click to expand...
Click to collapse
I've never had to use side load lol... You know more than I on the issue

How to setup ADB on Ubuntu? ---> http://forum.xda-developers.com/showthread.php?p=11823740#post11823740
or http://askubuntu.com/questions/318246/complete-installation-guide-for-android-sdk-on-ubuntu
---------- Post added at 11:51 PM ---------- Previous post was at 11:47 PM ----------
@canezila can you please check in TWRP -> Settings -> "Zip file signarure verification?" Checked or unchecked? If it´s checked: uncheck it!

Recovery couldn't open the zip. A failed signature verification would return a "signature verification failed" error, no?
Sent from my SAMSUNG-SGH-T769 using xda app-developers app

i don´t know what he did (i don´t think he knows it too ) let´s wait for his feedback...
trying to flash a recovery or another rom using sideload might work...
or he can try another file (only flashing a recovery.zip) flashing from a microSD card?
could be a bad download of the file too...
i´m going to sleep now hope my tipps work for him - i am sure he´ll give any feedback
---------- Post added at 12:14 AM ---------- Previous post was at 12:08 AM ----------
"(...)I used to have Philz installed. Recently went to TWRP because I was getting very unreliable bootloops and switching helped in the short term..(...)"
a recovery wouldn´t make a rom bootlooping i think he forgot to wipe something.
i never had a bootloop or other strange problems on a working rom! NEVER!
What i am doing:
wipe cache partition
wipe dalvic cache
format /system
wipe data factory reset (on PhilZ Touch "Clean to install a new Rom")
flash rom
reboot
if it´s working i reboot into recovery again
flash gapps
flash NEXT Kernel
flash Proprietary files for NEXT Kernel
reboot again
(sometimes flashing NEXT Kernel + Proprietary files directly after the rom before 1st boot - only if i am on Dual-Boot)
---------- Post added at 12:18 AM ---------- Previous post was at 12:14 AM ----------
If you like MicroDelta 4.1.2
Download
MicroDelta-P3110-JB-4.1.2-P3110XXDME3-signed.zip and MicroDelta-P3113-JB-4.1.2-P3113XXDME3-signed.zip
Try this (yes do it again):
wipe cache partition
wipe dalvic cache
format /system
wipe data factory reset
First flash MicroDelta-P3110-JB-4.1.2-P3110XXDME3-signed.zip
directly after that flash MicroDelta-P3113-JB-4.1.2-P3113XXDME3-signed.zip

$ sudo apt-get install android-tools-adb
$ adb version
Android Debug Bridge version 1.0.31
$ adb sideload philz_touch_5.15.0-p3110-blackhawk.zip
$ adb sideload blackhawk-next-kernel-2.1.5-p31xx-miui.zip
**probably usless step but I wanted to see if it worked and it installed wo errors***
$ adb sideload miui_3.10.25_p3110_beta2.zip
$ adb sideload proprietary-vendor-samsung.zip
** yes, I have no idea what I am doing because this probably is part of another thread.... but it is ok**
But now that I can easily push ROMs over... I am going to go crazy installing a bunch of similar 4.3.1 roms.
THANKS FOR THE HELP!

I ended up on PAC MAN 4.3.1. at least for now

Related

[SOLVED] FASTBOOT flash recovery remote: not allowed (update boot.img and system.img

I'm trying to reflash the default the original recovery in order to install
OTA_K2PLC_CL_JB422_SENSE50_MR_Cricket_US_3.02.1050.10-2.04.1050.5_release_343402dpsh8ror12wwdww2.zip
(4.2.2 and touch5 OTA)
What is causing this error and how do I get past it?
I'd try flashing the zip, but cwm can't mount the sdcard for some reason
cricket/moonshined/rooted/superCID
what command did you send
I sent
fastboot flash recovery [imagename].img
are you unlocked?
Yes. Unlocked bootloader, rooted, moonshine s-off, with supercid (1s). Not radio, s-off, only moonshined (disables the check, from what I understand)
start with phone connected to computer while booted in OS.
then open command prompt
adb reboot bootloader
adb kill-server
fastboot flash recovery recovery.img
fastboot reboot
russellvone said:
start with phone connected to computer while booted in OS.
then open command prompt
adb reboot bootloader
adb kill-server
fastboot flash recovery recovery.img
fastboot reboot
Click to expand...
Click to collapse
same result
Code:
C:\Users\user\Desktop\platform-tools>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Users\user\Desktop\platform-tools>adb kill-server
* server not running *
C:\Users\user\Desktop\platform-tools>fastboot flash recovery recovery.img
< waiting for device >
sending 'recovery' (8478 KB)... OKAY
writing 'recovery'... FAILED (remote: not allowed)
C:\Users\user\Desktop\platform-tools>
ok....when in fastboot, unplug usb from computer....
then send command
fastboot flash recovery recovery.img
then plug usb into computer
see if that flashes it
same result
zomgitsanoob said:
same result
Click to expand...
Click to collapse
Windows 8.1?
Okay, I see the problem now. Somehow, somewhere along the line, my bootloader got locked again... no idea how (last OTA update, perhaps?) (says TAMPERED/LOCKED)
Do I simply follow the same procedure I did the first time, or will supercid/s-off be a problem?
lol
#EDIT#
yeah, just
fastboot flash unlocktoken Unlock_code.bin
---------- Post added at 03:41 PM ---------- Previous post was at 03:39 PM ----------
S-OFF and superCID won't be a problem
---------- Post added at 03:46 PM ---------- Previous post was at 03:41 PM ----------
also with s-off, no need to ever lock/relock you're bootloader again...
russellvone said:
lol
#EDIT#
yeah, just
fastboot flash unlocktoken Unlock_code.bin
---------- Post added at 03:41 PM ---------- Previous post was at 03:39 PM ----------
S-OFF and superCID won't be a problem
---------- Post added at 03:46 PM ---------- Previous post was at 03:41 PM ----------
also with s-off, no need to ever lock/relock you're bootloader again...
Click to expand...
Click to collapse
wait, I'm confused. Didn't I have to unlock it again right now, despite being s-off, in order to flash my recovery? Or did you mean the pl80.zip method would have worked without unlocking, since I have s-off?
nope, sorry I posted before I read you 'oops I'm relocked' post
you gotta be unlocked to flash anything, s-on or s-off
keep it unlocked, there is no reason to lock it again after you unlock it this time.....
you can accept OTA updates with unlocked bootloader being s-off
Ah, man! I unlocked the bootloader like you said and upon reboot it went to the initial set-up... it factory reset.... despite not having the stock recovery or anything
So.., back to square one- flash the recovery and I can apply the OTA update that started this whole mess, correct?
Will I lose the OTA update if I restore a remote nandroid backup from obackup?
no, you'll still be able to receive it
and as long as your
/system
is in stock condition it will go through
by /system in stock condition, you mean as in not having removed all the bs I didn't want/use in order to make room, right? because I removed the cricket account app (which did nothing anyway, the default facebook app, the rescue app... a lot o things. I have backups of the apks and the app data, though.
Of course, because f-k me, my nandroid seems to be corrupted :victory:
godammit, I just want to get this OTA update installed because it has touch5 and an updated Android. I'd tery installing from sideload, but CWM can't mount the sd card :highfive:
zomgitsanoob said:
by /system in stock condition, you mean as in not having removed all the bs I didn't want/use in order to make room, right? because I removed the cricket account app (which did nothing anyway, the default facebook app, the rescue app... a lot o things. I have backups of the apks and the app data, though.
Of course, because f-k me, my nandroid seems to be corrupted :victory:
godammit, I just want to get this OTA update installed because it has touch5 and an updated Android. I'd tery installing from sideload, but CWM can't mount the sd card :highfive:
Click to expand...
Click to collapse
what about the zip I linked to you?
just flash it
---------- Post added at 04:22 PM ---------- Previous post was at 04:20 PM ----------
https://www.dropbox.com/s/f2fq45couq54eop/4.1.2_JB_Crkt_2.04.1050.3_stock_odexed.zip
flash this then stock recovery and update after
---------- Post added at 04:30 PM ---------- Previous post was at 04:22 PM ----------
twrp twrp twrp....
I've got a twrp backup too if you want to restore it(with twrp) of course, lol
Since we're s-off, we can then flash cwm or twrp back, install root and supersu from a .zip, and use rom toolbox to start hacking all the garbage back out again (and reinstalling the xposed framwork and all the good stuff) while enjoying sense 5 and android 4.whateverversionIdon'tevenrememberrightnow-2,ithink, correct? So like square one (when we bought the phone), but but with the latest OTA? :silly:
<-- just knowledgeable enough to make a mess, apparently
yes, successfully update to 4.2.2 Sense 5 then hack it up!

I need help, I accidentally wiped system and I haven't got any OS

[SOLVED]
This isn't my first time changing my ROM, but I'm still a noob. While I was installing Paranoid Android 5.0 alpha 2, I accidentally wiped system, and I got an error trying to install the zip (even when I didn't wipe system I got that error too). Now I haven't got any OS, and I can't use my OPO... I can only boot in the TWRP recovery. I know there's a way to install a ROM with the PC and Windows commands, but I don't know how. Please, if there's anyone that can help me, I would appreciate it. Thanks
I'm pretty sure you can connect phone to pc, place the rom zip in the root file. Then disconnect and boot into recovery. Then flash the zip file once you've located it.
http://www.technobuzz.net/root-unroot-unlock-restore-oneplus-one-wugfresh-toolkit/
---------- Post added at 04:13 PM ---------- Previous post was at 04:12 PM ----------
Try one toolkit that you can find in google, and you will be ok. Its not so hard
Thank you! I used the bacon Toolkit, because the device was in a bootloop and my PC can't recognize it, and it worked perfectly. I also rooted (again) it, it's very easy. Thanks!

[ROM] SU4TL-44 100% Stock

SU4TL-44 Stock Image for XT1254: https://mega.nz/#!v4QWiITb!_0jWWzE4KWCEgT__C36rYe0vaTzGKcEFsZm0vvBtLBg
Flash with TWRP.
This package will flash every image in the SU4TL-44 firmware package except for recovery. It should bring your phone to almost 100% stock. The only image that is not included is the recovery image, because that would overwrite TWRP. If you need the stock recovery, revert to stock by following section 0 of my guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684.
Yes, it does include modems.
No, it will not re-lock your bootloader.
No, it won't erase your data, but you should do a factory reset in TWRP after flashing this. You might be able to get away without it if you're coming from a modified stock rom, but if you leave out the factory reset after coming from a CM-based rom, you're gonna have a bad time.
Thanks to @firstEncounter for letting me incorporate his flashable zip into this package.
Will have to download this later. Looked to go back to stock and wait for mm to come out.
Sent from my XT1254 using Tapatalk
Just to be clear, this doesn't flash re-lock the bootloader, right? So it's just the ROM... correct?
schwinn8 said:
Just to be clear, this doesn't flash re-lock the bootloader, right? So it's just the ROM... correct?
Click to expand...
Click to collapse
No it won't relock boot loader just installed it you will not be rooted and twrp will ask you if you want to root before reboot if you click no and want to at a later point just go back into boot loader by doing vol down power combo from power off and select open boot loader and when you click to reboot it will ask you again if you want to root then you can just slide to install
schwinn8 said:
Just to be clear, this doesn't flash re-lock the bootloader, right? So it's just the ROM... correct?
Click to expand...
Click to collapse
Correct
Can I install viper and su along with this?
MazinDLX said:
Can I install viper and su along with this?
Click to expand...
Click to collapse
Sure. Just flash the rom first and the mods second.
TheSt33v said:
Sure. Just flash the rom first and the mods second.
Click to expand...
Click to collapse
Ok last night I tried this in this order.
TWRP Backup & ADB Pulled Back-up folder
I then went into TWRP and wiped everything
ADB Pushed the image onto the phone
Installed, wiped dalvik & rebooted into a bootloop of the Motorola Symbol
MazinDLX said:
Ok last night I tried this in this order.
TWRP Backup & ADB Pulled Back-up folder
I then went into TWRP and wiped everything
ADB Pushed the image onto the phone
Installed, wiped dalvik & rebooted into a bootloop of the Motorola Symbol
Click to expand...
Click to collapse
I've never tried to install an image via ADB before. Did you mount the image elsewhere and extract the system folder, and then ADB-pushed that? If not, your bootloop is probably because there's just a big, unextracted system.img on your system partition, and not the actual files within it. Why not just flash it with TWRP? When I tested it, I flashed it via TWRP and it worked.
If you really don't want to flash it via TWRP for some reason, you can extract the system.img from the zip and flash it using fastboot (fastboot flash system system.img).
EDIT: Oh wait, I think I understand now. You just used ADB to put the zip on your phone, and then you installed it with TWRP. Got it. Well my next question is why use ADB at all? Why not just plug in your phone while it's booted into TWRP and use the native MTP to transfer files?
Its chromeos ****, and I'm just a fan of cmd line.
---------- Post added at 10:49 PM ---------- Previous post was at 10:48 PM ----------
I'm going to try again later, after wiping everything X5 and reinstalling CM12.1.
Its flawless.
---------- Post added at 10:50 PM ---------- Previous post was at 10:49 PM ----------
CM12.1 is flawless that is.
The boot.img should probably be included as well for people flashing this from a custom ROM, otherwise they will experience a boot loop.
MazinDLX said:
Its chromeos ****, and I'm just a fan of cmd line.
---------- Post added at 10:49 PM ---------- Previous post was at 10:48 PM ----------
I'm going to try again later, after wiping everything X5 and reinstalling CM12.1.
Its flawless.
---------- Post added at 10:50 PM ---------- Previous post was at 10:49 PM ----------
CM12.1 is flawless that is.
Click to expand...
Click to collapse
This package only flashes /system. CM flashes its own boot.img, which is why this isn't working for you. I'll try to find some time tonight to add in the other images in the stock firmware to this package. Sorry about that.
firstEncounter said:
The boot.img should probably be included as well for people flashing this from a custom ROM, otherwise they will experience a boot loop.
Click to expand...
Click to collapse
Great minds think alike. Do you know if boot.img will cover it, or are there other partitions that are flashed by CM that need to be included as well?
TheSt33v said:
Great minds think alike. Do you know if boot.img will cover it, or are there other partitions that are flashed by CM that need to be included as well?
Click to expand...
Click to collapse
Nope, just boot and system.
Feel free to include the bootloader/radio package from my thread into your zip if you'd like to make this equivalent to flashing a full stock firmware.
MazinDLX said:
Its chromeos ****, and I'm just a fan of cmd line.
---------- Post added at 10:49 PM ---------- Previous post was at 10:48 PM ----------
I'm going to try again later, after wiping everything X5 and reinstalling CM12.1.
Its flawless.
---------- Post added at 10:50 PM ---------- Previous post was at 10:49 PM ----------
CM12.1 is flawless that is.
Click to expand...
Click to collapse
I updated the link. It now flashes boot.img in addition to system.img. It should work for you now.
firstEncounter said:
Nope, just boot and system.
Feel free to include the bootloader/radio package from my thread into your zip if you'd like to make this equivalent to flashing a full stock firmware.
Click to expand...
Click to collapse
I'm not entirely sure how to write a script to flash those in TWRP. For boot and system, it's easy because the devices that they are flashed to match the names used by fastboot. Bootloader and radio seem to be a little different though. When I list the contents of /dev/block/bootdevice/by-name, there is no "motoboot" or "radio," which is what fastboot uses when you flash these. I do see "aboot" and "modem," and I'm pretty sure those are the targets I'm looking for, but I don't want to go flashing things unless I'm 100% sure. Since there's not a huge demand for figuring that out, and boot + system is all people will need in 99% of cases, I'll leave them out. Thanks though!
Downloading, my XDA hasn't been functioning right lately and I don't get get notified of the 3778328 threads I'm subscribed too lol
---------- Post added at 10:15 PM ---------- Previous post was at 10:13 PM ----------
Thanks for the quick responses, you got a tip jar link?
MazinDLX said:
Downloading, my XDA hasn't been functioning right lately and I don't get get notified of the 3778328 threads I'm subscribed too lol
---------- Post added at 10:15 PM ---------- Previous post was at 10:13 PM ----------
Thanks for the quick responses, you got a tip jar link?
Click to expand...
Click to collapse
No, but I appreciate the thought. Donate to this guy instead. He does way more than me and also needs it way more than me: http://forum.xda-developers.com/droid-turbo/development/computerfreekunlocked1-0-t3255945
TheSt33v said:
I updated the link. It now flashes boot.img in addition to system.img. It should work for you now.
Click to expand...
Click to collapse
Thus really helped for whatever reason after altering the fxz xml so I wouldn't lose data rsd lite said the xml files didn't match. I have done this before with no issues. I couldn't take the recent Ota because somehow the system was modified. I am guessing it was something from sunshine. I never rooted the phone just unlocked so I don't know how anything was modified. This made it so much easier flashed it flashed stock recovery and took ota thanks.
bigv5150 said:
Thus really helped for whatever reason after altering the fxz xml so I wouldn't lose data rsd lite said the xml files didn't match. I have done this before with no issues. I couldn't take the recent Ota because somehow the system was modified. I am guessing it was something from sunshine. I never rooted the phone just unlocked so I don't know how anything was modified. This made it so much easier flashed it flashed stock recovery and took ota thanks.
Click to expand...
Click to collapse
Awesome! That's why we do this

HTC U12+ Bootloop after uninstalling Magisk Module

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.... ;-(

Help Needed Please

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.

Categories

Resources