Develop Bugs

Yakjuxe to Yakju

Hi all
Long time lurker, first time poster. I just picked up a Galaxy Nexus from Amazon which turns out to be the Docomo SC-04D. Coming from the Nexus One I'm a little more than irritated that there are so many bloody revisions of this phone (I'm starting to lose sight of why the Nexus line exists..), but I digress. For reference, I'm located in the US running on T-Mobile.
The phone is running stock 4.0.1, and came unlocked out of the box. I gained root access via the GNEX root toolkit.
Shortly after I booted the phone for the first time (before gaining root) I received a message indicating that there was an update - tried running it, but eventually ended up with an image of the android with a red sign popping out of his chest. I shrugged it off, rebooted the phone and went about my business.
I have since installed Clockworkmod + recovery, and attempted through various ways to flash the 4.0.4 update from Google's site with no success. Tried to flash to 4.0.2, no success their either (either it says installation aborted or some longer string). I've lost my sense of humor at this point (probably doesn't help I'm a few drinks into the evening..) and I'm hoping you all can possibly offer a solution. How do I get from Yakjuxe 4.0.1 to Yakju, ultimately 4.0.4?
Any help would be much appreciated.
Thanks
Andrew

download 4.0.4 yakju images.
connect to your computer.
Fastboot flash the images.

You May need to open up metainf/com/google/Android/updaterscript in the zip with NotePad++ which is a free program and very helpful for editing these files. Then find a line near the beginning with the words assert get prop. delete all the lines with that. It May be one or it might be a couple. Then save and put it back in the zip and flash it
Sent from my GT-P7510 using XDA

Finally got it running, via the toolkit no less (copied the tar into the proper directory and hitting the option to flash a stock google rom). Trying to do it via fastboot didn't appear to work, though I'm sure I ****ed that up somehow. Thanks guys.

quadnad said:
Finally got it running, via the toolkit no less (copied the tar into the proper directory and hitting the option to flash a stock google rom). Trying to do it via fastboot didn't appear to work, though I'm sure I ****ed that up somehow. Thanks guys.
Click to expand...
Click to collapse
Glad you figured it out. No need to fret.

quadnad said:
Finally got it running, via the toolkit no less (copied the tar into the proper directory and hitting the option to flash a stock google rom). Trying to do it via fastboot didn't appear to work, though I'm sure I ****ed that up somehow. Thanks guys.
Click to expand...
Click to collapse
Hi, i have the same Docomo, i have the same hard time to upgrade it, would you mind to share, i am new here. thanks.

daleylay said:
Hi, i have the same Docomo, i have the same hard time to upgrade it, would you mind to share, i am new here. thanks.
Click to expand...
Click to collapse
do you have adb setup?
is it setup correctly?
do you know the adb basics?
if yes to all those, try to fastboot unlock the bootloader first, reboot bootloader, then flash the rom, fastboot reboot bootloader, flash radio and any other images
if not, follow the instructions on setting up adb and fastboot via the dev sticky threads.

Can someone please help me with step-by-step instructions for this using the Toolkit. I have a rooted, unlocked Yakjuxe on 4.0.1 and want to get to 4.0.4 Yakju. Please help me with this. I am not some noob, but I have tried everything, including two guides here on XDA.

quadnad said:
Hi all
Long time lurker, first time poster. I just picked up a Galaxy Nexus from Amazon which turns out to be the Docomo SC-04D. Coming from the Nexus One I'm a little more than irritated that there are so many bloody revisions of this phone (I'm starting to lose sight of why the Nexus line exists..), but I digress. For reference, I'm located in the US running on T-Mobile.
The phone is running stock 4.0.1, and came unlocked out of the box. I gained root access via the GNEX root toolkit.
Shortly after I booted the phone for the first time (before gaining root) I received a message indicating that there was an update - tried running it, but eventually ended up with an image of the android with a red sign popping out of his chest. I shrugged it off, rebooted the phone and went about my business.
I have since installed Clockworkmod + recovery, and attempted through various ways to flash the 4.0.4 update from Google's site with no success. Tried to flash to 4.0.2, no success their either (either it says installation aborted or some longer string). I've lost my sense of humor at this point (probably doesn't help I'm a few drinks into the evening..) and I'm hoping you all can possibly offer a solution. How do I get from Yakjuxe 4.0.1 to Yakju, ultimately 4.0.4?
Any help would be much appreciated.
Thanks
Andrew
Click to expand...
Click to collapse
daleylay said:
Hi, i have the same Docomo, i have the same hard time to upgrade it, would you mind to share, i am new here. thanks.
Click to expand...
Click to collapse
ikghassassin said:
Can someone please help me with step-by-step instructions for this using the Toolkit. I have a rooted, unlocked Yakjuxe on 4.0.1 and want to get to 4.0.4 Yakju. Please help me with this. I am not some noob, but I have tried everything, including two guides here on XDA.
Click to expand...
Click to collapse
I would use this method to flash yakju IMM76D, and then this method to upgrade to IMM76I. Root using this.

efrant said:
I would use this method to flash yakju IMM76D, and then this method to upgrade to IMM76I. Root using this.
Click to expand...
Click to collapse
thank you will give this a try. I already have a rooted device however, with protected SU.

ikghassassin said:
thank you will give this a try. I already have a rooted device however, with protected SU.
Click to expand...
Click to collapse
I don't think it's guaranteed that your root will stick but it might so just be wary of that.

Return to Stock Yakjudv

Right, from the top, I'm a retard and shouldn't have messed with ROM's and custom recovery whilst blindly following a guide (I cant remember which guide, so mistake #1). I have a Telstra (Australian) Galaxy Nexus. I followed a guide to put CWM, Jelly Bean and root on, however I ran into a few problems and wanted to revert to my stock ROM, well I never performed a backup of my original ROM (mistake #2). I went looking and someone posted a Telstra stock ROM in CWM backup form here on xda, I successfully restored it and am *mostly* happy with the results, however no I cannot recieve OTA updates, which seems to be due to the prop file and others assert failing. Basically, I've learnt my lesson and want to be a good boy and go back to a non-root, completely out of the box state so if in the future, I need to return the phone for warranty, I can without fear of recourse for messing with the phone.
So again, I'm a tard, but can you help me?
EDIT: Mistake #3, I went back through my downloads and found the files I used from the guide I cant find to show you, but it DID involve Busybox which I have since read screws **** up.

http://forum.xda-developers.com/showthread.php?t=1626895
alll you need to know

atifsh said:
http://forum.xda-developers.com/showthread.php?t=1626895
alll you need to know
Click to expand...
Click to collapse
I've been over that thread twice now and cant find the Return to Stock instructions, am I blind? (happy to be proven wrong)

Syn3rgi3 said:
Right, from the top, I'm a retard and shouldn't have messed with ROM's and custom recovery whilst blindly following a guide (I cant remember which guide, so mistake #1). I have a Telstra (Australian) Galaxy Nexus. I followed a guide to put CWM, Jelly Bean and root on, however I ran into a few problems and wanted to revert to my stock ROM, well I never performed a backup of my original ROM (mistake #2). I went looking and someone posted a Telstra stock ROM in CWM backup form here on xda, I successfully restored it and am *mostly* happy with the results, however no I cannot recieve OTA updates, which seems to be due to the prop file and others assert failing. Basically, I've learnt my lesson and want to be a good boy and go back to a non-root, completely out of the box state so if in the future, I need to return the phone for warranty, I can without fear of recourse for messing with the phone.
So again, I'm a tard, but can you help me?
EDIT: Mistake #3, I went back through my downloads and found the files I used from the guide I cant find to show you, but it DID involve Busybox which I have since read screws **** up.
Click to expand...
Click to collapse
As I understand it, you should just be able to re-apply a stock GSM ROM to your Galaxy Nexus to get back to the original state of things. That's the whole point of a Nexus - it's stock with no customisations etc. It sounds like you'll have start from the very beginning and reinstall apps etc. but I guess you've already bitten that bullet, and presumably you're happy with your current ROM configuration?
It's not clear what recovery you have installed at the moment. You've made mention of CWM ... Clockwork Mod recovery possibly installed in that case? Again, as I understand it, Clockwork Mod recovery means you can't <s>receive</s> apply OTA updates. If you're on a stock ROM you should still receive notification about them though? If you are truly on stock, but have the Clockwork Mod recovery installed you can reinstall the stock boot recovery image. You should be able to find the stock images via a google search easily enough.
Once you've determined which recovery you currently have installed you'll have a better idea of how to get back to stock everything.
Above all, don't panic
PS I could add that busybox doesn't screw stuff up ... it just allows you to screw things up

Hi there,
the most simple way to go back to stock is using the GNex-Toolkit (to be found here http://forum.xda-developers.com/showthread.php?t=1392310) downloading the stock image here https://developers.google.com/android/nexus/images. Almost no chance to mess up your phone with this tool.

real_becksaufex said:
Hi there,
the most simple way to go back to stock is using the GNex-Toolkit (to be found here http://forum.xda-developers.com/showthread.php?t=1392310) downloading the stock image here https://developers.google.com/android/nexus/images. Almost no chance to mess up your phone with this tool.
Click to expand...
Click to collapse
Given a bit more research, I want to be able to get rid of Clockworkmod so I can receive OTA updates again.

Syn3rgi3 said:
Given a bit more research, I want to be able to get rid of Clockworkmod so I can receive OTA updates again.
Click to expand...
Click to collapse
yeah and if tried the tool, you would have seen, that there is an option to flash stock recovery to your phone. you can also disable the bootloader again.
choose your model/build perform action 7 --> option 3 and your back on stock recovery

real_becksaufex said:
yeah and if tried the tool, you would have seen, that there is an option to flash stock recovery to your phone. you can also disable the bootloader again.
choose your model/build perform action 7 --> option 3 and your back on stock recovery
Click to expand...
Click to collapse
I executed that successfully however CWM still exists =/

Syn3rgi3 said:
I've been over that thread twice now and cant find the Return to Stock instructions, am I blind? (happy to be proven wrong)
Click to expand...
Click to collapse
Seriously? The instructions in the first post...
Sent from my Galaxy Nexus using Tapatalk 2

real_becksaufex said:
yeah and if tried the tool, you would have seen, that there is an option to flash stock recovery to your phone. you can also disable the bootloader again.
choose your model/build perform action 7 --> option 3 and your back on stock recovery
Click to expand...
Click to collapse
Disable bootloader?
Pressed from my Maguro

efrant said:
Seriously? The instructions in the first post...
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
This still doesn't solve the problem I have in regard to not having the original Telstra (yakjudv) ROM.

Syn3rgi3 said:
This still doesn't solve the problem I have in regard to not having the original Telstra (yakjudv) ROM.
Click to expand...
Click to collapse
I few things:
1) If you can find a backup of a yakjudv ROM from some Australian user, I'd be happy to help you restore it; but
2) You do realize that yakjudv is still on 4.0.4 (ICS) and not Jelly Bean, right? And you do realize that it only recently (past few weeks) got updated to 4.0.4 while yakju has been on 4.0.4 since March?
3) You do realize that yakju is stock, and the factory images provided by Google are the "stock" ones that get updated first. yakjudv is a Samsung build, not a stock Google build.

LOL, Telstra
Syn3rgi3 said:
Right, from the top, I'm a retard and shouldn't have messed with ROM's and custom recovery whilst blindly following a guide (I cant remember which guide, so mistake #1). I have a Telstra (Australian) Galaxy Nexus. I followed a guide to put CWM, Jelly Bean and root on, however I ran into a few problems and wanted to revert to my stock ROM, well I never performed a backup of my original ROM (mistake #2). I went looking and someone posted a Telstra stock ROM in CWM backup form here on xda, I successfully restored it and am *mostly* happy with the results, however no I cannot recieve OTA updates, which seems to be due to the prop file and others assert failing. Basically, I've learnt my lesson and want to be a good boy and go back to a non-root, completely out of the box state so if in the future, I need to return the phone for warranty, I can without fear of recourse for messing with the phone.
So again, I'm a tard, but can you help me?
EDIT: Mistake #3, I went back through my downloads and found the files I used from the guide I cant find to show you, but it DID involve Busybox which I have since read screws **** up.
Click to expand...
Click to collapse
DO NOT GET YAKJUDV!!! Try and just get Yakju, Then you will get your updates from Google NOT Telstra. You don't need the Telstra stock rom, you can use Google's Yakju. I have a Telstra one and I get updates from google because I put Yakju. You will need to flash the ROM though your pc. I have been through what you have with the exact phone (Telstra one), If you need any help you can PM me

I agree with the post from Atifsh.
The guide offered by Efrant gives you, step by step, everything you need to reach your goal.
Contrary to your case I did not need to change the factory ROM but I applied the rest of the guide (for instance post 855 in Efrant thread shows what I did).
Since I want to learn I refuse, so far, to rely on a toolkit.
I deeply share Efrant philosophy of learning. And I agree on the purpose of the XDA forum. It is not a walking clinic, it is a hospital implementing new medecines:laugh:.
Finally, taking into account my age I am closer to the hospital than to the clinic.
Thanks to Efrant and few others I am doing "stuff" I did not know I could do.
And, yes I am over the time I used to want and get everything at once.

efrant said:
I few things:
1) If you can find a backup of a yakjudv ROM from some Australian user, I'd be happy to help you restore it; but
2) You do realize that yakjudv is still on 4.0.4 (ICS) and not Jelly Bean, right? And you do realize that it only recently (past few weeks) got updated to 4.0.4 while yakju has been on 4.0.4 since March?
3) You do realize that yakju is stock, and the factory images provided by Google are the "stock" ones that get updated first. yakjudv is a Samsung build, not a stock Google build.
Click to expand...
Click to collapse
I understand all the benefits of yakju, however I want to revert to yakjudv if for any reason in the future I require warranty (the phone is under contract).
I do in fact have a 4.0.1 Nandroid backup from another user on Telstra, I went ahead and restored it through CWM and everything was fine, except I still cannot receive OTA updates, doing some reading finds I need to get rid of CWM and revert to stock recovery, so how do I do this?

Syn3rgi3 said:
I understand all the benefits of yakju, however I want to revert to yakjudv if for any reason in the future I require warranty (the phone is under contract).
I do in fact have a 4.0.1 Nandroid backup from another user on Telstra, I went ahead and restored it through CWM and everything was fine, except I still cannot receive OTA updates, doing some reading finds I need to get rid of CWM and revert to stock recovery, so how do I do this?
Click to expand...
Click to collapse
As you say, the problem is you need the stock recovery for the build that you are on. What build is the backup you restored? If it is ITL41F, then you are in luck. Go to this thread and download any one of the two yakjudv updates to /sdcard. Use CWM to flash it, and you will be all set -- it will wipe CWM and replace it with the correct stock recovery for that build.
---------- Post added at 08:49 PM ---------- Previous post was at 08:48 PM ----------
And please change the title of this thread to "Return to stock yakjudv" as it is very confusing. Most people refer to stock as yakju or takju for GSM devices.

Syn3rgi3 said:
I understand all the benefits of yakju, however I want to revert to yakjudv if for any reason in the future I require warranty (the phone is under contract).
I do in fact have a 4.0.1 Nandroid backup from another user on Telstra, I went ahead and restored it through CWM and everything was fine, except I still cannot receive OTA updates, doing some reading finds I need to get rid of CWM and revert to stock recovery, so how do I do this?
Click to expand...
Click to collapse
Can you please post the back up on here please via drop box or something, I need the same thing so I can return for a warranty issue however everywhere I look I just find silly people trying to inform me that I should use Google builds and no Samsung/Telstra build. I know all this however my phone is now on life support and everything seems to be going wrong so I just want to return to out of the box and return it.
---------- Post added at 07:36 PM ---------- Previous post was at 07:31 PM ----------
I love it when people ignore the question in the OP and just decide to tell others to flash different firmware. This isnt helpful in any way when trying to return your device to Telstra in Australia as that's not what come with it so they will just give you your faulty POS back and laugh in your face because you are no longer covered by the warranty.

picton said:
Can you please post the back up on here please via drop box or something, I need the same thing so I can return for a warranty issue however everywhere I look I just find silly people trying to inform me that I should use Google builds and no Samsung/Telstra build. I know all this however my phone is now on life support and everything seems to be going wrong so I just want to return to out of the box and return it.
I love it when people ignore the question in the OP and just decide to tell others to flash different firmware. This isnt helpful in any way when trying to return your device to Telstra in Australia as that's not what come with it so they will just give you your faulty POS back and laugh in your face because you are no longer covered by the warranty.
Click to expand...
Click to collapse
Have you tried returning a device with yakju and have Telstra give you back your "faulty POS" back? Have you heard of others who have experienced that? On the contrary, I have heard of many people returning their non-yakju-bought device with yakju, and have had full warranty.
And if you would have searched before lipping off, you would have found this: http://forum.xda-developers.com/showpost.php?p=29898676&postcount=175

efrant said:
Have you tried returning a device with yakju and have Telstra give you back your "faulty POS" back? Have you heard of others who have experienced that? On the contrary, I have heard of many people returning their non-yakju-bought device with yakju, and have had full warranty.
And if you would have searched before lipping off, you would have found this: http://forum.xda-developers.com/showpost.php?p=29898676&postcount=175
Click to expand...
Click to collapse
I have tried that link bro and it wont flash in CWM. I just get a red triangle with a robot on it. A mate of mine tried to take his back due to a similar problem im having and he was told he had played with the device and wouldn't fix it under warranty and wanted to charge him something stupid to fix it. I'm not giving ya lip but I have been looking for the last 6 hours and in every thread about this subject everyone is saying the same thing.

picton said:
I have tried that link bro and it wont flash in CWM. I just get a red triangle with a robot on it. A mate of mine tried to take his back due to a similar problem im having and he was told he had played with the device and wouldn't fix it under warranty and wanted to charge him something stupid to fix it. I'm not giving ya lip but I have been looking for the last 6 hours and in every thread about this subject everyone is saying the same thing.
Click to expand...
Click to collapse
Ok, are you flashing it in CWM? The "red triangle with a robot" IS the stock recovery, it is not an error. What is the exact procedure you are using to flash it?

[Q] Please help. Custom ROMs constantly rebooting

ok let me just preface this by saying that i am a complete moron and didn't make a nandroid back up. i am new to this stuf obviously and didnt research enough before i dove in.
also this is referring to the htc on v cdma on virgin mobile.
so i was able to successfully unlock and root the phone. bootloader says unlocked and root checker from the market said i had full root access.
i installed the team win recovery on the phone. the first rom i flashed was the cdma pacman rom from here. i did a full wipe and flashed the rom, and then flashed the kernel from said rom via fastboot on my pc. upon firing it up, it boots and gets through the boot animation and into the OS. but after about 10 seconds my service shuts off (it shows a little R above my reception bars) and the phone reboots. just does this over and over.
so i thought maybe it was the ROM so i tried AOKP jellybean. same issue.
any idea what i did wrong here? thanks in advance.

lol, i had the same problem as you. It happens because of the OTA update or radio version, try using this:
http://forum.xda-developers.com/showthread.php?t=2018518
I just followed Solution 1 and it worked for me, I was originally on CWM but moved to TWRP cause it's more convenient.
After using the RUU you'll be back to bone-stock and will have to unlock the bootloader and all that fun stuff all over again that's if you use solution 1; however, atleast you'll be able to get the stock-rom backed up again for just-in-case. Skip OTA updates, and then proceed to recover and then start rom flashing/fastbooting kernel and all that fun stuff.

reID_entify said:
lol, i had the same problem as you. It happens because of the OTA update or radio version, try using this:
http://forum.xda-developers.com/showthread.php?t=2018518
I just followed Solution 1 and it worked for me, I was originally on CWM but moved to TWRP cause it's more convenient.
After using the RUU you'll be back to bone-stock and will have to unlock the bootloader and all that fun stuff all over again that's if you use solution 1; however, atleast you'll be able to get the stock-rom backed up again for just-in-case. Skip OTA updates, and then proceed to recover and then start rom flashing/fastbooting kernel and all that fun stuff.
Click to expand...
Click to collapse
awesome thank you so much. i am slightly confused on which one to download though. i am assuming it is this one here, the only one i see with sprint/vm branding. RUU​_PRIMO​_C_ICS​_40A​_Sprint​_WWE​_VM_1​.08.652​.6_Radio​_1.00​... i'll give it a shot

yea that's the one, it's an executable file, just make sure you follow the directions for RUU.

reID_entify said:
yea that's the one, it's an executable file, just make sure you follow the directions for RUU.
Click to expand...
Click to collapse
worked like a charm! thanks so much!!!
now to try putting a new rom on here again lol....

For future references I suggest not updating the OTA since its known to cause a lot of problems due to radio discrepancies. I'm glad you were able to fix yours though.
Sent from my Full Android on PrimoC using xda premium

t0ltespr..? WHAT?

Hello everybody. So, let me tell you my story.
Back a few months ago, I rooted my phone. At start I liked it a lot, then I decided there might be a lot of problems with it, so decided to unroot it. Searched all over XDA, found a way to unroot, unrooted. Now more details. I rooted it with cfm-autoroot-whatever, then in SuperSU checked that I don't want root, and was naive I got rid of root. I was wrong, so searched XDA, found that the only way out was to flash the original OS(/recovery?) of the phone. So, thanks to guys here on XDA, they provided me with a link to the original recovery. I tried updating a rooted phone OTA, first time it failed, same story was with the 2nd try. 3rd try, however, was successful. Well, almost. It started, as I thought, to update, but then the phone wouldn't turn on - all it could do is to go into Download mode. Thankfully enough, I had Odin (thanks to XDA guys for whicever time). I launched Odin and flashed the phone with stock recovery.
Now I have SPH-L900, L900VPUCNE2, Device status is Official, but...
That's why I'm here, finally.
Recently I downloaded CPU-Z for my phone, and when I opened "System" tab, the first thing I see is this:
Model SPH-L900 (t0ltespr)
What? Really? I thought it's for rooted phones, or at least for some not stock recovery. So, does that mean I don't have a stock recovery? Does that mean my phone is rooted even though I didn't root it after flashing with "stock" recovery?
I can find the threads, I think I bookmarked them if you need.

I'll try to explain
Look in cpu-z under system if at the bottom "Root Access: No" then your phone is not rooted.
now if your wondering about "t0ltespr" it is the code name for the SPH-L900 but every dev uses "l900" from what i can see.

NeoGman said:
Look in cpu-z under system if at the bottom "Root Access: No" then your phone is not rooted.
now if your wondering about "t0ltespr" it is the code name for the SPH-L900 but every dev uses "l900" from what i can see.
Click to expand...
Click to collapse
CPU-Z says the phone is not rooted. Really, my question has been answered: why the app says my phone is t0ltespr. Thanks.

[Q] HELP!! Have I bricked my new device!? SO WORRIED!!

Hey guys,
I'm kinda new to the HTC/Android world, found this community a damn good place to find support.. But now I've hit a road block.
Basically, I've been eager to root from day 1 of getting my first htc handset, I came across from jailbreak and loved the fact of customizability with Android.
So I had the Google play edition(I think, all geared towards Google) running Kit Kat 4.4.4. Love it, big Google user so this all tied together lovely.
Here is the Situation.
I found a video on youtube, cannot provide URL as I'm in work at the moment, but it was root guide from scratch. Fresh windows OS, seemingly a phone fresh out the box.. you get the idea.
I used the Hasoon2000 tool to root the device. Installed ADB etc on my pc, signed up as a a dev, got the Key for device, sent in and received my .bin file. I got up to actually rooting my device, well pleased and happy. Using TWRP via Hasoon2000.
But here is where **** hits the fan.
The device needed to update, It took me back to 4.4.2 but Im unsure on how to get back to most up to date OS and keep the root.
But when I reboot to install this, it goes into TWRP. no other way around this.
Queried this on another forum, decided to continue to be patient... but no replies, in the mean time I restored my apps and have a fiddle, see what the root function can do for myself.
I installed "Freedom 1.0.6" and a program called "Market Share"- Hate iAP, some games are ridiculously priced for the smallest of things, I just wanted to sandbox plague inc. ;(
Now the device is stuck in a boot loop, phone starts up, see the home screen for a bout 40 seconds/ one minute.. Some times I unlock the device and it goes back to flash screen then.. others I boot an app and its slides away once more.
This happened close to 15x before I left for work this morning and I imagine its just going to repeat this and run the battery - I tried to stop this loop by going into TWRP and possibly choosing to boot system this way may of stopped it.. but when I was on the boot screen with those options.. It said Tampered at top of screen and S-On- which has scared me quite a bit..
What the hell has happened!?
I'm desperate to know and don't want to have this damn thing bricked! Please help.. try explain like I'm 5, as said I'm new to a lot of this! >.<

first off, if the screen comes on, its not bricked.
esenfur said:
But here is where **** hits the fan.
The device needed to update, It took me back to 4.4.2 but Im unsure on how to get back to most up to date OS and keep the root.
But when I reboot to install this, it goes into TWRP. no other way around this.
Click to expand...
Click to collapse
Do you mean you accepted an official OTA? I think that is what you are saying. You should not be accepting OTAs on a phone that has been bootloader unlocked, custom recovery, etc. unless you know exactly what you are doing and what the result will be (which is clearly not the case).
Stock recovery is needed to install an OTA. That is why it keeps going to TWRP, then it doesn't find stock recovery and reboots, hence the loop you are stuck in. Try to find the OTA file and delete it.

redpoint73 said:
first off, if the screen comes on, its not bricked.
Do you mean you accepted an official OTA? I think that is what you are saying. You should not be accepting OTAs on a phone that has been bootloader unlocked, custom recovery, etc. unless you know exactly what you are doing and what the result will be (which is clearly not the case).
Stock recovery is needed to install an OTA. That is why it keeps going to TWRP, then it doesn't find stock recovery and reboots, hence the loop you are stuck in. Try to find the OTA file and delete it.
Click to expand...
Click to collapse
Thank you for fast response.
Official OTA - being that the phone its self said "Update the OS" - I just accepted this, hit download and began install as a reboot- didnt spot implications. As said, noob, followed a tut. If it highlighted DO NOT UPDATE or.. IF U WANT UPDATE NOW FOLLOW THIS- Great, but nothing of the sort?
Is the OTA file basically the .exe for the OS- so find it and delete it.. although I dont have enough time to navigate and establish where the file actually is located!
Or do you have any links to tutorials I could possibly follow?
Side note- when this loop started I deleted

esenfur said:
Or do you have any links to tutorials I could possibly follow?
Click to expand...
Click to collapse
This is really your main issue. By following a YouTube video and using a Toolkit, you've failed to actually learn anything or gain any real understanding or knowledge. Do yourself a favor and ditch the tutorials and videos (and toolkit for that matter) and do it the old fashioned way . . . by reading. Videos and step-by-step guides do you no good when things go south (as you've now discovered). And with the prior proper knowledge (usually not gained by following tutorials) this whole mess probably would have never happened in the first place.
A cardinal rule of Android phone modding: DO NOT accept/download/install OTAs (official OS updates) on a modded device unless you know what you are doing, and what the result will be. If in any doubt, simply DO NOT do it.
esenfur said:
Is the OTA file basically the .exe for the OS- so find it and delete it.. although I dont have enough time to navigate and establish where the file actually is located!
Click to expand...
Click to collapse
.exe file is Windows specific. You are looking for a zip file, and it typically starts with "OTA". Don't remember where its saved to, so you will have to search for it. If you can't keep the phone running long enough to do so, mount the memory on your computer and search that way.
Deleting the OTA file worked for me on a past device, although one M8 user in the same position said deleting the file didn't get him out of the loop. Flashing your ROM again, or wiping the internal memory (backup any important personal data first) might be options for you.

redpoint73 said:
you've failed to actually learn anything or gain any real understanding or knowledge.
Click to expand...
Click to collapse
Ive seen quite a fair few ratings for Hasoon2000 and decided to go with it..
redpoint73 said:
Videos and step-by-step guides do you no good when things go south (as you've now discovered).
Click to expand...
Click to collapse
agreed.. theres FAR much more I need to learn.. its scary haha.
redpoint73 said:
DO NOT accept/download/install OTAs (official OS updates)
Click to expand...
Click to collapse
taken on board. I know with my jailbreaks in past it has been a pain, assumed Android would be alot more stable to over write- due to functionality of OS and unlocked features.
I was being generic when I said .exe- basically the installer..
I returned from work to see phone stopped looping.. i could stop the install and deleted the file ASAP.. but now what.. Phone is still bugging me to update, lost the root(got a checker).. so whats the correct procedure!?

I am confused to what you are trying to accomplish at this point, is it to install a OTA, or a recovery? What exactly is going down here?
Me personally to take an OTA is to relock bootloader, install stock recovery, and make sure CID matches. I am S-Off so bootloader means very little, but you can unlock and relock at will when you are S-Off. You will not lose S-Off accepting an OTA.

Try to re-flash the ROM, with stok ROM, using TWRP and clean install. It should work.

hack14u said:
I am confused to what you are trying to accomplish at this point, is it to install a OTA, or a recovery? What exactly is going down here?
Me personally to take an OTA is to relock bootloader, install stock recovery, and make sure CID matches. I am S-Off so bootloader means very little, but you can unlock and relock at will when you are S-Off. You will not lose S-Off accepting an OTA.
Click to expand...
Click to collapse
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8

esenfur said:
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
Click to expand...
Click to collapse
First of all once the bootloader is unlocked you don't have to relock it to get OTA.
As I undersand you have done the following:
1) Unlock using HTCDev-Method
2) flashed a custom revocery (TWRP in your case)
3) flashed a supersu too!?
To install the OTA means loosing root acces. Thus you have to re-root it after the OTA is done. The other problem ist that STOCK OTAs don't work with a custom recovery. Meaning you would have to flash a stock recovery first, install the OTA second (as long as you didn't change anything an just root), and re-root third.
Let's have a look which stock recovery you would need:
1) reboot to bootloader
2) connect the phone to you PC and open cmd in you adb/fastboot folder
3) enter "fastboot getvar all"
4) paste this information here (but DELETE the IMEI and SERIAL NUMBER before posting!!)
As soon as we know which stock recovery you need we will go on.

esenfur said:
Ive seen quite a fair few ratings for Hasoon2000 and decided to go with it..
Click to expand...
Click to collapse
I'm not saying there is anything "wrong" with the toolkit, per se. For the most part, it does what its intended to do.
But it also shortcuts the learning process, and facilitates folks rooting the phone without gaining the proper knowledge. This is a dangerous thing.
This is just my opinion. But I strongly believe it. If you can't accomplish these things without a toolkit, you shouldn't be rooting your phone in the first place.
Others use the toolkits, and love them. They are more than entitled to have their own opinion. But when things go south, the toolkits aren't going to help; and those folks don't have the proper knowledge and they come running here. So you tell me what is the "best" way to root the phone?
esenfur said:
I was being generic when I said .exe- basically the installer..
Click to expand...
Click to collapse
I already figured this was probably the case. But I found it better to provide the exact information on what file to delete; rather than leaving it open to the possibility of you and/or others being misinformed.
esenfur said:
Phone is still bugging me to update, lost the root(got a checker).. so whats the correct procedure!?
Click to expand...
Click to collapse
Sounds like you still have TWRP installed, so just flash SU or SuperSU to gain root.
After that, you can use Titanium Backup or similar app to find the update process and freeze it, to stop the update notifications.
Don't remember the exact process (this is where searching and reading comes in for you) but its something like "drm..." or "updater".

I have this situation before,what i do is find the right stock recovery and flash..after ota done flash back custom recovery..?

esenfur said:
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
Click to expand...
Click to collapse
At this point after seeing this, I would suggest you take some time and start reading. All of your answers are here in the forums. Knowledge is power and within the pages of this site you will find everything you need.
To take the OTA find a stock recovery, to flash ROM's find the one you like and flash via your favorite recovery.