Related
Trying to install a leak thru stock recovery. Does anyone Known how to get past that issue? Thanks
Jake
themadzionist said:
Trying to install a leak thru stock recovery. Does anyone Known how to get past that issue? Thanks
Jake
Click to expand...
Click to collapse
As far as I can tell, I believe it means you're rooted still. I had the same problem so I Odin'd stock UVALH2 and then installed the leak without issue.
Not trying to hijack this thread but have been wondering why do you guys try to install leaks throw stock recovery. It is super easy to root this phone. Why not root install custom recovery then jush flash leaks?
Sent from my SGH-T999
Because you have to be 100% stock to install the leaks. This is the source of the error btw op. Prob not root but a custom recovery. Must be stock everything, modem and kernel must match too.
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
Because you have to be 100% stock to install the leaks. This is the source of the error btw op. Prob not root but a custom recovery. Must be stock everything, modem and kernel must match too.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
This is just not true. I install those OTA leaks every time they are released. Never once used stock recovery to do it.
Aerowinder said:
This is just not true. I install those OTA leaks every time they are released. Never once used stock recovery to do it.
Click to expand...
Click to collapse
Same here, I didn't come from a stock rom. Oh well.
So are you flashing the deodexed roms then?
Im talking about the actual ota you download from somewhere like sammobile.
It patches the existing system (UVDLI8 patches UVALI5) if anything is modded in UVALI5 the patch wont work, or if it does it can cause problems.
If you're flashing roms from development section then yes you can flash normally with custom recovery. But those roms are based on the otas, they're not the actual otas themselves.
Sent from my SGH-T999 using xda app-developers app
I don't bother with TW custom roms. Not really my thing, but I understand why people might want them.
I flash the OTA updates from the link in my signature (sammobile) in order to pull modems. Although there hasn't been a point lately, because you are working at the speed of light. But I flashed UVALEM, UVALH2, I1, 2, 3, 4, 5, 6, you get the idea.
Are you using TWRP? That recovery might not work with the OTA updates, but I've proven myself, and through many other people, that you can indeed flash OTA leaks from sammobile with CWM Touch 6.0.1.2. I'm unsure about the workings of TWRP because I don't use it. I don't use it because I don't like the buggy keyboard.
Yeah i tried everyway possible. The only way that worked was going uvahl2 thru odin, and then thru stock recovery i applied the ota jb uvdli7 from external sd. It was the only way to get it to work. I think the reason why the error message was coming up was because even though i unrooted my phone, the phone status still said "modified". Once i reflashed hl2 and it didn't say modified it updated the leak.
I think its going to take a video to prove you don't need stock recovery for this operation.
Aerowinder said:
I don't bother with TW custom roms. Not really my thing, but I understand why people might want them.
I flash the OTA updates from the link in my signature (sammobile) in order to pull modems. Although there hasn't been a point lately, because you are working at the speed of light. But I flashed UVALEM, UVALH2, I1, 2, 3, 4, 5, 6, you get the idea.
Are you using TWRP? That recovery might not work with the OTA updates, but I've proven myself, and through many other people, that you can indeed flash OTA leaks from sammobile with CWM Touch 6.0.1.2. I'm unsure about the workings of TWRP because I don't use it. I don't use it because I don't like the buggy keyboard.
Click to expand...
Click to collapse
Lol! Im just usually online when they drop! Theres only been a couple where I wasn't.
If cwm touch recovery does flash these otas as is then it just means they've disabled the check the ota does to verify the system meets the requirements. Or they just disable the recovery check/patch to protect their own recovery. I hope its the latter.
Not saying it cant be done but till now I hadn't heard of it. I use TWRP (just personal preference) but actually never bothered to try with it becsuse too many people early on got errors like the OP when anything wasn't matching stock.
I use Mobile Odin for the otas since it not only allows me to meet the stock requirements but it also injects root so you never have to worry about rerooting or anything.
At this point I just want to know how CWM does the otas. Does it completely disable the system check, or just the recovery part of that check.
Sent from my SGH-T999 using xda app-developers app
The zip file still runs the verification process. I've always done it properly, so I don't know what a flashing failure looks like. I have a background in programming, and I'm an amateur for sure, but I suspect that when the update checks for stock recovery, it thinks CWM is the stock recovery. I'm not sure of the code behind this, but I equate it to user-agents in browsers. CWM is saying it is stock recovery, OTA update accepts that, or some such. Without seeing the code, I can't say for sure, but this is my guess.
You get the option to disable the recovery patch, and to keep root when you attempt to exit recovery after the OTA flash.
I never saw much use for Mobile Odin. I did buy it, because the dev is amazing, but I've never used it. It allows you to flash zip files? I've always just done it through CWM. I flash everything through CWM... even other recoveries.
However it does it, I guess it works. Only reason I wanted to know if it bypassed the entire check is because that could cause problems for the more inexperienced.
Yeah, I love Chainfires work. The ability to flash zips with Mobile Odin was just added a few weeks ago and has worked flawlessly for me.
Sent from my SGH-T999 using xda app-developers app
fix it
you need to flash your kernel to man. most stock kernel wouldnt work with cyanogenmod. Update your kernel with unofficial kernel that are compatible with your device
raaaaarrrr!!!
Has no one figured this out yet...i unrooted my phone using odin mobile ...then attempted to do the 4.3 manual update and im getting the same errors! this is bs...i even tried to use odin to flash mdl and it dint do anything to my phone. very unhappy.
atheistics1 said:
Has no one figured this out yet...i unrooted my phone using odin mobile ...then attempted to do the 4.3 manual update and im getting the same errors! this is bs...i even tried to use odin to flash mdl and it dint do anything to my phone. very unhappy.
Click to expand...
Click to collapse
Well, first, there is not an Odin flashable 4.3 file, but you said you tried to flash MDL? Not sure what this is exactly. The most likely issue is you are using an incompatible recovery. Probably one that is too old.
I think you are totally confused between odin flashable files and recovery flashable files....
Okay so maybe this will help...omni version is jfltecan...which is Canadian and my baseband is l720vpuemja ...that's sprint which my phone is...I'm getting no data...and I'm not able to revert back to 4.3 or 4.2.
Sent from my SGH-I337M using XDA Premium 4 mobile app
you should probably consider asking in your devices forum. if you use anything here youll likely brick.
Sent from my T-Mobile MyTouch 3G Slide(HTC Espresso) using Tapatalk 2
wolverine
themadzionist said:
Trying to install a leak thru stock recovery. Does anyone Known how to get past that issue? Thanks
Jake
Click to expand...
Click to collapse
Just downgrade to 4.0.4 and install cwm then flash it through it. it works for me.
Since ATT claims that they will be doing an OTA update tomorrow I'm wondering what will happen to my rooted phone. Do I install the update? Will it try and automatically install the update itself? If it does what will happen to my phone. I'm currently on the latest version of Clean ROM. Thanks for all the help in advance!
I am kinda curious about this also. I am just rooted tho , with the exploit method. No custom roms or anything. I unchecked the options and rebooted to get phone state normal and then checked for updates , but didn't find anything.
Sent from my SAMSUNG-SGH-I317 using xda premium
As long as u dont have custom recovery u will be able to get the update ....u will lose root thought....
Sent from my SAMSUNG-SGH-I317 using xda premium
---------- Post added at 08:57 AM ---------- Previous post was at 08:56 AM ----------
nuclearrage said:
I am kinda curious about this also. I am just rooted tho , with the exploit method. No custom roms or anything. I unchecked the options and rebooted to get phone state normal and then checked for updates , but didn't find anything.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
Lol cause there is no update yet
Sent from my SAMSUNG-SGH-I317 using xda premium
I am also rooted and using CleanRom 3.5. I am sure the build date for the current CleanRom will be newer than the AT&T build date supposedly coming today. I guess I won't be updating since they are only adding multiview and I already have it via CleanRom. When the day comes that 4.1.2 is pushed out by AT&T and an update is needed, will I need to unroot my phone to get that update or is there another method?
If you have a custom recovery and things frozen or deleted with titanium backup you must undo all of that and get a stock recovery and then use ota root keeper to temporarily hide the root and you should be ok
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Ahhh, Ok. Thanks!
I'm not sure why anyone would want to go back to stock if you have a custom rom already installed. Custom roms will always be a step or 2 ahead of the carrier releases. This current at&t update is only for multi window and whatever updates are released in the future are likely going to be available via custom roms long before the official carrier release anyway.
topshelf95 said:
I'm not sure why anyone would want to go back to stock if you have a custom rom already installed. Custom roms will always be a step or 2 ahead of the carrier releases. This current at&t update is only for multi window and whatever updates are released in the future are likely going to be available via custom roms long before the official carrier release anyway.
Click to expand...
Click to collapse
I was rooted, running CWM, and CleanROM 3.5. I went into recovery and flashed the stock rom and it automatically downloaded and installed the update even though i had a custom recovery. After the update was complete I lost root and had stock recovery. The official ATT 4.1.2 update is way slower than CleanROM 3.5 so Im rooting and flashing back. Also cant customize toggles like the international 4.1.2.
iDrummer3 said:
I was rooted, running CWM, and CleanROM 3.5. I went into recovery and flashed the stock rom and it automatically downloaded and installed the update even though i had a custom recovery. After the update was complete I lost root and had stock recovery. The official ATT 4.1.2 update is way slower than CleanROM 3.5 so Im rooting and flashing back. Also cant customize toggles like the international 4.1.2.
Click to expand...
Click to collapse
Interesting. I am running root stock with twrp. I removed root, but still have custom recovery (twrp). Flashing the update fails due to ro.secure==1 or something.
Did you do anything at all to prep for the update, maybe ta or hide root?
-----
I would love to help you, but help yourself first: ask a better question
http://www.catb.org/~esr/faqs/smart-questions.html
I got an update push today. I told it to go ahead, but it rebooted to twrp and stopped. Now Ive put back the stock recovery and everytime i hit update in settings nothing happens.
Sent from my SGH-T989 using Tapatalk 2
ackliph said:
I got an update push today. I told it to go ahead, but it rebooted to twrp and stopped. Now Ive put back the stock recovery and everytime i hit update in settings nothing happens.
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Well now you cant run an update with a custom recovery on board and since you started it there is prolly a file or the OTA server thinks you have it installed and is not offering it again.
Best thing to do on phones where you have custom recovery? Look here on the boards for the Stock ROIM of the version you want. If you wanted it un-rooted [no super user] then look in the returning to stock thread, if you want supersu (have your phone rooted) then look for a ROM of your choice based on the Android Version of your choice they range from hardly any changes [the ones that say only busybox and rooted are usually just stock ROM with just those 2 additions].
You want to use JB which Samsung has not even upgraded the T989 to yet [completely stable and I have been using it as my Daily Driver for month ].
First download ROM Manager from Market and have it flash CWM Recovery
Go to development section here and find the ParanoidAndroid thread and download the Nov 18 dated file and Gapps and flash those
Now you will have Android 4.1.2 - Jellybean! Enjoy
I have stock rooted 4.0.4 and it asked me to update. Do you think T-Mobile is releasing an update? Anyone else getting it?
I'd like to keep my wifi calling so i havent moved to a 4.1.2 rom.
Sent from my SGH-T989 using Tapatalk 2
ackliph said:
I have stock rooted 4.0.4 and it asked me to update. Do you think T-Mobile is releasing an update? Anyone else getting it?
I'd like to keep my wifi calling so i havent moved to a 4.1.2 rom.
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
I've been receiving an update as well. Problem is every time I go to update since my phone is rooted but running the stock rom, after i reboots to start the update it sends me to Clockwork Recovery...which actually brings me to ask my question here instead of starting a new thread. I really don't want to un-root since I make use of the cracked Google Play for a couple of my apps Do I really have to un-root just to receive T-Mobiles update?
- For android 4.3, there has been a lot of talk on the developer section, and from what I can see, the major bugs/issues have been fixed. Like the ROM not rebooting correctly. For those using 4.3, is this true?
- Also, from what I understand, this was due to the recoveries not being ready for 4.3, however CM released their own bare bone recovery to fix that issue. And then I've read that the TW recovery has also been updated to solve this problem.
-There is a lot of information in the development forums, but I have not seen any post on the steps on what to do in order to upgrade from 4.2 to 4.3.
-Right now I have CWM 5 recovery, because that's been working for me, and I never bothered changing (bad experience with trying to upgrade/change a recovery). Now from what I understand, I should be able to flash the newest touch recovery (via the goo app?), and then wipe and flash any 4.3 ROM. Any detail instructions would be a help, or if someone can create a tutorial post, that would be great.
Thanks in advance.
Here is a post I made yesterday about how I switched from 4.2 to 4.3
I hope it helps. I have been on hellybean 4.3 for two days and everything is running great.
http://forum.xda-developers.com/showpost.php?p=45021060&postcount=632
You could just install ROM Manager and update from there. It's super-easy (you need ROOT, but I presume you have that since you're flashing ROMs anyway). :good:
Sicily1918 said:
You could just install ROM Manager and update from there. It's super-easy (you need ROOT, but I presume you have that since you're flashing ROMs anyway). :good:
Click to expand...
Click to collapse
Many people have had bad experiences with ROM Manager. Especially in the Gingerbread days when its use was more common for this sort of thing.
Just my 2 cents.
monkeybuttons said:
Many people have had bad experiences with ROM Manager. Especially in the Gingerbread days when its use was more common for this sort of thing.
Just my 2 cents.
Click to expand...
Click to collapse
Interesting -- always been good to me, although I only use it to update the recovery; for the ROM itself I use Cyanogen's update util. I also use CWM, not TWRP, so there's that...
bobiscool07 said:
- For android 4.3, there has been a lot of talk on the developer section, and from what I can see, the major bugs/issues have been fixed. Like the ROM not rebooting correctly. For those using 4.3, is this true?
- Also, from what I understand, this was due to the recoveries not being ready for 4.3, however CM released their own bare bone recovery to fix that issue. And then I've read that the TW recovery has also been updated to solve this problem.
-There is a lot of information in the development forums, but I have not seen any post on the steps on what to do in order to upgrade from 4.2 to 4.3.
-Right now I have CWM 5 recovery, because that's been working for me, and I never bothered changing (bad experience with trying to upgrade/change a recovery). Now from what I understand, I should be able to flash the newest touch recovery (via the goo app?), and then wipe and flash any 4.3 ROM. Any detail instructions would be a help, or if someone can create a tutorial post, that would be great.
Thanks in advance.
Click to expand...
Click to collapse
Ur best and safest approach would be to DL Odin and the drivers for ur phone, then go to techerrata.com/browse/twrp2/hercules and DL twrp2.6.0.4, this is the 4.3 compatible version, then put ur device in DL mode and connect to odin, load the tar file in PDA and click start, 30 sec and u have the latest and greatest twrp recovery, now go get hellybean 4.3 or beanstalk4.3 and flash it, watch the beauty take place...
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
I updated my rom today like I usually do from the CMUpdater and it updated from 4.2 to 4.3. I didn't mean or want to do that, but it didn't tell me otherwise. Now I'm having issues left and right......the one time I don't back it up...grrr.
I'm having the most issues with Gapps. I downloaded the new one and installed it and Google Music and Youtube keeps crashing. I guess I'll be doing the full wipe now.
Did u update to 4 3 gapps? It won't do it automatically, even if u updated through goo it just looks at what version is installed and updates that version, 4.3 gapps can be found in any 4.3 thread
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
soupysoup said:
Ur best and safest approach would be to DL Odin and the drivers for ur phone, then go to techerrata.com/browse/twrp2/hercules and DL twrp2.6.0.4, this is the 4.3 compatible version, then put ur device in DL mode and connect to odin, load the tar file in PDA and click start, 30 sec and u have the latest and greatest twrp recovery, now go get hellybean 4.3 or beanstalk4.3 and flash it, watch the beauty take place...
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Why do some of those files say hercules, and others sgh-t989? Aren't they the same phone?
Just wondering. I know that by installing a custom ROM we wont get official updates.
But what If I am using the stock ROM and I just rooted using TWRP will I still be able to get an Official Update if I flash it using Odin?
Im afraid of flashing custom ROMs because back on my Note 10.1 (old version) when I flashed Custom ROMs It broke the allsharecast feature.
Recovery is separate from Rom... heck... even kernel difference I THINK won't break OTA update, as long as ROM is stock.
Now with this beingWiFi only... will there even BE an auto update? Or will it have to be manual.
AestenD said:
Recovery is separate from Rom... heck... even kernel difference I THINK won't break OTA update, as long as ROM is stock.
Now with this beingWiFi only... will there even BE an auto update? Or will it have to be manual.
Click to expand...
Click to collapse
I doubt OTA will work though. But maybe can still download the official rom and flash via Odin manually
Maybe I can answer some of your questions? OTA updates are not only for devices on a mobile network. Our device will get the updates when on wifi, and the only limit or this to work properly is the fact that it is a custom ROM. A rooted device is not a limit, but it can (with the emphasis on *can*) cause a boot problem as a new ROM comes with a new recovery image. Therefore my advice is to use the various writeups in the Android development forum to understand the options to go rooted and back. Since this is a more general forum I suggest to ask your questions there too.
Sent from my SM-P600 using XDA Premium 4 mobile app