Hi,
I have galaxy nexus yakju it was running android 4.1.1. Then i rooted the phone. After the 4.2 update got release to get early update i flashed takju4.1.2 ROM and updated it to 4.2 using the ADB Update option in recovery.
then i rooted the device it was working fine, to test some other ROMs i installed TWRP recovery for 4.2. Before installing ROMS i took the backup. Im not satisfied with ROM so i restored Backup.
Currently im running rooted android 4.2 with TWRP recovery. Everything is fine but suddenly today i got OTA update to 4.2.1.(i dont think i should get OTA updates since i dont have stock recovery and i rooted). Since im very curious person i installed the update.
it installed the update successfully , now im running 4.2.1. But unfortunately it Unrooted my device and replaced my recovery with stock.
When i enter into recovery by pressing volume Down+power button , when the device is showing lying android symbol, it says 'updating' msg and there are no options other than start which will eventually start the normal boot process.
Now how can i flash stock 4.2 ROM and stock recovery?
that sleeping android is the stock recovery.. press volume up + power to boot into it
First of all, why would you not just keep 4.2.1 and root that?
Also everything that has happened is perfectly normal, and you should indeed get OTA's if you only rooted it, and if your recovery supports it, you can install them as well.
If you really do want to get back to 4.2, just flash the stock image from google and root it from there by flashing a recovery from fastboot and then using that recovery to flash superuser and su binary, but you might as well stay in 4.2.1 and just do the latter.
and yes that sleeping android is the stock recovery.
mortenmhp said:
First of all, why would you not just keep 4.2.1 and root that?
Also everything that has happened is perfectly normal, and you should indeed get OTA's if you only rooted it, and if your recovery supports it, you can install them as well.
If you really do want to get back to 4.2, just flash the stock image from google and root it from there by flashing a recovery from fastboot and then using that recovery to flash superuser and su binary, but you might as well stay in 4.2.1 and just do the latter.
and yes that sleeping android is the stock recovery.
Click to expand...
Click to collapse
i think he was tense cuz he thought his recovery is gone thats why he wanted to go back.. but OP if you wanna stay on 4.2.1 and root it, just flash twrp adn flash the supersu zip in it to root your gnex
Tha for the reply
k786 said:
that sleeping android is the stock recovery.. press volume up + power to boot into it
Click to expand...
Click to collapse
I did tried volume down_ power button. But the recovery menu is something different than its used to be. It has 'start' button as it is in fast boot, and big title in middle saying 'Updating', other than that there are no options.
i think i should flash 4.2 stock rom from google using toolkit, which will over rite my current recovery, if there is a problem with recovery it will solve it.
Let me know if im doing it wrong.
Thanks
Issue fixed
Flashed stock 4.2 image using toolkit, now recovery is working fyn when i press volume down + power button.And updated to 4.1.2 also.
But i got rpc:S-5:AEC-0 error while trying to download apps from market. im still searching for solution. gonna post it here if i cant find it anywhere.
Thanks everyone.
Related
So i recently unlocked and rooted my GNex (LTE version) and upgraded to 4.0.4... It worked fine until sometime later apps that required root access couldnt acquire it. I couldn't flash cwm in rom manager and i couldn't boot into cwm. When I powered the device on and went into recovery manually (volume buttons and power button) it just went to the stock recovery/bootloader.
I think i need to reroot my device again? I'm not sure. Any help would be appreciated!
Sounds like you just need to reflash CWM. I'm not sure what version you were on before, if it was touch based or not. But either reflash CWM file you did before, or if you use ROM Manager just flash CWM at the top option in the app and reboot into recovery. Hopefully that will work for you.
You probably lost root when you applied the 4.0.4 update. You need to install a custom recovery via fastboot and install the new superuser. Some su.zip's do not work, so you need to find a newer one. adrynalyne posted a working one. I'm sure you can find it by searching his user name and looking at the results as posts.
A 'rootkit' may also work for you. It does the same thing, just makes it so users don't really know what's happening .
Hi guys, blackberry convert here.
So I just bought a "docomo" carrier nexus and it's been working good so far.
It's running 4.01 and recently got an update notification but when i tried to update it rebooted to a green android with its chest opened up and a red exclamation mark. I did some searching and noticed that happens when you try to OTA upgrade a rooted phone am I correct?
So my question is what are my options? Can I flash 4.04 ? Do i need to lock my bootloader and wipe back to stock? If I do.. Will i get the unpleasant surprise of everything being in japanese?
What about flashing a custom rom such as aokp? Will that upgrade me to 4.04 or not?
TIA
KrizTM said:
Hi guys, blackberry convert here.
So I just bought a "docomo" carrier nexus and it's been working good so far.
It's running 4.01 and recently got an update notification but when i tried to update it rebooted to a green android with its chest opened up and a red exclamation mark. I did some searching and noticed that happens when you try to OTA upgrade a rooted phone am I correct?
So my question is what are my options? Can I flash 4.04 ? Do i need to lock my bootloader and wipe back to stock? If I do.. Will i get the unpleasant surprise of everything being in japanese?
What about flashing a custom rom such as aokp? Will that upgrade me to 4.04 or not?
TIA
Click to expand...
Click to collapse
Yes that means its rooted, you should have a custom Recovery. If you power off and hold the volume keys and the power button then a green android will pop up use the volume keys and hit up twice to the "recovery mode" then hit the power button... then if you could tell me what you see? At the bottom it should say Clockworkmod 5.x.x.x or it will have TWRP which it will show TeamWin at first and a curtain will pull up. If you do have custom recovery you could just simply flash a custom ROM like AOKP for you device .
KrizTM said:
Hi guys, blackberry convert here.
So I just bought a "docomo" carrier nexus and it's been working good so far.
It's running 4.01 and recently got an update notification but when i tried to update it rebooted to a green android with its chest opened up and a red exclamation mark. I did some searching and noticed that happens when you try to OTA upgrade a rooted phone am I correct?
So my question is what are my options? Can I flash 4.04 ? Do i need to lock my bootloader and wipe back to stock? If I do.. Will i get the unpleasant surprise of everything being in japanese?
What about flashing a custom rom such as aokp? Will that upgrade me to 4.04 or not?
TIA
Click to expand...
Click to collapse
No, that doesn't happen because of root. Root has NO IMPACT WHATSOEVER on your ability to install updates OTA. It will happen if your recovery does not match your ROM.
You have a few options:
1) you can go to the "update" link in my signature, find the update for your build, and install it manually as per the instructions in that thread.
2) you can go to the "flash" link in my signature and flash stock (yakju) 4.0.4 as per the instructions.
3) you can flash a 4.0.4-based custom ROM.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
No, that doesn't happen because of root. Root has NO IMPACT WHATSOEVER or your ability to install updates OTA.
Click to expand...
Click to collapse
UH YES it does... why do you think we get so many "broken android red exclamation mark!" threads started... because people who root tried to accept the OTA. OTA's require the stock Recovery to install... when it sees that thats been changed or something has been modified.. then it errors. Get it straight.
ÜBER™ said:
UH YES it does... why do you think we get so many "broken android red exclamation mark!" threads started... because people who root tried to accept the OTA. OTA's require the stock Recovery to install... when it sees that thats been changed or something has been modified.. then it errors. Get it straight.
Click to expand...
Click to collapse
Uh, excuse me... having root makes no difference. You get it straight. But you are right, having the wrong recovery (custom recovery or incorrect stock version) will give you that screen.
I've applied every single update on a rooted phone. Details in the update link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
Uh, excuse me... having root makes no difference. You get it straight. But you are right, having the wrong recovery (custom recovery or incorrect stock version) will give you that screen.
I've applied every single update on a rooted phone. Details in the update link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Heh... i dont see people with just superuser and no custom recovery the two go hand in hand... which is why i say Root does to play a part. At least on certain devices.
ÜBER™ said:
Heh... i dont see people with just superuser and no custom recovery the two go hand in hand... which is why i say Root does to play a part. At least on certain devices.
Click to expand...
Click to collapse
Well, lots of users in the forums root and keep the stock recovery, but yeah, not as many as those who use a custom recovery along with root. That is why I make the distinction. Adding files to /system (which is what rooting does ) doesn't affect anything. Deleting or replacing system files does however.
Additionally, you can still update even with a custom recovery. Just put the update file in /sdcard, reboot into recovery and flash it. No difference than having it flashed by a stock recovery.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
Well, lots of users in the forums root and keep the stock recovery, but yeah, not as many as those who use a custom recovery along with root. That is why I make the distinction. Adding files to /system (which is what rooting does ) doesn't affect anything. Deleting or replacing system files does however.
Additionally, you can still update even with a custom recovery. Just put the update file in /sdcard, reboot into recovery and flash it. No difference than having it flashed by a stock recovery.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Gotcha now that we are done bickering.. i hope the OP can find his way.
ycholish siempre
3) you can flash a 4.0.4-based custom ROM.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Is aokp a 4.04 based ROM? I keep refering to aokp because from what ive read its the best rom out there.
then if you could tell me what you see?
Click to expand...
Click to collapse
Well it tells me im on prime and that my lock mode is : unlocked. So i suppose i'm rooted.
So if i flash a custom 4.04 rom i'm all set for future upgrades? Or should I flash androids stock 4.04 and then flash a custom rom?
Thanks for the help guys .
KrizTM said:
Is aokp a 4.04 based ROM? I keep refering to aokp because from what ive read its the best rom out there.
Well it tells me im on prime and that my lock mode is : unlocked. So i suppose i'm rooted.
So if i flash a custom 4.04 rom i'm all set for future upgrades? Or should I flash androids stock 4.04 and then flash a custom rom?
Thanks for the help guys .
Click to expand...
Click to collapse
Aokp just has a bunch more options which is quite overwhelming especially for a new user such as yourself. I would suggest using CM9 first. Okay that means your boot loader is unlocked... I said you have to go into recovery mode... which when at the boot loader screen you use the volume keys and hit up twice it change from start to recovery mode in red. Press the power button and tell me if you see a cyan blue recovery or team win on a blue curtain that pulls up.
Sent from my Galaxy Nexus using xda premium
ÜBER™ said:
Aokp just has a bunch more options which is quite overwhelming especially for a new user such as yourself. I would suggest using CM9 first. Okay that means your boot loader is unlocked... I said you have to go into recovery mode... which when at the boot loader screen you use the volume keys and hit up twice it change from start to recovery mode in red. Press the power button and tell me if you see a cyan blue recovery or team win on a blue curtain that pulls up.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Ok. i did the recovery mode thing and it gave me the android with its chest open and a red exclamation mark thing again
What's going on?
Check my sig to get yourself on AOKP.
KrizTM said:
[snip]
Well it tells me im on prime and that my lock mode is : unlocked. So i suppose i'm rooted.
Click to expand...
Click to collapse
Ok, I think you are confusing things here:
(1) An unlocked bootloader
(2) Root
(3) A custom recovery
The three items above are completely separate. Having one does not mean the others, nor does one require any of the others. Just because your bootloader is unlocked does not mean your OS is rooted, nor does it mean you have a custom recovery.
KrizTM said:
So if i flash a custom 4.04 rom i'm all set for future upgrades? Or should I flash androids stock 4.04 and then flash a custom rom?
Click to expand...
Click to collapse
ONLY stock ROMs can receive OTA updates. If you want updates, you need to be running a stock ROM. Period.
If you want to run a custom ROM, you will either get updates from the developer, or you will need to flash an updated version of that custom ROM.
Again, don't confuse flashing an updated version of ROM (i.e., a complete ROM), vs updating a ROM (i.e., an incremental update).
KrizTM said:
Ok. i did the recovery mode thing and it gave me the android with its chest open and a red exclamation mark thing again
What's going on?
Click to expand...
Click to collapse
That screen IS the stock recovery. (FYI, to access the menu, you need to press vol up and power simultaneously and repeatedly).
I would suggest you follow the instructions here to flash the yakju 4.0.4 build (do all the optional steps in part D) and then you will be set for all future OTA updates. (And besides, it is always wiser to run stock for a while, so that when you switch to a custom ROM, you have a basis for comparison.)
If you want to run a custom ROM, download whichever ROM it is to your /sdcard.
No you must first flash a custom recovery. Do this:
Assuming you already have the drivers set up and you have fastboot.exe on you computer (instructions found in the link above), do the following:
1) Download CWM from here;
2) Rename the file to cwm.img, and make sure it is in the same directory as your fastboot.exe file;
4) Restart your device in fastboot mode and plug into computer;
5) Open a command prompt in the directory mentioned above and type: fastboot flash recovery cwm.img
6) Now you have a custom recovery. Use the volume buttons on your device to navigate to "recovery", and use the power button to select;
7) Wipe your device using the CWM menus;
8) Flash the ROM by using the CWM menus (something like flash zip or something).
efrant said:
Ok, I think you are confusing things here:
(1) An unlocked bootloader
(2) Root
(3) A custom recovery
The three items above are completely separate. Having one does not mean the others, nor does one require any of the others. Just because your bootloader is unlocked does not mean your OS is rooted, nor does it mean you have a custom recovery.
ONLY stock ROMs can receive OTA updates. If you want updates, you need to be running a stock ROM. Period.
If you want to run a custom ROM, you will either get updates from the developer, or you will need to flash an updated version of that custom ROM.
Again, don't confuse flashing an updated version of ROM (i.e., a complete ROM), vs updating a ROM (i.e., an incremental update).
That screen IS the stock recovery. (FYI, to access the menu, you need to press vol up and power simultaneously and repeatedly).
I would suggest you follow the instructions here to flash the yakju 4.0.4 build (do all the optional steps in part D) and then you will be set for all future OTA updates. (And besides, it is always wiser to run stock for a while, so that when you switch to a custom ROM, you have a basis for comparison.)
If you want to run a custom ROM, download whichever ROM it is to your /sdcard.
No you must first flash a custom recovery. Do this:
Assuming you already have the drivers set up and you have fastboot.exe on you computer (instructions found in the link above), do the following:
1) Download CWM from here;
2) Rename the file to cwm.img, and make sure it is in the same directory as your fastboot.exe file;
4) Restart your device in fastboot mode and plug into computer;
5) Open a command prompt in the directory mentioned above and type: fastboot flash recovery cwm.img
6) Now you have a custom recovery. Use the volume buttons on your device to navigate to "recovery", and use the power button to select;
7) Wipe your device using the CWM menus;
8) Flash the ROM by using the CWM menus (something like flash zip or something).
Click to expand...
Click to collapse
Awesome. That clears up a lot of things. Thanks a lot You're right. Gonna stick to stock 4.04 till I get better at this hehe.
Thanks
Hi My Galaxy Nexus seems to be Bricked.(PHONE NOT BOOTING)
Problem:
1. Power button doesn't work- Phone not booting
2. I connected through a USB cable then phone started charging, Then i tried to boot which didn't work
2.1 Then i tried to go into Recovery (TWRP) which somehow worked for a while and then rebooted.
2.2 After trying more i finally managed to get TWRP working and i re-flashed the same version of Paranoid Android(@BigBrother) 4.3 Beta 2 that was installed - DIDN'T WORK
3. Then i trying to take the backup and succeeded using ADB from TWRP.
3.1 Then i flashed an old version of PA - didn't work
3.2 Then i tried installing the Stock ROM (4.3) - Installed successfully- But didn't work on restart. After Restarting the Google screen came up and then the Battery Charging indicator started flashing. The phone didn't boot up.
Initially i used Trickster MOD to overclock the phone to 1.5 Ghz, but I did it in Morning and the phone was fine till night So i am still not sure of the reason.
Anyone Please Help :'(
can you get into download mode?
if yes then reflash the stock google image using terminal and not toolkit.
if you successfully flashed 4.3, then go to recovery mode and wipe data/cache. it should boot up correctly.
run stock firmware for a week and see if the phone is stable.
hp13 said:
can you get into download mode?
if yes then reflash the stock google image using terminal and not toolkit.
if you successfully flashed 4.3, then go to recovery mode and wipe data/cache. it should boot up correctly.
run stock firmware for a week and see if the phone is stable.
Click to expand...
Click to collapse
Yes i Did get into Download Mode, and i Had successfully flashed stock 4.3 using terminal. I never used toolkit.
Didn't Boot yet
NOT BOOTING AT ALL
dk_india_world said:
Yes i Did get into Download Mode, and i Had successfully flashed stock 4.3 using terminal. I never used toolkit.
Didn't Boot yet
NOT BOOTING AT ALL
Click to expand...
Click to collapse
remove battery and put it back.
go into stock recovery and reset data
hp13 said:
remove battery and put it back.
go into stock recovery and reset data
Click to expand...
Click to collapse
Removed battery for half an hour.
Data already gone due to stock installation.
Power button not working at all.
Still needs to power up using a charger and then at least i could see the google logo
Guys Any Help.. :|
So I rooted my sgh-m919 (m919uvuemk2) running android 4.3. Root went fine, but I couldn't get TWRP (2.8.7.0) installed. Anytime I tried to boot into it, it would just boot normally. Thinking it was knox messing with the firmware boot, I uninstalled it. It seemed to uninstall fine but when I tried to get into recovery/download mode while holding the buttons it flashed the android screen then rebooted normally.
Then I installed andromizer and was finally able to get to TWRP. So I installed cyanogenmod 12.1 fine, but gapps failed (error code 70). So i've lost root. And my phone still can't get into download mode. Flashes and boots normally. Doesn't seem like a hard or soft brick situation, but I don't really know. I wasn't able to find any forums that fit this description.
Any ideas or recommendations on what I should do?
Any help greatly appreciated... thank you!
slungshot said:
So I rooted my sgh-m919 (m919uvuemk2) running android 4.3. Root went fine, but I couldn't get TWRP (2.8.7.0) installed. Anytime I tried to boot into it, it would just boot normally. Thinking it was knox messing with the firmware boot, I uninstalled it. It seemed to uninstall fine but when I tried to get into recovery/download mode while holding the buttons it flashed the android screen then rebooted normally.
Then I installed andromizer and was finally able to get to TWRP. So I installed cyanogenmod 12.1 fine, but gapps failed (error code 70). So i've lost root. And my phone still can't get into download mode. Flashes and boots normally. Doesn't seem like a hard or soft brick situation, but I don't really know. I wasn't able to find any forums that fit this description.
Any ideas or recommendations on what I should do?
Any help greatly appreciated... thank you!
Click to expand...
Click to collapse
I think you may have some terms confused.
To get into Download Mode: Turn off your phone, then turn it on and hold down the Volume Down button. You will get a screen that starts with "Warning!!", and where you can press Volume Up to Continue, or Volume Down to Cance.
To get into Recovery Mode: Turn off your phone, then turn it on and hold down the Volume Up button. You will get some small text at the top left of the screen, and then whichever Recovery you have installed in the Recovery partition will run.
You use Download mode to flash using ODIN.
To get something into the Recovery partition, you can flash using ODIN, or if you are rooted, you can use an app like the TWRP Manager app, and some others.
Also, there isn't an official 2.8.7.0 TWRP. The latest is 2.8.4.0 which may be most/part of your issue.
Getting root is very easy on the SGH-M919, just use the CF-AutoRoot app. But, you don't need root to flash TWRP with ODIN. Also, almost every non-stock ROM will come pre-rooted. So, if you have flashed a CM rom, you are rooted. But, you may need to download SuperSU from the app store.
Rob
Hi Rob, Thanks for the reply. My problem is I hold down the buttons but they no longer boot me into recovery, the android recovery screen flashes for a sec, then boots normally.
I may have found a workaround though, it seems I can now do a recovery option from the power down menu, and that boots me into TWRP. Not sure why the buttons no longer get me into the recovery console, but this may work.
Funny thing is I lost root after installing cm 12.1 while rooted. I think I may downgrade to kit kat because it seems like lollipop drains the battery much faster.
rlichtefeld said:
I think you may have some terms confused.
To get into Download Mode: Turn off your phone, then turn it on and hold down the Volume Down button. You will get a screen that starts with "Warning!!", and where you can press Volume Up to Continue, or Volume Down to Cance.
To get into Recovery Mode: Turn off your phone, then turn it on and hold down the Volume Up button. You will get some small text at the top left of the screen, and then whichever Recovery you have installed in the Recovery partition will run.
You use Download mode to flash using ODIN.
To get something into the Recovery partition, you can flash using ODIN, or if you are rooted, you can use an app like the TWRP Manager app, and some others.
Also, there isn't an official 2.8.7.0 TWRP. The latest is 2.8.4.0 which may be most/part of your issue.
Getting root is very easy on the SGH-M919, just use the CF-AutoRoot app. But, you don't need root to flash TWRP with ODIN. Also, almost every non-stock ROM will come pre-rooted. So, if you have flashed a CM rom, you are rooted. But, you may need to download SuperSU from the app store.
Rob
Click to expand...
Click to collapse
slungshot said:
Hi Rob, Thanks for the reply. My problem is I hold down the buttons but they no longer boot me into recovery, the android recovery screen flashes for a sec, then boots normally.
I may have found a workaround though, it seems I can now do a recovery option from the power down menu, and that boots me into TWRP. Not sure why the buttons no longer get me into the recovery console, but this may work.
Funny thing is I lost root after installing cm 12.1 while rooted. I think I may downgrade to kit kat because it seems like lollipop drains the battery much faster.
Click to expand...
Click to collapse
If TWRP 2.8.70 is not functioning correctly, then please try the last stable version: 2.8.4.0.
See the thread here: http://forum.xda-developers.com/showthread.php?t=2263001&page=61
I run 2.8.4.0, and the buttons work and TWRP Manager works, etc.
CM12 comes pre-rooted - all non-stock ROMs do. You may have lost the SuperSU app when you flashed, but that can be downloaded from the app store.
Rob
Thanks Rob. I figured out that I was still able to reboot into recovery without buttons so I just went that route. Where did you get the 4.4.4 rom? I can't find anything on the cyanogen site other than snapshot 4.4.2, which I installed last night trying to solve my problem of when someone calls they hear a wicked echo.
rlichtefeld said:
If TWRP 2.8.70 is not functioning correctly, then please try the last stable version: 2.8.4.0.
See the thread here: http://forum.xda-developers.com/showthread.php?t=2263001&page=61
I run 2.8.4.0, and the buttons work and TWRP Manager works, etc.
CM12 comes pre-rooted - all non-stock ROMs do. You may have lost the SuperSU app when you flashed, but that can be downloaded from the app store.
Rob
Click to expand...
Click to collapse
slungshot said:
Thanks Rob. I figured out that I was still able to reboot into recovery without buttons so I just went that route. Where did you get the 4.4.4 rom? I can't find anything on the cyanogen site other than snapshot 4.4.2, which I installed last night trying to solve my problem of when someone calls they hear a wicked echo.
Click to expand...
Click to collapse
SamMobile has all the Stock firmwares for all the Samsung phones. However, their downloads can be a little slow.
Luckily, ShinySide on this forum in the General Section has this thread with fast downloads:
http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508
Flashing 4.4.4 will get you the most recent firmware - boot, recovery, modem and ROM. So, you'll need to flash a recovery and CM Rom after that if you want to go back to CM. However, with CM you lose WiFi Calling. You could root the Stock and remove any apps you don't want, or freeze them with TitaniumBackup. That way you get the best of both worlds - stock, but only running the apps you want.
YMMV.
Rob
Is the OH1 bootloader compatible with custom roms that require nd8?
I want to put Wicked S5 Xperience on my SIII but it says must have nd8 bootloader and I did the ota to OH1 and rerooted w/ twrp and supersu.
OH1 compatible with custom roms
aschubart said:
Is the OH1 bootloader compatible with custom roms that require nd8?
I want to put Wicked S5 Xperience on my SIII but it says must have nd8 bootloader and I did the ota to OH1 and rerooted w/ twrp and supersu.
Click to expand...
Click to collapse
Hey all,
Answered my own question. Successfully installed wicked s5 xperience 2.2 (wih requires nd8) without a hitch. basically I followed the step by step with exception to. I used twrp... wich they dont support. I did a dirty flash... worked fine but all my old settings were still there, So I did a Proper clean flash and all is good. Way better modem.... than OH1. I have signal and data in places I used to not get.
Hope this helps anyone else.
I have a question, how did you go about installing a custom ROM with OH1.
I can't seem to use Odin to install TWRP. It says success but when I try to 'adb reboot recovery', it just goes to the stock recovery. Any idea on how to install a custom recovery?
TheFatDemon said:
I have a question, how did you go about installing a custom ROM with OH1.
I can't seem to use Odin to install TWRP. It says success but when I try to 'adb reboot recovery', it just goes to the stock recovery. Any idea on how to install a custom recovery?
Click to expand...
Click to collapse
Did you
Hold power button to turn off your S3, after it turns off about 10 seconds later it will turn back on to the battery charging screen so before that quickly hold Volume+ and Home, to boot into recovery.
I got from http://forum.xda-developers.com/showthread.php?t=2787771
If odin says success it should boot to twrp.
Once I was in twrp I just installed my downloaded ROM. You probably will want to do a wipe first to have a clean flash.
aschubart said:
Did you
Hold power button to turn off your S3, after it turns off about 10 seconds later it will turn back on to the battery charging screen so before that quickly hold Volume+ and Home, to boot into recovery.
I got from http://forum.xda-developers.com/showthread.php?t=2787771
If odin says success it should boot to twrp.
Once I was in twrp I just installed my downloaded ROM. You probably will want to do a wipe first to have a clean flash.
Click to expand...
Click to collapse
I ended up having to do that. For some reason Odin wasn't kicking me into recovery so I had to boot into recovery myself. Another issue that I noticed was that TWRP couldn't root stock firmware. It would install SuperSU but wouldn't install the su binary. I ended up just installing AICP.
Thanks for the help.
TheFatDemon said:
I ended up having to do that. For some reason Odin wasn't kicking me into recovery so I had to boot into recovery myself. Another issue that I noticed was that TWRP couldn't root stock firmware. It would install SuperSU but wouldn't install the su binary. I ended up just installing AICP.
Thanks for the help.
Click to expand...
Click to collapse
Glad you got it going.. I haven't tried Ice Cold looks like a solid ROM though.
Roms
Is there any rom for the l710vpudoh1?
Hi...Please can you get an OH1 modem for me? My phone has no service and im running android 6.0.1