Related
I ran the causal root applet on a new SG3 on 4.1.2. Ran root, the unlock script and installed TWRP. Booted into recovery and I got the error for a locked bootloader. I used download mode to get back to the stock rom and then used E-Z unlock to unlock the bootloader. Was able to boot into recovery this time but TWRP read internal and external memory as 0mb, unable to make a backup, and gave a no OS error when went to reboot. I updated TWRP with TWRP manager but the problems are still persistent. Phone boots fine and reboots fine at the moment.
I'm not sure what to do now though. I'm at the point were I don't care if I get stuck with the OTA update but I'm afraid that will brick the phone. I'm not sure what went wrong with TWRP, since this is the second S3 I've rooted.
Any sugestions? I'm afraid to use odin or try anything else since the phone currently works fine. But I'd prefer to not have to sleep in fear it might force the OTA update while I'm asleep and wake up to a bricked phone.
I tried searching, the best I could find is that newer versions of TWRP can't read the memory on a 4.1.2 rom, but the problems were there when I originally started with the recommended version.
Thanks for any help anyone can give.
Try to use cwm or philz and see if you have the same issue.
Sent from my SCH-I535 using Tapatalk 2
Xx
BadUsername said:
Try to use cwm or philz and see if you have the same issue.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Can you install a different custom recovery over one using the causal applet? I was planning on trying to reinstall TWRP but I wasn't sure if I had to do it a certain way like through odin or Using the unified tool kit?
Thanks for the help so far!
Smogon said:
Can you install a different custom recovery over one using the causal applet? I was planning on trying to reinstall TWRP but I wasn't sure if I had to do it a certain way like through odin or Using the unified tool kit?
Thanks for the help so far!
Click to expand...
Click to collapse
No.
Download latest philz touch recovery d2lte zip, then flash it in recovery, then reboot recovery.
Then check and see if you're getting a similar error message.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
No.
Download latest philz touch recovery d2lte zip, then flash it in recovery, then reboot recovery.
Click to expand...
Click to collapse
I can't, recovery doesn't detect my internal or external memory. That's my main issue.
Smogon said:
I can't, recovery doesn't detect my internal or external memory. That's my main issue.
Click to expand...
Click to collapse
OK.
Then download the Odin version and flash through that. Then boot the phone into recovery.
Or download ez recovery, and the latest cwm image file, and flash through that from your rom.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
OK.
Then download the Odin version and flash through that. Then boot the phone into recovery.
Or download ez recovery, and the latest cwm image file, and flash through that from your rom.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I'll try the second option, Thanks!
BadUsername said:
OK.
Or download ez recovery, and the latest cwm image file, and flash through that from your rom.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I tried CWM and the stock recovery through EZ, both gave the same error as TWRP, unable to mount /
I'm really confused as to whats wrong. At this point I don't care if I get stuck with the OTA 4.3, but I don't want to try to update it with the recovery still not reading either my SD cards.
Any Ideas?
Are you sure of your phone model? I believe it puts it on the screen in download mode and also on a sticker under the battery. I'm mostly curious because you mention that this is a new phone with 4.1.2. Are you trying older versions of cwm as well?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Smogon said:
I ran the causal root applet on a new SG3 on 4.1.2. Ran root, the unlock script and installed TWRP. Booted into recovery and I got the error for a locked bootloader. I used download mode to get back to the stock rom and then used E-Z unlock to unlock the bootloader. Was able to boot into recovery this time but TWRP read internal and external memory as 0mb, unable to make a backup, and gave a no OS error when went to reboot. I updated TWRP with TWRP manager but the problems are still persistent. Phone boots fine and reboots fine at the moment.
I'm not sure what to do now though. I'm at the point were I don't care if I get stuck with the OTA update but I'm afraid that will brick the phone. I'm not sure what went wrong with TWRP, since this is the second S3 I've rooted.
Any sugestions? I'm afraid to use odin or try anything else since the phone currently works fine. But I'd prefer to not have to sleep in fear it might force the OTA update while I'm asleep and wake up to a bricked phone.
I tried searching, the best I could find is that newer versions of TWRP can't read the memory on a 4.1.2 rom, but the problems were there when I originally started with the recommended version.
Thanks for any help anyone can give.
Click to expand...
Click to collapse
by any chance did u try to setup dualboot? I have a similar issue where nothing gets mounted and o mb for storage, .only receovery i get to work is cwm. im pretty sure its a partition issue but idk. i tried flashing pit files for my phone but so far the issue remains.
xevildoerxx said:
by any chance did u try to setup dualboot? I have a similar issue where nothing gets mounted and o mb for storage, .only receovery i get to work is cwm. im pretty sure its a partition issue but idk. i tried flashing pit files for my phone but so far the issue remains.
Click to expand...
Click to collapse
No I just used the causal tool.
dpeeps74 said:
Are you sure of your phone model? I believe it puts it on the screen in download mode and also on a sticker under the battery. I'm mostly curious because you mention that this is a new phone with 4.1.2. Are you trying older versions of cwm as well?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm pretty sure, has all the verizon bloat and logos, also I'm pretty sure the causal applet bricks the international ones. I don't remember the version of twrp that the causal script flashed, but I tried that one, the most recent one, and 2.5 i think from EZ recovery. The stock recovery from EZ has the same issue now though which is what really confuses me. at the moment I have root dissabled and the bootloader is locked and its back with the stock recovery, it still says custom when i reboot the phone though.
I'm on stock rooted 4.4.2 running Franco kernel. Question is how do I update with out bringing phone to factory settings
SENT FROM MY SM-N900T/NEXUS 5 USING TAPATALK
you make a backup in recovery, then dirty flash, dont wipe a single thing, 444 over it. if alls well after, then perfect. if you have issues, you have that backup in recovery to restore
simms22 said:
you make a backup in recovery, then dirty flash, dont wipe a single thing, 444 over it. if alls well after, then perfect. if you have issues, you have that backup in recovery to restore
Click to expand...
Click to collapse
I downloaded then tried to flash the zip file in twrp .. It says it failed not sure what to do next and is 4.4.4 the latest firmware?
SENT FROM MY SM-N900T/NEXUS 5 USING TAPATALK
ROADKING17 said:
I downloaded then tried to flash the zip file in twrp .. It says it failed not sure what to do next and is 4.4.4 the latest firmware?
SENT FROM MY SM-N900T/NEXUS 5 USING TAPATALK
Click to expand...
Click to collapse
Unfortunately my clairvoyant skills aren't working today
perhaps you could elaborate on the following 2 things
1) what zip are you flashing?
2) what error are you getting?
Sent from my Nexus 5 using Tapatalk
The pop up I get every 3 days for me to update my device to 4.4.3 I believe.. It's located in twrp under cache... When I try flashing it says error in red lettering ... Also I tried Uninstalling Xposed but seems not to change anything
SENT FROM MY SM-N900T/NEXUS 5 USING TAPATALK
ROADKING17 said:
The pop up I get every 3 days for me to update my device to 4.4.3 I believe.. It's located in twrp under cache... When I try flashing it says error in red lettering ... Also I tried Uninstalling Xposed but seems not to change anything
SENT FROM MY SM-N900T/NEXUS 5 USING TAPATALK
Click to expand...
Click to collapse
Don't use OTA updates. Just manually flash a rooted stock ROM via TWRP.
Click the link in my signature and go to the "resources" section. You'll find a full rooted, PURE STOCK 4.4.4 rom there.
Copy it to your /sdcard, take a FULL nandroid backup then flash the ROM.
rootSU said:
Don't use OTA updates. Just manually flash a rooted stock ROM via TWRP.
Click the link in my signature and go to the "resources" section. You'll find a full rooted, PURE STOCK 4.4.4 rom there.
Copy it to your /sdcard, take a FULL nandroid backup then flash the ROM.
Click to expand...
Click to collapse
Will I lose anything on my device and will I be able to dirty flash
SENT FROM MY SM-N900T/NEXUS 5 USING TAPATALK
ROADKING17 said:
Will I lose anything on my device and will I be able to dirty flash
SENT FROM MY SM-N900T/NEXUS 5 USING TAPATALK
Click to expand...
Click to collapse
did you read any of the threads? the answer is in there.
ROADKING17 said:
Will I lose anything on my device and will I be able to dirty flash
SENT FROM MY SM-N900T/NEXUS 5 USING TAPATALK
Click to expand...
Click to collapse
if the dirty flash is successful, you wont lose a thing, except time. if you have to go back and wipe, you will lose your data. so, make a backup in recovery first, before the dirty flash.
Is it possible to boot a recovery image from the phone without flashing? If not is it ok to reflash backups of stock recovery? Tnx
and313 said:
Is it possible to boot a recovery image from the phone without flashing? If not is it ok to reflash backups of stock recovery? Tnx
Click to expand...
Click to collapse
It is possible via android sdk. You can use command: fastboot boot twrp.img
where twrp.img is the name of the recovery that you downloaded and not twrp.img
Alexandar92zr said:
It is possible via android sdk. You can use command: fastboot boot twrp.img
where twrp.img is the name of the recovery that you downloaded and not twrp.img
Click to expand...
Click to collapse
Yes i know but i would like to do it from the phone... There are tons of flash recovery apps but no boot recovery apps
ROM manager used to do it years ago until people got into trouble with it and it was removed.
If you intend on flashing things AMD backing up, flash a recovery. If you're not willing to flash a recovery, don't modify your phone
Sent from my Nexus 5 using Tapatalk
and313 said:
Yes i know but i would like to do it from the phone... There are tons of flash recovery apps but no boot recovery apps
Click to expand...
Click to collapse
Try flashify
AndreIrawan97 said:
Try flashify
Click to expand...
Click to collapse
That flashes recovery. Clue is in the name.
Sent from my Nexus 5 using Tapatalk
rootSU said:
ROM manager used to do it years ago until people got into trouble with it and it was removed.
If you intend on flashing things AMD backing up, flash a recovery. If you're not willing to flash a recovery, don't modify your phone
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
The problem with flashing is that you loose the ota update ability. That's why i would like to keep the stock recovery and just boot into cwm when i need it... But i guess i can restore the stock recovery via flashify before the ota is being installed so thats a solution... I just dont like flashing this stuff via apps
and313 said:
The problem with flashing is that you loose the ota update ability. That's why i would like to keep the stock recovery and just boot into cwm when i need it... But i guess i can restore the stock recovery via flashify before the ota is being installed so thats a solution... I just dont like flashing this stuff via apps
Click to expand...
Click to collapse
1) you do not lose OTA update ability with custom recovery. Read "OTA help-desk" available via my signature
2] what's the big deal about OTA? Its the worst way of updating available to everyone. Why bother? If you rely on OTA, remain unrooted, unmodified. Rooting is not for you.
Sent from my Nexus 5 using Tapatalk
Ugh lol OK, so worried about the ota? No worries, flash whatever recovery you want twrp,cwm,philz whatever floats your boat. Then when your ota comes out use Rashr to reflash stock recovery so you can update(you have to be on stock obviously).
I've done this numerous times, works every time.
Sent from my Nexus 5 using XDA Free mobile app
todorcim said:
Ugh lol OK, so worried about the ota? No worries, flash whatever recovery you want twrp,cwm,philz whatever floats your boat. Then when your ota comes out use Rashr to reflash stock recovery so you can update(you have to be on stock obviously).
I've done this numerous times, works every time.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
One of the problems with OTA is the slow delivery and partial nature.
If I wasn't rooted, i'd always update using factory images. But since I am, the best way is for flash a pre-rooted stock ROM via recovery. They're usually available within an hour of the factory image becoming available
Sent from my Nexus 5 using Tapatalk
rootSU said:
One of the problems with OTA is the slow delivery and partial nature.
If I wasn't rooted, i'd always update using factory images. But since I am, the best way is for flash a pre-rooted stock ROM via recovery. They're usually available within an hour of the factory image becoming available
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Agreed 100%, I normally stay rooted,this most recent preview though I'm staying stock. After running L for the last couple months its hard to go back to KitKat(I've tried several times). I have no intention of flashing another rom atm, I'll worry about root after the 3rd.
As for buddy worrying about the ota, really you have two choices.
#1 root and flash a recovery then wait for someone to post a root stock ROM
#2 wait for the ota
The only real benefit I see in waiting for the ota is you will probably get to keep all your apps on your phone. Me personally? I'd just fastboot the preview and wait till the 3rd.
Materialized From The DarkSide
So I installed the lateat CM12 nightly, wasn't really impressed yet and went to go restore my backup and once it's done restoring, it get stuck at the bootscreen animation. Just keeps going and going abs going. I used the latest cwm touch recovery as CM12 is not compatible with MultiROM. I would just flash the factory img back but my computer decided to it doesn't ever want to recognize adb avid fastboot on Linux.
Anyone know where I can find a flashable zip for the factory 5.0.1 ROM? Any help would be appreciated!
Try googling Nexus 5 factory image...
Here's a flashable 5.0 : http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523
Niflheimer said:
Here's a flashable 5.0 : http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523
Click to expand...
Click to collapse
Now I'm assuming I'd have to unroot it and flash stock recovery and lock the bootloader to get it to update to 5.0.1?
No, it's flashable in your custom recovery. It's 5.0 though
Sent from my Nexus 5 using XDA Free mobile app
Yeap , ota needs stock recovery. Also , switch to twrp since cwm isn't playing nice with L.
jd1639 said:
No, it's flashable in your custom recovery. It's 5.0 though
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I was talking about the 5.0.1 update but thanks.
Niflheimer said:
Yeap , ota needs stock recovery. Also , switch to twrp since cwm isn't playing nice with L.
Click to expand...
Click to collapse
I'm on the stock ROM you linked too, stock recovery, and unrooted but, when I get the update for 5.0.1 and try and install it, I get an error. Do I need to relock my boatloader?
asd87 said:
I'm on the stock ROM you linked too, stock recovery, and unrooted but, when I get the update for 5.0.1 and try and install it, I get an error. Do I need to relock my boatloader?
Click to expand...
Click to collapse
You're on a custom Rom. The ota isn't going to work. And you don't need to relock your bootloader. If you can afford to wipe your data download the 5.0.1 factory image. Extract it and use the flash-all.bat
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
You're on a custom Rom. The ota isn't going to work. And you don't need to relock your bootloader. If you can afford to wipe your data download the 5.0.1 factory image. Extract it and use the flash-all.bat
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
My computer is Linux, and adb and fastboot for whatever reason unknown to me, won't install. That's why I asked for a zip file of the factory image. Thanks for the help though.
asd87 said:
My computer is Linux, and adb and fastboot for whatever reason unknown to me, won't install. That's why I asked for a zip file of the factory image. Thanks for the help though.
Click to expand...
Click to collapse
Well, unfortunately, there isn't a 5.0.1 flashable rom available right now. If you can't get fastboot to work on your Linux machine you're kind of sol as you need to be 100% stock to get the ota to work. That means stock recovery in your case. Google recovery zip collection xda. There's a custom recovery flashable stock recovery there.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Well, unfortunately, there isn't a 5.0.1 flashable rom available right now. If you can't get fastboot to work on your Linux machine you're kind of sol as you need to be 100% stock to get the ota to work. That means stock recovery in your case. Google recovery zip collection xda. There's a custom recovery flashable stock recovery there.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I have the stock 5.0 recovery that I installed through Flashify. I'll barrow a windows computer or something lol
asd87 said:
I have the stock 5.0 recovery that I installed through Flashify. I'll barrow a windows computer or something lol
Click to expand...
Click to collapse
I'd work on getting adb/fastboot working on your Linux machine. You're going to need it in the long run.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I'd work on getting adb/fastboot working on your Linux machine. You're going to need it in the long run.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I've spent hours trying to get it work one night. I'll do some note searching for more advice and again thanks.
jd1639 said:
I'd work on getting adb/fastboot working on your Linux machine. You're going to need it in the long run.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Did some more digging, got it install, and flashed the factory img for 5.0.1 and twrp recovery then superSU through twrp.
Mods please lock the thread thanks.
Get wugfreshes Toolbox. It has access to all factory images. Some people are not fans of "one click solutions" but this has never let me down.
There's a flushable zip on here also. Put it in a search in the app and you should come across it. It IS the full version.
Did you ever find out why the CWM restore led to getting stuck on boot animation??
Just ran into this last night. Tried restoring 2 different CWM backups and both got stuck on boot animation.
I eventually got a new ROM flashed. Going to try TWRP recovery I suppose.
I know I never had this problem with 4.4, this was the first time I have restored a LP ROM..
one7dchevy said:
Did you ever find out why the CWM restore led to getting stuck on boot animation??
Just ran into this last night. Tried restoring 2 different CWM backups and both got stuck on boot animation.
I eventually got a new ROM flashed. Going to try TWRP recovery I suppose.
I know I never had this problem with 4.4, this was the first time I have restored a LP ROM..
Click to expand...
Click to collapse
My guess would be; cwm hasn't been optimized for Lollipop. Cyanogen has just recently started working on 5.0 and they probably haven't touched the recovery too much. But that's just my guess.
asd87 said:
My guess would be; cwm hasn't been optimized for Lollipop. Cyanogen has just recently started working on 5.0 and they probably haven't touched the recovery too much. But that's just my guess.
Click to expand...
Click to collapse
Yea figured something like that.
Got TWRP installed, will try to update after my next nandroid restore so that any old CWM users will know..
So I had my phone rooted, with TWRP recovery, and today I've received a notification for 5.1 update, and when I pressed Install and reboot, it rebooted directly into TWRP, so I can't update it (or didn't find a way). Is there any way to update it now without wiping data?
There's a whole thread on the ota process in the general forum. You should read it. The ota will not work with a custom recovery. You need the stock recovery which you can install using fastboot. There are other requirements too. You have to be 100% stock system, kernel and recovery.
Sent from my Nexus 5 using XDA Free mobile app
Just flash the ota zip via twrp you will loose all root and your system modifiactions which are reversible!
bhavstech said:
Just flash the ota zip via twrp you will loose all root and your system modifiactions which are reversible!
Click to expand...
Click to collapse
It won't work with 5.x. You need the stock recovery.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
it won't work with 5.x. You need the stock recovery.
Sent from my nexus 5 using xda free mobile app
Click to expand...
Click to collapse
oh i didnt know that thanks!
AlexSRB said:
So I had my phone rooted, with TWRP recovery, and today I've received a notification for 5.1 update, and when I pressed Install and reboot, it rebooted directly into TWRP, so I can't update it (or didn't find a way). Is there any way to update it now without wiping data?
Click to expand...
Click to collapse
See quote below.
Elluel said:
download new factory images
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
boot into custom recovery
then flash SuperSU/other stuff if desired
Click to expand...
Click to collapse