Related
I have a Galaxy Tab 2 VZW and was trying to install the ClearRom, but I guess I forgot to unlock bootloader, so now everytime I turn the tab on I get message statitng " System Software not authorized by Verizon Wireless has been found on your phone."
I have a backup from before I tried installing the ROM but don't know what to do with it
Any help will be appreciated
melog69 said:
I have a Galaxy Tab 2 VZW and was trying to install the ClearRom, but I guess I forgot to unlock bootloader, so now everytime I turn the tab on I get message statitng " System Software not authorized by Verizon Wireless has been found on your phone."
I have a backup from before I tried installing the ROM but don't know what to do with it
Any help will be appreciated
Click to expand...
Click to collapse
HOw did you make the backup? CWM? If so, then install CMW recovery and do a restore.
DigitalMD said:
HOw did you make the backup? CWM? If so, then install CMW recovery and do a restore.
Click to expand...
Click to collapse
I tried getting into recovery mode, but I get the following screen everytime, I think I need the Stock Firmware to flash with ODIN but I don't know where to find it.
<iframe src="https://skydrive.live.com/embed?cid=47A1A726F16BDCFD&resid=47A1A726F16BDCFD%212570&authkey=AE3MPZ8PewFeQos" width="180" height="320" frameborder="0" scrolling="no"></iframe>
Always, ALWAYS, follow directions exactly how they're laid out.
What you need to do is download the aboot.img to your sd card. Reboot into recovery, ADB Shell into your device (you may need linux for this part as Windows doesn't recognize the device in recovery mode). Once you ADB into recovery, make sure you are root (noted by # instead of $).
Then:
dd if=/sdcard/aboot.img of=/dev/block/mmcblk0p5
reboot download
This should unlock you bootloader so you can get by verizons pesky warning.
We can't see the picture you tried attaching.
MrHyde03 said:
Always, ALWAYS, follow directions exactly how they're laid out.
What you need to do is download the aboot.img to your sd card. Reboot into recovery, ADB Shell into your device (you may need linux for this part as Windows doesn't recognize the device in recovery mode). Once you ADB into recovery, make sure you are root (noted by # instead of $).
Then:
dd if=/sdcard/aboot.img of=/dev/block/mmcblk0p5
reboot download
This should unlock you bootloader so you can get by verizons pesky warning.
We can't see the picture you tried attaching.
Click to expand...
Click to collapse
I cannot get to recovery mode, only download mode, also ClearRom did not specify that the bootloader, that is why I did not even bother
melog69 said:
I cannot get to recovery mode, only download mode, also ClearRom did not specify that the bootloader, that is why I did not even bother
Click to expand...
Click to collapse
You'll more than likely have to send it back. There has been no official release of stock firmware, unfortunately (none that I have found at least). In the root thread there are steps 1 - 3 for a reason. 1 - Root, 2 - Unlock and Recovery, 3 - Custom ROM. Always follow directions.
MrHyde03 said:
You'll more than likely have to send it back. There has been no official release of stock firmware, unfortunately (none that I have found at least). In the root thread there are steps 1 - 3 for a reason. 1 - Root, 2 - Unlock and Recovery, 3 - Custom ROM. Always follow directions.
Click to expand...
Click to collapse
Well, thanks guys now I know what to do when it's fixed
melog69 said:
Well, thanks guys now I know what to do when it's fixed
Click to expand...
Click to collapse
Maybe try a stock 3100 rom? If the hardware is the same should work, just need to set APN etc.Then reroot, install recovery, install cuztom rom.
---------- Post added at 04:04 PM ---------- Previous post was at 03:54 PM ----------
acefsw said:
Maybe try a stock 3100 rom? If the hardware is the same should work, just need to set APN etc.Then reroot, install recovery, install cuztom rom.
Click to expand...
Click to collapse
Actually, according to here http://forum.xda-developers.com/showthread.php?t=1885558 you just need download mode to install the stock image and then follow the rest of the steps.
acefsw said:
Maybe try a stock 3100 rom? If the hardware is the same should work, just need to set APN etc.Then reroot, install recovery, install cuztom rom.
Click to expand...
Click to collapse
DO NOT INSTALL A P3100 ROM. It's not the same hardware (not really even close), so that would only make it worse.
imnuts said:
DO NOT INSTALL A P3100 ROM. It's not the same hardware (not really even close), so that would only make it worse.
Click to expand...
Click to collapse
I edited the post, read the link, it is for his device
imnuts is correct. These devices are extremely different and really does need it's own subforum so people don't keep getting confused. The i705 is closest to the i535 (s3), nearly identical actually.
MrHyde03 said:
imnuts is correct. These devices are extremely different and really does need it's own subforum so people don't keep getting confused. The i705 is closest to the i535 (s3), nearly identical actually.
Click to expand...
Click to collapse
Then wouldn't it be easier to flash an S Rom?
melog69 said:
Then wouldn't it be easier to flash an S Rom?
Click to expand...
Click to collapse
It still wouldn't work. boot, recovery, and system for the s3 are designed for the s3. The hardware is the same, but the software has it's differences. What differences, though, is beyond me.
I have the same issue, this is the first time I've ever "Bricked" a device. Thought I followed the instructions correctly, I can successfully flash recovery.tar.md5 on Mr.Hydes thread http://forum.xda-developers.com/showthread.php?t=1885558 but when it goes to reboot it gives me the Yellow ExclaTriangle "System software not authorized by Verizion , yadi, yadi ya da".
I can get into Download mode but NO RECOVERY, Tried flashing (With ODIN) CWM 6.0.1.9 located here http://forum.xda-developers.com/showthread.php?t=2044630 but ERROR with NAND WRITE FAIL.
Does anyone have a PIT file? I want give Heimdall a stab at it before I go throw it through Verizon's front window. Appreciate any help, like I said I understand the importance of following Instructions, I've done plenty of Android devices before including The Original GTab7, I dont mind cracking it open either, I've already had it apart to disconnect the battery but that did no help either, BTW it's really easy to open up.
Sounds like you didn't flash the unsecure bootloader
Sent from my SCH-I535 using XDA Premium HD app
MrHyde03 said:
Sounds like you didn't flash the unsecure bootloader
Sent from my SCH-I535 using XDA Premium HD app
Click to expand...
Click to collapse
I couldn't boot into Recovery to Flash, I'm Trying to flash now using Odin but get "Secure Check Fail". Any Ideas?
The bootloader needs to be flashed before the recovery using the dd command. Its listed first under step 2, before the recovery.
Sent from my SCH-I535 using XDA Premium HD app
MrHyde03 said:
The bootloader needs to be flashed before the recovery using the dd command. Its listed first under step 2, before the recovery.
Sent from my SCH-I535 using XDA Premium HD app
Click to expand...
Click to collapse
Yeah that's where I'm confused, I've had it rooted and unlocked since November following your original Development, I was on G3 not J1. Followed the Instructions and then crap.
Unlocked since Nov and it just now crapped? That doesn't make any sense.. When you boot into download mode right now, what orientation is the screen? Portrait or landscape? Landscape would mean a correctly flashed aboot.img (boot loader)
Sent from my SCH-I535 using XDA Premium HD app
iwSachin plain
MrHyde03 said:
Unlocked since Nov and it just now crapped? That doesn't make any sense.. When you boot into download mode right now, what orientation is the screen? Portrait or landscape? Landscape would mean a correctly flashed about.img (boot loader)
Sent from my SCH-I535 using XDA Premium HD app
Click to expand...
Click to collapse
I followed this thread of yours in the beginning of NOV. http://forum.xda-developers.com/showthread.php?t=1942674 I was rooted and unsecured bootloader, had CWM and SuperUser, but there weren't any ROMS out yet. Everything was fine until I went to install CleanRom the other day.
Portrait Orientation in Download mode.
hi, iam new user of TF300t, i installed the Energy.TF201.or.TF300..JB.03.18.2013.( i dont remebmer is the STOCKED or THEMED) ! after that i wanted to install BAKED_TF300T_BB-8, but the device stay on the boot menu! so what i did , installed the 6.0.2.3 CWM ( [CWM][6.0.2.3 / 5.5.0.4] Official CWM Recovery for JB/ICS + ROOT) ! after that i rebooted the device. Stock in the Asus LOGO! After i rebboted by holding the power menu and volume down, i choosed the wipe option ( i dont know why) and from tht time, it rebbots only in the 6.0.2.3 CWM what ever i do!
For 5 days, i have tried to flash via fastboot twrp.blob, i have pushed the firmware from asus to /sdcard and flashed via fastboot always, i have tried and read similaire problems! didt succed! i have always the message tht Can not mount sdcard! cant mound E/data! cant mount anythingg!! What ever i do, always reboot to this CWM !!!!!
please any one help me!!!!!!! thanks a lot!!!
You have installed an incompatible older custom recovery on the 4.2.1 bootloader. What you should have one is downgraded the bootloader from the energy thread to 4.1.1. You didn't need to downgrade your recovery.
Anyway I think you have bricked now.
sbdags said:
You have installed an incompatible older custom recovery on the 4.2.1 bootloader. What you should have one is downgraded the bootloader from the energy thread to 4.1.1. You didn't need to downgrade your recovery.
Anyway I think you have bricked now.
Click to expand...
Click to collapse
but i can use adb commands, and fastboot commande ( except tht i have waiting for device each time) so its bricked for EVER?!
You appear to have the same brick as everyone else. Caused by an older recovery on the latest bootloader.
If you can get fastboot to accept a lower bootloader or get it to accept TWRP 2.4.4.0 you should be able to recover but as you said it won't accept anything........
sbdags said:
You appear to have the same brick as everyone else. Caused by an older recovery on the latest bootloader.
If you can get fastboot to accept a lower bootloader or get it to accept TWRP 2.4.4.0 you should be able to recover but as you said it won't accept anything........
Click to expand...
Click to collapse
yes, it accept nothing! even if i downgrade to ics to apply the nvflash its worse! so should i say bye forever to my tf300t?!! if yes, which tablets tht cn be less bricked than others? thks a lottt! wht would u do if u were at my place? thksssssssssss
buy a new mainboard (motherboard)
Sent from my TF300T using xda app-developers app
How are you trying to downgrade? Can you get to the booloader? If yes, try this:
In bootloader, wipe data
Reboot into bootloader
Then, using fastboot, flash system blob from Asus stock ROM using fastboot (fastboot -i 0x0b05 flash staging blob)
If that succeeds, flash appropriate TWRP from bootloader using fastboot, then flash bootloader compatible ROM
If it only (re)boots to recovery, then you'll have to hang in there until a solution is invented. Until that time, you're bricked
---------- Post added at 10:08 PM ---------- Previous post was at 10:06 PM ----------
On a side note - can I flash 4.1 compatible ROMs on a 4.1 bootloader using the newest patched 2.4.4.0 TWRP without getting into trouble?
Ti2 said:
How are you trying to downgrade? Can you get to the booloader? If yes, try this:
In bootloader, wipe data
Reboot into bootloader
Then, using fastboot, flash system blob from Asus stock ROM using fastboot (fastboot -i 0x0b05 flash staging blob)
If that succeeds, flash appropriate TWRP from bootloader using fastboot, then flash bootloader compatible ROM
If it only (re)boots to recovery, then you'll have to hang in there until a solution is invented. Until that time, you're bricked
---------- Post added at 10:08 PM ---------- Previous post was at 10:06 PM ----------
On a side note - can I flash 4.1 compatible ROMs on a 4.1 bootloader using the newest patched 2.4.4.0 TWRP without getting into trouble?
Click to expand...
Click to collapse
thanks for yr reply ill try even im bricked! ill by another tabelt but not asus, maybe samsung, i have a GS2 , i install every thing without problem, i think there tables dont brick easly! true?
You wouldn't be bricked if you had read the instructions and followed them to the letter (and ask questions when unsure).
With that in mind - you can just as easily brick any device.
Ti2 said:
You wouldn't be bricked if you had read the instructions and followed them to the letter (and ask questions when unsure).
With that in mind - you can just as easily brick any device.
Click to expand...
Click to collapse
No that's just wrong for a bunch of people. At the time I did it. There was no warning, no indication of any problems. Just decided to do it at the wrong time. If it was 1 day later, I would have seen the bricked threads or had the patched TWRP.
sevenalive said:
No that's just wrong for a bunch of people. At the time I did it. There was no warning, no indication of any problems. Just decided to do it at the wrong time. If it was 1 day later, I would have seen the bricked threads or had the patched TWRP.
Click to expand...
Click to collapse
Wrong? No.
Harsh? Yes.
Read read read. Learn learn learn. Then read some more. When unsure, ask questions. Don't just try, then read the manual tot learn how you screwed up...
I am unsure tot flash 4.1 bootloader based roms through the 4.2 patched TWRP. I am NOT just going to try, I am awaiting an answer for 3 days now.
Is a Tab(2) as easily to brick as a Transformer? Yes it is.
sevenalive said:
No that's just wrong for a bunch of people. At the time I did it. There was no warning, no indication of any problems. Just decided to do it at the wrong time. If it was 1 day later, I would have seen the bricked threads or had the patched TWRP.
Click to expand...
Click to collapse
true wht u said !
Not trying to be harsh but that's why they call it "bleeding edge". You take the risks if you cannot be patient.
Sent from my SCH-I510 using xda app-developers app
hi,
did you try to use TWRP 2.4.4.0 - 4.2 this is the only one can read and write the sdcard on my TF300t after update to 4.2.1 good luck
lk2l said:
hi,
did you try to use TWRP 2.4.4.0 - 4.2 this is the only one can read and write the sdcard on my TF300t after update to 4.2.1 good luck
Click to expand...
Click to collapse
no succes to flash anything! always back to cwm 6.0.2.3...
when you type fastboot devices or adb devices can you see the device?
lk2l said:
when you type fastboot devices or adb devices can you see the device?
Click to expand...
Click to collapse
i can see this 0123456789ABCDEF, thts not the device name sure! isn't ? i can flash via fastboot ( sending ok, flashing ok) i flashed the blob file tht comes with the Asus frimwork 10.6.1.8 but nothing, always i go back to the 6.0.2.3 CWM! i flashed the twrp.blob file! same thing! im turning in an empty circle! good for trash??
depend if the code you write is only an example probably it is, is the device code.
don't worry until you can see the device you should be able to fix it... only thing is to found how
lk2l said:
depend if the code you write is only an example probably it is, is the device code.
don't worry until you can see the device you should be able to fix it... only thing is to found how
Click to expand...
Click to collapse
hope so! thkssssssssssssssssssssss
can you tell me which procedure you do to flash the recovery?
here you can found all I have used to flash my tf300t with the bootloader 4.2.1
fastboot+twrp recovery 2.4.4.0-4.2
is possible your fastboot dosen't work correctly?
I am far from a developer but I pulled the stock kernel for JSS15J, decompiled it and under "default.prop" edit
Code:
ro.secure=1 to ro.secure=0
and
Code:
ro.adb.secure=1 to ro.adb.secure=0
(probably super unsafe)
Recompiled and this booted just fine on my N7(2013), although size did change dramatically?
Anyway, didn't do any other wizardry, as I really don't know any. Hence, why I am attaching the stock kernel as well for actual wizards to perform on.
Stock and Insecure.zip This is hosted on Mega
Full /system /boot and /recovery: http://forum.xda-developers.com/showthread.php?t=2381438
Can you upload system.img too
Yeah, please upload the system.img, I am very curious about it Have a nice day.
nutzu4ever said:
Yeah, please upload the system.img, I am very curious about it Have a nice day.
Click to expand...
Click to collapse
Here you go
CLICK HERE
Credit to Nburnes
phuduong said:
Here you go
CLICK HERE
Credit to Nburnes
Click to expand...
Click to collapse
That's really helpful. Could you also pull the stock recovery if you still have it? The one that's floating around on xda is TWRP masquerading as stock.
dexgen said:
That's really helpful. Could you also pull the stock recovery if you still have it? The one that's floating around on xda is TWRP masquerading as stock.
Click to expand...
Click to collapse
If you tell me what to do, I'll pull the stock recovery for you.
gksmithlcw said:
If you tell me what to do, I'll pull the stock recovery for you.
Click to expand...
Click to collapse
I'm no expert but I think you'd find it here:
/dev/block/platform/msm_sdcc.1/by-name/recovery
But only if you haven't flashed any other recovery.
dexgen said:
I'm no expert but I think you'd find it here:
/dev/block/platform/msm_sdcc.1/by-name/recovery
But only if you haven't flashed any other recovery.
Click to expand...
Click to collapse
Hmm... Pulled up ADB Shell and ls'd that directory and just got an echo of the path back. Tried an ADB pull for the hell of it and got an error stating it remote object was not a file or directory.
gksmithlcw said:
Hmm... Pulled up ADB Shell and ls'd that directory and just got an echo of the path back. Tried an ADB pull for the hell of it and got an error stating it remote object was not a file or directory.
Click to expand...
Click to collapse
You can take a look at this: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
Also, can you just check to see if you have /system/recovery.img on your device? It might be the fastest way.
dexgen said:
You can take a look at this: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
Also, can you just check to see if you have /system/recovery.img on your device? It might be the fastest way.
Click to expand...
Click to collapse
No recovery.img in the ls of /system; I have recovery-from-boot.p. I'll check the link.
---------- Post added at 05:23 PM ---------- Previous post was at 05:20 PM ----------
dexgen said:
You can take a look at this: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
Also, can you just check to see if you have /system/recovery.img on your device? It might be the fastest way.
Click to expand...
Click to collapse
It looks like I need root to do this and, of course, to gain root I have to flash a custom recovery SO I think we're out of luck until Google posts factory images.
If anyone knows how to do it without root, I'll gladly try it.
gksmithlcw said:
No recovery.img in the ls of /system; I have recovery-from-boot.p. I'll check the link.
---------- Post added at 05:23 PM ---------- Previous post was at 05:20 PM ----------
It looks like I need root to do this and, of course, to gain root I have to flash a custom recovery SO I think we're out of luck until Google posts factory images.
If anyone knows how to do it without root, I'll gladly try it.
Click to expand...
Click to collapse
Just an FYI that you can access the stock recovery after rooting. The 'file' you mentioned: "recovery-from-boot.p" causes your custom recovery to revert back to stock after a reboot. If you've rooted a Nexus you may recall that one of the first steps is to change that file to "recovery-from-boot.p.bak" (or similar) so that your system will retain the custom recovery. My point is that you can root with TWRP or CWM, reboot and you'll revert back to the stock recovery. (You don't lose root, just the custom recovery). Pull the stock recovery.img and then flash your preferred custom recovery again. The 2nd time you'll want to change the file to "recovery-from-boot.p.bak" so that you don't revert back to stock again. Make Sense?
swest6602 said:
Just an FYI that you can access the stock recovery after rooting. The 'file' you mentioned: "recovery-from-boot.p" causes your custom recovery to revert back to stock after a reboot. If you've rooted a Nexus you may recall that one of the first steps is to change that file to "recovery-from-boot.p.bak" (or similar) so that your system will retain the custom recovery. My point is that you can root with TWRP or CWM, reboot and you'll revert back to the stock recovery. (You don't lose root, just the custom recovery). Pull the stock recovery.img and then flash your preferred custom recovery again. The 2nd time you'll want to change the file to "recovery-from-boot.p.bak" so that you don't revert back to stock again. Make Sense?
Click to expand...
Click to collapse
It's been awhile since I unlocked my G-Nex and rooted it but I do recall this. I'm hoping CWM for the new N7 shows up quickly.
gksmithlcw said:
It's been awhile since I unlocked my G-Nex and rooted it but I do recall this. I'm hoping CWM for the new N7 shows up quickly.
Click to expand...
Click to collapse
TWRP is out. I haven't tried it, but there is a How To started in General and there is a download link.
Sent from my Nexus 7 using Tapatalk HD
swest6602 said:
TWRP is out. I haven't tried it, but there is a How To started in General and there is a download link.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Oh, I know. I'd rather wait for CWM Touch. Thanks for the link though.
gksmithlcw said:
Oh, I know. I'd rather wait for CWM Touch. Thanks for the link though.
Click to expand...
Click to collapse
Did you see this link: http://forum.xda-developers.com/showthread.php?t=2381544
Brenex said:
Did you see this link: http://forum.xda-developers.com/showthread.php?t=2381544
Click to expand...
Click to collapse
I did, thank you!
Brenex said:
Did you see this link: http://forum.xda-developers.com/showthread.php?t=2381544
Click to expand...
Click to collapse
Flashed CWM through fastboot working fine. I prefer CWM myself. Thanks!
You can also just BOOT into recovery w/o flashing it (fastboot boot recovery <blah.img>. I did this with TWRP and backed up the device's system/boot/recovery.
I assume that would have backed up the original recovery right?
What does insecure means for a kernel?
Sent from my Nexus 7 using Tapatalk 4 Beta
casonswag said:
What does insecure means for a kernel?
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
It allows ADB to run as root on the devices.
This is really a useful feature for Developers because it allows simplier access to the file system... For Example...
With an unsecure image you can do... "ADB Pulls" and pull files from the /data/ partition on the device (I forget if you can do that or not on a secure image)
But you can also do ADB push which to me is essential because I may be working on, lets say, a custom battery mod or a customer XXXXXXX. And instead of putting it in a flashable zip and flashing it each time I can use an "ADB push" command to push the file where I want it.
Unsecure may not do much for average Joe building ROMS but this is quintessential for developers.
Got it? Good!
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.
Hello,
I hope this is the right spot for asking for help.
I had rooted my Samsung Galaxy S7 a few months ago, but 2 days ago I decided to uninstall my Magisk Root.
I decided to completely restore my Phone, but I chose the wrong restore in TWRP and I deleted everything on my phone.
I noticed my phone said that it didn't have any OS installed, and I feared the worse.
I couldn't start my phone without going straight into TWRP recovery, and I can't access the downloading modus.
Could anyone give me advice/help me getting my phone back into stock rom?
I have discord, skype and I can talk here on this forum.
With kind regards,
Bokees
Ty it got solved
bokees said:
Ty it got solved
Click to expand...
Click to collapse
good if you get this situation again try one of the following
1-use jig to enter download mode
2-flash bootloader files from stock rom (useing dd command which have the form dd if=/file path of=/path to the partition in the device)
---------- Post added at 12:15 AM ---------- Previous post was at 12:11 AM ----------
bokees said:
Ty it got solved
Click to expand...
Click to collapse
use dd command while you are in the custom recovery mode(adb mode with root access is enabled)