Hi!
I have flashed JB according to this Topic http://forum.xda-developers.com/showthread.php?t=1911024 on my unlocked TF201 wich already was prepared with NVFlash. Everything seems to be fine and JB runs rather good. The problem is that I cannot access Recovery anymore. I had CWM installed and when I tried to boot into it I always got the red Andy. I tried to flash CWM and TWRP with several methods but with no success. Now it always stops at "Booting to recovery"note after selecting RCK. JB itself still runs well.
Anyone can tell me how I can regain access to CWM or TWRP?
Thanks
Gr0mit
me either ,, tried everything to get one on my prime too . not even fastboot method adds it . stuck now with no root or anything
adz63 said:
me either ,, tried everything to get one on my prime too . not even fastboot method adds it . stuck now with no root or anything
Click to expand...
Click to collapse
I guess I'm #3 here. I've tried doing stock recovery no dice. However the JB rom I installed is working fine (full stock dedoxed from devel thread)
However I really wanna get some wookie on here
How to do it is on one of these threads if people like you would llook on the forum instead of posting and spamming the boards. We would not have all these problems. Go look through all the thread about this subject and you will find it. :cyclops:. Sorry for being rude I so tired of looking through all the threads on this subject when i know only one thread actually has the answer
If you have nvflash try this:
Enter APX mode [Power + Vol-Up]
wheelie --blob blob.bin
nvflash -r --download 5 recovery.img
nvflash -r --go
You need flash only recovery for JB.
schlesh436 said:
How to do it is on one of these threads if people like you would llook on the forum instead of posting and spamming the boards. We would not have all these problems. Go look through all the thread about this subject and you will find it. :cyclops:. Sorry for being rude I so tired of looking through all the threads on this subject when i know only one thread actually has the answer
Click to expand...
Click to collapse
Not one of the threads on here work for me . Tried them all over and over again . Not even anything from about 20 pages of a Google search work either
Sent from my GT-I9300 using Tapatalk 2
The link in the first post to craig gomez's rom has a link to twrp recovery and instructions of how to install it.. don't try CWM yet and don't try recoveries meant for ICS.. might brick your prime
schlesh436 said:
How to do it is on one of these threads if people like you would llook on the forum instead of posting and spamming the boards. We would not have all these problems. Go look through all the thread about this subject and you will find it. :cyclops:. Sorry for being rude I so tired of looking through all the threads on this subject when i know only one thread actually has the answer
Click to expand...
Click to collapse
I've spent several days going through posts and trying different "howto" instructions with no luck. My prime is running the first stock rooted JB I grabbed from here. Glad you're having better luck than we are. I went from the androwookie JB (non-tf201 rom) to the stock tf201 rooted rom and now I can't get a recovery back on. The rom still boots just can't get another rom on at the moment. If you were sorry for being rude you wouldn't have been rude in the first place lol.
Hi,
Now I found a solution with the Fresh Root script from this post
http://forum.xda-developers.com/showthread.php?t=1929189
It gave me TWRP and JB is still running! PERFECT! :good:
Greetings
gr0mit72
Related
Hello,
sorry for my poor english.
I have a new tf201 and have it unlocked with the orig asus tool.
after unlocking i installed clockwork recovery 5.8.2 and then flashing
aokp_TFP_b34_v1.4.1. The tf201 don´t starts.
Then i flashed again, the same problem.
I do wiping the partitions, and now i have the Problem, nothing runs,
no access to sdcard, no access from PC to internal storage.
I have used WSG UnBricker V1.0.2 und flashing of system.img failes (0x4)
What can i Do?
Thanks for Your Help.
Countryman
Wrong section my friend, go to Q&A. This has been discussed before, please search and read before posting questions. ope the mods move this before you get flamed
loveableterrorepic4g said:
Wrong section my friend, go to Q&A. This has been discussed before, please search and read before posting questions. ope the mods move this before you get flamed
Click to expand...
Click to collapse
People always say that but nobody ever gets flamed anymore with the banhappy mods around.
Follow diamond's backs thread in development
Sent from my Transformer Prime TF201 using XDA
ountryman said:
Hello,
sorry for my poor english.
I have a new tf201 and have it unlocked with the orig asus tool.
after unlocking i installed clockwork recovery 5.8.2 and then flashing
aokp_TFP_b34_v1.4.1. The tf201 don´t starts.
Then i flashed again, the same problem.
I do wiping the partitions, and now i have the Problem, nothing runs,
no access to sdcard, no access from PC to internal storage.
I have used WSG UnBricker V1.0.2 und flashing of system.img failes (0x4)
What can i Do?
Thanks for Your Help.
Countryman
Click to expand...
Click to collapse
check my post http://forum.xda-developers.com/showthread.php?t=1514088&page=25
Hello,
Thank You to the Mods for Moving this Thread
and Thanky You schlesh436 and captsakis for the Answers.
Reading of the threads from diamondback and Capsakis brings me not the Solution.
My Problem is big. CWM Bootloader is Broken. Asus Bootloader ist not present.
I Can´t flash Bootloader with fastboot. The Flash Method via microsd is not possible. I Have just 2 Icons on the Screen, (Fastboot usb & Wipe DATA).
Any Help available?
Or must i send my tf201 to Asus?
Thanks for the Help...
Countryman
same here
I'm in the same situation. But when I run the unbricker, it only says must be in bootloader mode to use this even though I'm in bootloader on the prime. In fact, that's the only thing I can do at present.
Update: I managed to get it working again through trial and error. 1rst thing very important, do not use Unbricker! The only thing that works is wiping partitions and made things a lot harder for me.
If your like me your prime can only go into fastboot mode, so use it to reflash your recovery partition. Then it still wouldn't boot because bootloader was broken. I discovered quite by accident that using ubuntu installer from lilstevie restored my bootloader!!!
From then on it's pretty strait forward to boot into recovery and use a rom from your /sdcard to reinstall system. But if like me you wiped your user data, you can simply plug the prime to your pc and adb push a new rom file to flash.
Link for ubunto
Can you give me the link for ubuntu.
Tips on how to search for things such as Ubuntu :
go to www.google.com
Type search in bar.
Profit.
Alternate route :
type www.ubuntu.com
Crazy, I know!!!
Nightpath said:
Tips on how to search for things such as Ubuntu :
go to www.google.com
Type search in bar.
Profit.
Alternate route :
type www.ubuntu.com
Crazy, I know!!!
Click to expand...
Click to collapse
don't be an ass; they were asking about how to get to the ubuntu installer for prime;
http://forum.xda-developers.com/showthread.php?t=1603921
from what i've seen though, even in ubuntu, you'd need a fastboot mode or a blob image; if you can just get into apx mode and that's all, you may be hosed... as i am...
Hello, i've been using these forums in particular the Samsung Galaxy S2 thread "
[Rom] AOKP(Jellybean 4.1.2) | Task650 & Ktoonsez (11/9)" for awhile now, probably going on a year. Just today i tried updating to the aforementioned update in that thread from 11/9, and while installing the ROM segment, i got an Error, and said installation aborted, tried once more, same thing, upon trying to reboot my phone it is now stuck in an endless reboot loop, which is why i believe it is bricked. I have found sites that tell me to get back to the stock rom, since i believe that is my only option now, but first and foremost id like to know how to manually get into recovery mode.
Other sites have said holding down Home Volume Up and Power simultaneously will do this, i've tried multiple times, hasn't worked, so unless there's something i'm missing there i'd love to know if there is some other way. Also if there is anything i can do besides simply going back to stock ROM which is a long and drawn out process Id love to know.
Thank you for ANY and all answers in advance.
First off, make sure you have the i777. I know you said you've been using Tasks' AOKP rom, but forgive us for not trusting you yet. Too many people are trying to flash roms that aren't built for their model.
Secondly, recovery mode is volume up AND down, while holding the power for the i777. Hold all three until you get into recovery.
Also, what sort of error did you get? If you can get into recovery your phone isn't bricked.
Sent from my i777
4thCrater said:
First off, make sure you have the i777. I know you said you've been using Tasks' AOKP rom, but forgive us for not trusting you yet. Too many people are trying to flash roms that aren't built for their model.
Secondly, recovery mode is volume up AND down, while holding the power for the i777. Hold all three until you get into recovery.
Also, what sort of error did you get? If you can get into recovery your phone isn't bricked.
Sent from my i777
Click to expand...
Click to collapse
I've been flashing form this thread for nearly a year as i mentioned so i definitely have the right model, i'm not sure what type of error it was, all i know it it said something like E:/Error cancellation aborted.
Ok in the midst of posting this i finally got into recovery thank you, and i tried reinstalling again. it says "Installing Update...
Symlink: some symlinks failed
E:Error in /emmc/aokp_JB_I777-ota-eng.task650.ktoonsez-11.9.2012.zip
(Status 7)
Which i know is a common issue in the FAQ. but the only suggestion is to install some other ROM< which i cannot do b/c i cannot get the phone past boot screen, so i believe i'll be using a guide i found on cnet to go back to stock rom.
pisky1 said:
I've been flashing form this thread for nearly a year as i mentioned so i definitely have the right model, i'm not sure what type of error it was, all i know it it said something like E:/Error cancellation aborted.
Ok in the midst of posting this i finally got into recovery thank you, and i tried reinstalling again. it says "Installing Update...
Symlink: some symlinks failed
E:Error in /emmc/aokp_JB_I777-ota-eng.task650.ktoonsez-11.9.2012.zip
(Status 7)
Which i know is a common issue in the FAQ. but the only suggestion is to install some other ROM< which i cannot do b/c i cannot get the phone past boot screen, so i believe i'll be using a guide i found on cnet to go back to stock rom.
Click to expand...
Click to collapse
Don't use stuff from other sites.
Sent from Team Pirate! Using Tapatalk 2
Nick281051 said:
Don't use stuff from other sites.
Sent from Team Pirate! Using Tapatalk 2
Click to expand...
Click to collapse
I have no problem doing that as long as their some guide on this site to go back to stock rom for me. This guide requires me to go to download mode, which i'm assuming is a different button combination than Recovery?
Id like to know that if thats known.
pisky1 said:
I have no problem doing that as long as their some guide on this site to go back to stock rom for me. This guide requires me to go to download mode, which i'm assuming is a different button combination than Recovery?
Id like to know that if thats known.
Click to expand...
Click to collapse
I'm thinking if i can get into download mode, i can follow the steps that the thread i've been following far give you for status 7 errors, and get my back up and running how it was.
Just need to know how lol.
First thing is IF you need to go back to stock find creepycrawly's return to stock thread. I would HIGHLY SUGGEST TO ONLY USE GUIDES FROM THIS FORUM.
Now onto your issue I personally would get a remove able sdcard, download the aokp zip again and double check the md5. My bet is you just got a bad download. Place the new aokp on the external sdcard, reboot back into recovery and choose to install from sdcard (NOT from internal sdcard since you cannot boot up). Then flash the new aokp.
Another thought is did you make a nandroid backup? You should be able to get into recovery and restore from internal sdcard if you made a nandroid. This will get you back to where you were originally. Then redownload the aokp and check that the md5 matches EXACTLY. Then flash the newer aokp. You are not bricked at this point. Follow up here after you try my suggestions and let us know how it went.
Sent from My SGH-I777 Running Spiderman Themed AOKP or Spiderman Themed CM10
pisky1 said:
I'm thinking if i can get into download mode, i can follow the steps that the thread i've been following far give you for status 7 errors, and get my back up and running how it was.
Just need to know how lol.
Click to expand...
Click to collapse
Covered thousands of times in this forum.
Volume up and down plus power gets to recovery
Volume up and down plus plug in USB gets you to download. These should be the first things anyone knows before Modding their phone.
Sent from my Nexus 7 using Tapatalk 2
Pirateghost said:
Covered thousands of times in this forum.
Volume up and down plus power gets to recovery
Volume up and down plus plug in USB gets you to download. These should be the first things anyone knows before Modding their phone.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I was referred to this thread nearly a year ago by a friend, and i've had no issues so far, so i kind of arrogantly didn't look too far into things like that, which now i'm obviously regretful of. I've gotten into Download mode, am i right in assuming that download mode only accesses stuff on the external SD< b/c i cannot access my internal drive when entering it, which would make my previous theory about being able to follow the standard Status 7 recovery tutorial if i could get into download mode, wrong.
Sadly to respond to the other poster, no again, with the same about not knowing how to get into download mode, i never made a nandroid, mainly because almost everything on my phone is disposable, i don't take pictures really at all, and all my numbers/contacts are synced up to GMAIL, i guess i never thought of a situation arising like this where that didn't matter, i simply wanted to use my phone lol.
Back to a previous comment you said that i now realize i answered too hastily, about if i have the I777, when my phone boots up it says I9100, but what's weird, and i said it before i was referred here by a good friend of mine who knows my phone, and is a much more experienced rooter than i am, so i guess i just took their word for it, and as i said i've flashed ROM's on this phone for nearly a year now, and it's been seamless, not a single problem up until this point, so im wondering if the i777 vs i9100 conflict caused anything.
[EDIT:] Disregard the following comments... I don't believe they will help.
---------------------------------
I've got the answer to all of your questions:
Stickies and Search. READ.
I'm absolutely 100% serious and positively right. Your problems are very well known and thus very well documented.
Try searching in Google:
Status 7 error I777 xda
I777 shows i9100 on boot xda
Any other queries followed by "xda"
Clay
Team Pirate
Sent from my PINK GSwagger2
clay101eve said:
[EDIT:] Disregard the following comments... I don't believe they will help.
---------------------------------
I've got the answer to all of your questions:
Stickies and Search. READ.
I'm absolutely 100% serious and positively right. Your problems are very well known and thus very well documented.
Try searching in Google:
Status 7 error I777 xda
I777 shows i9100 on boot xda
Any other queries followed by "xda"
Team Pirate
Sent from my PINK GSwagger2
Click to expand...
Click to collapse
I want to thank everyone on this thread for their patience, and their answers, i actually used a guide from another site because it had gotten really good feedback, the only problem is it does not have the I777 official firmware, but rather the i9100, for the international version of the phone so my back key does not work, i am currently looking for the correct version, on this thread, and across the internet if anyone can find the official firmware let me know, thanks in advance, and again thanks everyone who answered in the past, your patience and answers were greatly appreciated.
pisky1 said:
I want to thank everyone on this thread for their patience, and their answers, i actually used a guide from another site because it had gotten really good feedback, the only problem is it does not have the I777 official firmware, but rather the i9100, for the international version of the phone so my back key does not work, i am currently looking for the correct version, on this thread, and across the internet if anyone can find the official firmware let me know, thanks in advance, and again thanks everyone who answered in the past, your patience and answers were greatly appreciated.
Click to expand...
Click to collapse
Forums have these things called stickies. Within these stickies are tidbits of information .. typically these tidbits are important enough to warrant the sticky status and as such should be read carefully. All the info you seek is contained within these stickies
Sent from my Nexus 7 using Tapatalk 2
Just get into recovery mode and do the three wipes to fix the bootloop. If it doesn't, DOWNLOAD and FLASH others rom from the original development thread and then install the latest aokp from task to prevent the error status 7. otherwise, please edit the build.prop
Sent from my SGH-I777 using xda premium
pisky1 said:
I want to thank everyone on this thread for their patience, and their answers, i actually used a guide from another site because it had gotten really good feedback, the only problem is it does not have the I777 official firmware, but rather the i9100, for the international version of the phone so my back key does not work, i am currently looking for the correct version, on this thread, and across the internet if anyone can find the official firmware let me know, thanks in advance, and again thanks everyone who answered in the past, your patience and answers were greatly appreciated.
Click to expand...
Click to collapse
For one you could have easily found the sticky threads with the i777 stock firmware. Second now that you flashed a i9100 I HOPE it didn't contain the boot loaders for the i9100. But I guess you will find out at some point I'm sure.
Like I said EVERYTHING you need CAN and ONLY should be found HERE on xda developers. Anything else is a crap shoot. Maybe you will get lucky and maybe not.
now that you flashed the i9100 firmware you will have to actually READ FURTHER than you did before to see HOW to fix your button issue. It can be easy if you know what your doing or can be hard if you don't. Good luck. I'm out...
Sent from my SCH-I800 using xda premium
RockRatt said:
For one you could have easily found the sticky threads with the i777 stock firmware. Second now that you flashed a i9100 I HOPE it didn't contain the boot loaders for the i9100. But I guess you will find out at some point I'm sure.
Like I said EVERYTHING you need CAN and ONLY should be found HERE on xda developers. Anything else is a crap shoot. Maybe you will get lucky and maybe not.
now that you flashed the i9100 firmware you will have to actually READ FURTHER than you did before to see HOW to fix your button issue. It can be easy if you know what your doing or can be hard if you don't. Good luck. I'm out...
Sent from my SCH-I800 using xda premium
Click to expand...
Click to collapse
I simply did a factory reset, then install the i777 stock firmware, and i'm up and running, i'm gonna do this for awhile i intend on getting a new phone in the next couple months, at that point i'll go back to rooting. So nothing to worry about, thanks again for everyone's help.
I was wondering if there has been a way for the Verizon Note 2 users to replace their custom recovery with the Android Stock Recovery to receive OTA's? Similar to this http://www.youtube.com/watch?v=2VVyQRdsnaA
Thanks
andrewjt19 said:
I was wondering if there has been a way for the Verizon Note 2 users to replace their custom recovery with the Android Stock Recovery to receive OTA's? Similar to this http://www.youtube.com/watch?v=2VVyQRdsnaA
Thanks
Click to expand...
Click to collapse
Visit this thread http://forum.xda-developers.com/showthread.php?t=2107738. Under the section boldly labeled Here's the bottom line up-front.....flash the stock pit file and the updated bootloader baseline file. Place the pit file in the PIT section of ODIN and the bootloader baseline file in the PDA section and flash them at the same time. This should restore the stock recovery.
Thanks. I'll give it a shot when I need it again. I ended up just restoring the phone entirely.
Sent from my SCH-I605 using xda app-developers app
andrewjt19 said:
Thanks. I'll give it a shot when I need it again. I ended up just restoring the phone entirely.
Click to expand...
Click to collapse
How did you do the restore? Thanks.
universexda said:
How did you do the restore? Thanks.
Click to expand...
Click to collapse
It's simple. check out the guide by imnuts here
http://rootzwiki.com/index.php?/topic/37372-[ODIN][VRALJB]-Restore-to-Stock
[ODIN][VRALJB] Restore to Stock
Sent from my SCH-I605 using xda app-developers app
universexda said:
How did you do the restore? Thanks.
Click to expand...
Click to collapse
i told you how to do the restore...damn i swear some folks around here are hard headed.
droidstyle said:
i told you how to do the restore...damn i swear some folks around here are hard headed.
Click to expand...
Click to collapse
If you think I'm not going to seek out other people's experience and rely only on your word or your guide as gospel you don't what real computer/phone engineering is about and you don't know me.
Elsewhere I asked you if you have an unlocked bootloader and you flashed the alternate restore file which leaves you bootloader unlocked if running the VRALL4 OTA would successfully relock the bootloader or cause a problem. Would you answer that question, give it your best shot, or simply say you don't know, which are all part of a scientific process.
universexda said:
If you think I'm not going to seek out other people's experience and rely only on your word or your guide as gospel you don't what real computer/phone engineering is about and you don't know me.
Elsewhere I asked you a pertinent question that is not covered in your guide. If you're really about understanding and spreading the knowledge and not simply trying to avoid the question and make people think you know it all, then you'll answer the question, give it the best shot you can, or simply say you don't know, which are all part a scientific process.
Click to expand...
Click to collapse
Let me help you out. You can keep asking and you're going to get the same answer or you're gonna get the wrong answer. His guide is not gospel as you put it, but it is the best, most accurate and easiest guide (that's why the mods decided to stickie it).
Also, I've directed countless people to his guide here and the s3 section to unbrick their phones and guess what it works every time. So you can keep your phone in the state it is and keep flooding the forum with the same question and get the answers I mentioned earlier.
Finally what is part of the scientific process? And what's this question you asked? I just read through your posts and I see questions that were answered in his guide which he then answered again for you. By the way you do realize his work is a guide to help new people with their phone. Not a comprehensive faqs thread.
Sent from my SCH-I605 using Tapatalk 2
kintwofan said:
...
Click to expand...
Click to collapse
I edited my response to him and laid out a detailed question I have based upon reading his guide, and many posts here. It pertains to relocking the bootloader. If you, he or someone else can answer it I'd appreciate it.
universexda said:
I edited my response to him and laid out a detailed question I have based upon reading his guide, and many posts here. It pertains to relocking the bootloader. If you, he or someone else can answer it I'd appreciate it.
Click to expand...
Click to collapse
He answered that for you already, but I'll go into more details. The problem is not OTA with unlocked. It's a custom recovery and OTA. The OTA contains a boot loader theat overwrites your unlocked boot loader without a problem. It does not have a recovery so you keep your custom recovery and get a locked boot loader which equals unauthorized message.
The alternate restore gives you a stock recovery back. The only thing it doesn't restore to stock is the boot loader. So restore+OTA=full locked stock
Sent from my SCH-I605 using Tapatalk 2
kintwofan said:
He answered that for you already, but I'll go into more details. The problem is not OTA with unlocked. It's a custom recovery and OTA. The OTA contains a boot loader theat overwrites your unlocked boot loader without a problem. It does not have a recovery so you keep your custom recovery and get a locked boot loader which equals unauthorized message.
The alternate restore gives you a stock recovery back. The only thing it doesn't restore to stock is the boot loader. So restore+OTA=full locked stock
Click to expand...
Click to collapse
Thanks for the answer.
kintwofan said:
He answered that for you already, but I'll go into more details. The problem is not OTA with unlocked. It's a custom recovery and OTA. The OTA contains a boot loader theat overwrites your unlocked boot loader without a problem. It does not have a recovery so you keep your custom recovery and get a locked boot loader which equals unauthorized message.
The alternate restore gives you a stock recovery back. The only thing it doesn't restore to stock is the boot loader. So restore+OTA=full locked stock
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
THIS!!!!!!!
---------- Post added at 10:07 PM ---------- Previous post was at 10:04 PM ----------
universexda said:
If you think I'm not going to seek out other people's experience and rely only on your word or your guide as gospel you don't what real computer/phone engineering is about and you don't know me.
Elsewhere I asked you if you have an unlocked bootloader and you flashed the alternate restore file which leaves you bootloader unlocked if running the VRALL4 OTA would successfully relock the bootloader or cause a problem. If you're really about understanding and spreading the knowledge and not simply trying to avoid the question and make people think you know it all, then you'll answer the question, give it your best shot, or simply say you don't know, which are all part a scientific process. But avoiding a response and crude blustering are bs.
Click to expand...
Click to collapse
i didnt avoid any question...i answered it plain and simple. yea i dont know anything, boy you got me there lmfao.
on a side note i didnt provide a full detailed explanation because kwintofan and myself have answered that question countless times. a bit of resesrch on your end should of easily answered your question. dont get butt hurt its just the internet
droidstyle said:
THIS!!!!!!!
---------- Post added at 10:07 PM ---------- Previous post was at 10:04 PM ----------
i didnt avoid any question...i answered it plain and simple. yea i dont know anything, boy you got me there lmfao.
on a side note i didnt provide a full detailed explanation because kwintofan and myself have answered that question countless times. a bit of resesrch on your end should of easily answered your question. dont get butt hurt its just the internet
Click to expand...
Click to collapse
It's silly to get wound up because people don't just accept your guide and advice right off the bat. If you were really about knowledge and not your ego you wouldn't have a problem with people attempting to verify what you have to say.
Notably, your response to me in your guide thread that "no people had problems with ota when using a custom recovery" conflicts with kintwofan's response that "The problem is not OTA with unlocked. It's a custom recovery and OTA." But above you just endorsed what kintwofan had to say. So despite your vein popping crudeness my question remains unresolved between what the 2 of you say.
universexda said:
Don't get your panties in a bunch because people don't accept your guide and advice at face value. If you were really about knowledge and not your ego you wouldn't have a problem with people attempting to verify what you have to say.
Notably, your response to me in your guide thread that "no people had problems with ota when using a custom recovery" conflicts with kintwofan's response that "The problem is not OTA with unlocked. It's a custom recovery and OTA." But above you just endorsed what kintwofan had to say. So despite your vein popping crudeness my question remains unresolved between what the 2 of you say.
Click to expand...
Click to collapse
Our answers are the same. He said no to having a problem taking the ota and being unlocked then continued to say the problem was a custom recovery. I guess he just forgot the period in there.
And this is getting old. If you were really all about knowledge you would take his answer and research why instead of wanting to be soon fed the information. You would have also just searched for the multiple people that have went to his guides and fixed their phone to verify if they were legit.
Sent from my SCH-I605 using Tapatalk 2
kintwofan said:
Our answers are the same. He said no to having a problem taking the ota and being unlocked then continued to say the problem was a custom recovery. I guess he just forgot the period in there.
And this is getting old. If you were really all about knowledge you would take his answer and research why instead of wanting to be soon fed the information. You would have also just searched for the multiple people that have went to his guides and fixed their phone to verify if they were legit.
Click to expand...
Click to collapse
I don't see where droidstyle says it's recovery that would cause a problem with the OTA and not the bootloader.
Verifying with others is precisely what I've been doing. The thing is that droidstyle has jumped in peevishly to assert that I should just accept what his guide says and not ask anyone else about it at all. Problem is that his guide doesn't explicitly address my question. And secondly it makes sense to verify procedures with others before relying on what could be a hundreds of dollars mistake.
Appreciate both you and him when you address the issue. It's not old to me when there are discrepancies in what's being said. I've researched the issue by reading all relevant threads here since the vrall4 jailbreak and still my question has not been consistently answered. I advise you both to ignore my questions/research on this matter in the future as it appears you've already contributed what you can.
no. People had problems with ota when using a custom recovery.
There I'll add the punctuation from his quote now you can see that we agree. My point was not to keep asking, but to actually research. You know look at what's in the ota and what causes the unauthorized message. Then take that info and formulate a hypothesis and test it. You know the scientific method you like.
Also don't worry I won't answer you're further questions.
Sent from my SCH-I605 using Tapatalk 2
universexda said:
I don't see where droidstyle says it's recovery that would cause a problem with the OTA and not the bootloader.
Verifying with others is precisely what I've been doing. The thing is that droidstyle has jumped in peevishly to assert that I should just accept what his guide says and not ask anyone else about it at all. Problem is that his guide doesn't explicitly address my question. And secondly it makes sense to verify procedures with others before relying on what could be a hundreds of dollars mistake.
Appreciate both you and him when you address the issue. It's not old to me when there are discrepancies in what's being said. I've researched the issue by reading all relevant threads here since the vrall4 jailbreak and still my question has not been consistently answered. I advise you both to ignore my questions/research on this matter in the future as it appears you've already contributed what you can.
Click to expand...
Click to collapse
i did say it was a recovery issue in my thread wher u initially asked...go back and read. then u might want to go back and read thru the guide again and you will see where i answered that question more than once. my guide is stickied for a reason...if you want other opinions thats fine, i could care less. i provided you with all the info necessary, your not going to get some magical answer....ill say it again.
odin stock vraljb(no bootloader version / alternate restore method). this will give you stock recovery back which will allow you to take the L4 OTA. then you will be on stock, locked, and bloated L4.... the bootlader being locked or unlocked will not effect anything OTA related. Having a custom recovery will cause the OTA to fail.
---------- Post added at 11:07 PM ---------- Previous post was at 10:57 PM ----------
universexda said:
It's silly to get wound up because people don't just accept your guide and advice right off the bat. If you were really about knowledge and not your ego you wouldn't have a problem with people attempting to verify what you have to say.
Notably, your response to me in your guide thread that "no people had problems with ota when using a custom recovery" conflicts with kintwofan's response that "The problem is not OTA with unlocked. It's a custom recovery and OTA." But above you just endorsed what kintwofan had to say. So despite your vein popping crudeness my question remains unresolved between what the 2 of you say.
Click to expand...
Click to collapse
you obviously have a problem with comprehension...my panties are not in a bunch or wound up. i could give 2 ****s REALLY! you came into my thread asking my advice, then ignored me. then you proceed to take advice from new users that were not sure themselves. wow your scientific method is really panning out now.
note 2 bootloop
Ok next...i bought a note 2 verizon off someone and i know it was on 4.3.1 nd7 thats all i can remember i rooted kingroot then supersu me ok everything fine until i downloaded twrp app from playstore flashed twrp and what ever i did i went to boot into recovery thats it done deal no stock recovery only have download mode.Keeps saying firmare disrupted and verizon firmware wrong go to store and fix. Ive flashed some stock roms and tried flashing twrp through odin..whenever i do it does pass the flash and reboots right back to original stuck screen its says note 2 real fast then pops up to the bootloop screen any advice would be appretiated..lets help another android user out i need my phone back
ricosf415 said:
Ok next...i bought a note 2 verizon off someone and i know it was on 4.3.1 nd7 thats all i can remember i rooted kingroot then supersu me ok everything fine until i downloaded twrp app from playstore flashed twrp and what ever i did i went to boot into recovery thats it done deal no stock recovery only have download mode.Keeps saying firmare disrupted and verizon firmware wrong go to store and fix. Ive flashed some stock roms and tried flashing twrp through odin..whenever i do it does pass the flash and reboots right back to original stuck screen its says note 2 real fast then pops up to the bootloop screen any advice would be appretiated..lets help another android user out i need my phone back
Click to expand...
Click to collapse
I did the same thing on my Note 2. I currently use the Note 4, but wanted to do some updates to my Note 2 and give it to my son. I just forgot about the locked bootloader, and I downloaded the TWRP app from the Play Store and flashed the 3.0 TWRP. Next boot gave me the "Unauthorized software" message. I've tried flashing stock firmware, and it succeeds, but since the bootloader is locked, I still get the "Unauthorized" message. I would also appreciate any help that can be offered to get the bootloader back to stock. I knew better, it had been a couple years since I messed with my Note 2. Thanks for any help.
Did you all try flashing the 4.4 stock firmware? Should work if you can find the file. I just can't seem to find it
Sent from my SM-N915V using Tapatalk
So my friend decided to try to update my tablet and i was on Hariybean 2.31 and he installed twrp that wasn't compatible and now i cannot mount anything in the recovery and it only boots to the recovery i can still get adb from the remove menu and i can adb restart bootloader and access fast boot but every time i try to flsh anything it locks up fastboot says that i am on 10.6.1.27. anyone with any knoloege please help.
Edit:
Follow Flumpsters method below ...
the isc or the jelly bean on also i have gotten the hairbeany recover back on but i dont have permission to do anything. keeps asking for password.?
SAJdroid said:
Goto twrp download 2.5.0.0 version n flash from fast boot. Install hairy bean again by following the instructions.
Once u are able to successfully load the rom. Goto recovery n flash the downgrade bootloader which can be found at the bottom of hairy bean thread. Now you can flash any rom compatible on 4.1 bootloader.
Click to expand...
Click to collapse
Mate you have to stop telling people this. This is the second thread I have seen you say it In. Hairy bean uses the 4.2 bootloader, flashing 2.5 twrp from their site for the prime is just asking to hard brick the device.
Official twrp will not work on a 4.2 bootloader, he would not be able to do anything in it. It would have all partitions locked and he would be completely stuck and it would ask for a password.
http://forum.xda-developers.com/showpost.php?p=40149294&postcount=8
http://forum.xda-developers.com/showthread.php?t=2409602
edit.. Just in case that sounded a bit harsh it wasn't meant to. I am just trying to stop people getting in worse situations.
flumpster said:
Mate you have to stop telling people this. This is the second thread I have seen you say it In. Hairy bean uses the 4.2 bootloader, flashing 2.5 twrp from their site for the prime is just asking to hard brick the device.
Official twrp will not work on a 4.2 bootloader, he would not be able to do anything in it. It would have all partitions locked and he would be completely stuck and it would ask for a password.
http://forum.xda-developers.com/showpost.php?p=40149294&postcount=8
http://forum.xda-developers.com/showthread.php?t=2409602
edit.. Just in case that sounded a bit harsh it wasn't meant to. I am just trying to stop people getting in worse situations.
Click to expand...
Click to collapse
Flumpster you are correct mate .. sorry for the confusion .. I am editing the previous threads ...
SAJdroid said:
Flumpster you are correct mate .. sorry for the confusion .. I am editing the previous threads ...
Click to expand...
Click to collapse
Cheers. Don't stop helping over this, They need all the people they can over here helping out. Just make sure you know you are 100 percent before giving advise, I always used to test it myself first as wrong information is far worse than no information.
Keep up the good work mate. :good:
I rooted my Verizon GS4 using the saferoot method and was successful. When I tried to install TWRP Recovery using GooManager, it rebooted to a screen with the Android logo that said it could not reboot normally. Is there any way to fix this?
quinpin said:
I rooted my Verizon GS4 using the saferoot method and was successful. When I tried to install TWRP Recovery using GooManager, it rebooted to a screen with the Android logo that said it could not reboot normally. Is there any way to fix this?
Click to expand...
Click to collapse
Every day someone creates a thread like this.
Use Odin to restore to whatever stock build you were on, then start your research by reading this thread.http://forum.xda-developers.com/showthread.php?t=2606501
Search the forums. All of the questions you're going to ask have already been answered.
Yes it's fixable. First you must read every stickied thread possible, then find where the search button is. This is posted almost daily so it's out there. You can't flash a custom recovery on me7 or higher,safestrap is the only option. To get back your stock recovery you'll have to flash one of the stock images via Odin . until your recovery is back You can power your phone off in the meantime use the buttons to boot into download mode, cancel it and your phone will boot normally.
READ AND SEARCH BEFORE YOU DESTROY A 600$ device. Not trying to be rude but 5 mins of reading would of saved you a couple hours of troubleshooting/fixing.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Thank you! This isn't my first time rooting my Droid but it is the first time I've encountered a problem, so I'm glad I'll be able to get some help with it.
So none of the things at GalaxyS4Root would have worked? (I'd post the link but the forums won't let me)
quinpin said:
Thank you! This isn't my first time rooting my Droid but it is the first time I've encountered a problem, so I'm glad I'll be able to get some help with it.
So none of the things at GalaxyS4Root would have worked? (I'd post the link but the forums won't let me)
Click to expand...
Click to collapse
You need to find what build you're on and then find out what will or won't work.
Sent from my NCC-1701 using Tapatalk 4