[Q] How do I get past "initiating swagger" boot loop - HTC One V

Hello,
I'm new to the OneV phone (CDMA), coming from the awesome Rezound. Starting from stock, I used Hasoons One V all in one kit. I'm unlocked and using TWRP 2.2. I first wiped my phone, installed the Nov 18 aokp primoc unofficial, flashed gapps-jb-4.2-V1-20121117-signed, and then flashed the extracted boot.img from the same rom using the command prompt fastboot flash. I did this process a few times now, but I still get stuck at the loop screen.
I've also tried flashing Jellyboot5.
Anyone have an idea what I am doing wrong? I've flashed roms many times on the Rezound, but it was so much simpler!

http://forum.xda-developers.com/showthread.php?t=1996665

cybervibin said:
http://forum.xda-developers.com/showthread.php?t=1996665
Click to expand...
Click to collapse
Thanks for responding. So if the kernal is a .zip file, I should rename the entire file "boot.img" correct? I don't extact the boot.img file from the zip...

it will be in .img format by default if not try opening it and see!

cybervibin said:
it will be in .img format by default if not try opening it and see!
Click to expand...
Click to collapse
Right, I figured the boot.img inside the kernal .zip is all that is necessary. I still can't figure out where I'm flashing wrong. I was able to successfully flash my nandroid of my stock.
1. In TWRP, I wiped cache/davilk, system, and did a factory reset
2. Then flashed a stable/nightlies version of rukins AOKP jellybean
3. Flashed gapps (also tried w/o flashing this)
4. In the bootloader, I flashed the boot.img in cmd (tried from rom .zip and jellyboot)
5. After phone restarted it was at the stuck at the boot loop "initiating swagger" *sigh*
Maybe its the rom version I'm using? Can you or someone recommend a good rom to start off with along with what kernal I should use?

ninjastic said:
Right, I figured the boot.img inside the kernal .zip is all that is necessary. I still can't figure out where I'm flashing wrong. I was able to successfully flash my nandroid of my stock.
1. In TWRP, I wiped cache/davilk, system, and did a factory reset
2. Then flashed a stable/nightlies version of rukins AOKP jellybean
3. Flashed gapps (also tried w/o flashing this)
4. In the bootloader, I flashed the boot.img in cmd (tried from rom .zip and jellyboot)
5. After phone restarted it was at the stuck at the boot loop "initiating swagger" *sigh*
Maybe its the rom version I'm using? Can you or someone recommend a good rom to start off with along with what kernal I should use?
Click to expand...
Click to collapse
I was able to figure out that I needed to flash a older RUU to be able to flash a custom rom. :laugh:

ninjastic said:
Hello,
I'm new to the OneV phone (CDMA), coming from the awesome Rezound. Starting from stock, I used Hasoons One V all in one kit. I'm unlocked and using TWRP 2.2. I first wiped my phone, installed the Nov 18 aokp primoc unofficial, flashed gapps-jb-4.2-V1-20121117-signed, and then flashed the extracted boot.img from the same rom using the command prompt fastboot flash. I did this process a few times now, but I still get stuck at the loop screen.
I've also tried flashing Jellyboot5.
Anyone have an idea what I am doing wrong? I've flashed roms many times on the Rezound, but it was so much simpler!
Click to expand...
Click to collapse
Did you happen to install an ota update when you still had your stock rom on your phone?
---------- Post added at 07:39 PM ---------- Previous post was at 07:38 PM ----------
ok.... never mind

Can you please elaborate on what you mean by flashing an older RUU? I am stuck at the same screen you speak of. I just got the phone and started flashing away. PRIMOC if that matters. Thanks!

It's to restore your phone to stock ...if you got a bootloop or your phone isn't booting

donhashem.dh said:
It's to restore your phone to stock ...if you got a bootloop or your phone isn't booting
Click to expand...
Click to collapse
Thanks for the reply. You are saying to restore my phone using the back up I created using the recovery then reflash?
Or are you saying to download a factory restore and flash that? From what the op states he needed to flash an older build.
---------- Post added at 09:36 PM ---------- Previous post was at 09:03 PM ----------
so I erased my rom, reflashed with the same image and it now boots into the rom. I am seeing a lot of issues though. The android keyboard has FC numerous times. The home button only seems to function one time, it asks which launcher to use, I select on then it will not work as a home button again. Also the button that shows all open application is opening context menus (the ... you see on some apps) instead of showing recent apps I tried reflashing again with the same results. Thoughts/comments?

are u cdma?

EDIT: Issue I has was unrelated to this thread I believe. If anyone else experiences what I described read this post, I outline everything I did and how to fix it (different gapps file )

mrdally204 said:
Can you please elaborate on what you mean by flashing an older RUU? I am stuck at the same screen you speak of. I just got the phone and started flashing away. PRIMOC if that matters. Thanks!
Click to expand...
Click to collapse
For anyone else reading this (and thx to donhashem below for elaborating) the stock RUU can be found here. Kudos to all who put these links together :good:

Related

Both CM9/CM10 hangs at boot.

My procedure in chronological order:
Flashed recovery TWRP 2.3
Wiped everything possible in the wipe-tab
Installed CM9/10 from zip on SD-card (zip contains META-INF, system and boot.img)
Flashed boot.img from the zip file CM9/10
Issued the command fastboot erase cache
Unplugged cable and reboot
What happens is that I am stuck at the HTC booting screen. I have been here for about 30-40 minutes. If I try any adb shell command I receive this error: - exec '/system/bin/sh' failed: No such file or directory (2) -. Clearly, something is not right here. I will not speculate because I lack the knowledge to do so. Any help is appreciated because I have been phone-less for a day now and it is getting irritating. Thanks!
Seems you did everything correctly.
Try to flash via ClockWorkMod recovery.
Sent from my HTC One X
TToivanen said:
Seems you did everything correctly.
Try to flash via ClockWorkMod recovery.
Click to expand...
Click to collapse
I just did the same procedure as before but with clockworkmod instead. Still hung at booting screen. I get the same error as before. Is root access a must? I have not done any exploit, only thing I have done is unlocked my boot loader at HTCDev.
zettez said:
I just did the same procedure as before but with clockworkmod instead. Still hung at booting screen. I get the same error as before. Is root access a must? I have not done any exploit, only thing I have done is unlocked my boot loader at HTCDev.
Click to expand...
Click to collapse
Root should not be needed since most roms are rooted by default.
Did you flash gapps?
TToivanen said:
Root should not be needed since most roms are rooted by default.
Did you flash gapps?
Click to expand...
Click to collapse
No, I have not. Maybe I should give it a try? Or is it not required? Should I not be able to start the phone without any gapps?
Do you by chance have any ROM you can recommend that works so I could try it out and exclude problems? Would very like to know if it is my phone or ROM that is buggy.
It should boot without them, but better to give it a try.
Ironically, I've been using CM10 for more than a month now and never had any problems booting.
Sent from my HTC One X
If you have an hboot newer than 1.12 you need a different boot.img, check the bottom if the ROM OP.
TToivanen said:
It should boot without them, but better to give it a try.
Ironically, I've been using CM10 for more than a month now and never had any problems booting.
Click to expand...
Click to collapse
Would you mind telling me which CM10 build you are using and which boot.img you flashed?
BenPope said:
If you have an hboot newer than 1.12 you need a different boot.img, check the bottom if the ROM OP.
Click to expand...
Click to collapse
I have hboot 1.3 or something I think. I downloaded the different builds at get.cm. Where can I get the boot.img if not the one in the zip file? Do you mean whichever thread that CM have posted themselves here on xda? Would you mind sending a link to where I can find the boot.img?
zettez said:
I have hboot 1.3 or something I think. I downloaded the different builds at get.cm. Where can I get the boot.img if not the one in the zip file? Do you mean whichever thread that CM have posted themselves here on xda? Would you mind sending a link to where I can find the boot.img?
Click to expand...
Click to collapse
Normally it would be found in the bottom of CM10 threads OP but the link is down.
Here you go:
http://forum.xda-developers.com/showpost.php?p=34829297&postcount=9173
Remember to repack it with the one found in zip. Repack tool stickied on android development forum.
Sent from my HTC One X
TToivanen said:
Normally it would be found in the bottom of CM10 threads OP but the link is down.
Here you go:
http://forum.xda-developers.com/showpost.php?p=34829297&postcount=9173
Remember to repack it with the one found in zip. Repack tool stickied on android development forum.
Click to expand...
Click to collapse
Thanks, but still a no go. What I did was take the modified boot from your link and the boot.img from the zip file, do the online converter as stickied on the forum, then did the procedure all again but this time I flashed the new boot.img I got from combining the old and the new boot.img. Still hangs at boot. Very annoying. I am currently using a modified stock ROM and I dislike it very much.
Hey,
I have exactly the same issue. I've unlocked my bootloader using the method as specified by htcdev.com. Then I flashed the newest CWM recovery. But if I flash any ROM, I'm stuck at its boot animation. However if I then unzip the boot.img from the ROM, and flash that (fastboot flash boot boot.img), my phone won't boot past HTC screen. Even erasing the cache didn't help (fastboot erase cache).
I've restored the stock ROM using the RUU, however during the process something went wrong and it formatted my sd-card. So I'm stuck with the stock ROM, without any applications or data.
Can anybody help me flash CM10?
My Hboot version is 1.36.0000
And I'm trying to flash the cm-10-20121210-NIGHTLY-endeavoru.zip ROM.
Thanks in advance
Han
irundaia said:
Hey,
I have exactly the same issue. I've unlocked my bootloader using the method as specified by htcdev.com. Then I flashed the newest CWM recovery. But if I flash any ROM, I'm stuck at its boot animation. However if I then unzip the boot.img from the ROM, and flash that (fastboot flash boot boot.img), my phone won't boot past HTC screen. Even erasing the cache didn't help (fastboot erase cache).
I've restored the stock ROM using the RUU, however during the process something went wrong and it formatted my sd-card. So I'm stuck with the stock ROM, without any applications or data.
Can anybody help me flash CM10?
My Hboot version is 1.36.0000
And I'm trying to flash the cm-10-20121210-NIGHTLY-endeavoru.zip ROM.
Thanks in advance
Han
Click to expand...
Click to collapse
You cannot use the boot.img that comes with the zip out of the box if you have Hboot 1.36. What you have to do is repack it, taking the boot.img from the zip file and then a modified boot.img here http://forum.xda-developers.com/show...postcount=9173 (thanks TToivanen), then as I understood it, repack it for instance here http://forum.xda-developers.com/showthread.php?t=1815607, download the repacked boot.img and flash that.
With that said, I could not get it running but it might be something wrong with my phone. Please try this out and tell me if it works or not so I may start to conclude where the error lies.
zettez said:
Thanks, but still a no go. What I did was take the modified boot from your link and the boot.img from the zip file, do the online converter as stickied on the forum, then did the procedure all again but this time I flashed the new boot.img I got from combining the old and the new boot.img. Still hangs at boot. Very annoying. I am currently using a modified stock ROM and I dislike it very much.
Click to expand...
Click to collapse
Sorry, but all I can say is that you did a mistake at some point.
Try installing again with full wipe and remember to wipe cache and dalvik.
You are referring to the official CM10 and not Trip's or any other builds right?
TToivanen said:
Sorry, but all I can say is that you did a mistake at some point.
Try installing again with full wipe and remember to wipe cache and dalvik.
You are referring to the official CM10 and not Trip's or any other builds right?
Click to expand...
Click to collapse
Will try again. I got the latest build from http://get.cm/?device=endeavoru. Will try cm-10-20121213-NIGHTLY-endeavoru.zip as it came out today.
zettez said:
You cannot use the boot.img that comes with the zip out of the box if you have Hboot 1.36. What you have to do is repack it, taking the boot.img from the zip file and then a modified boot.img here http://forum.xda-developers.com/show...postcount=9173 (thanks TToivanen), then as I understood it, repack it for instance here http://forum.xda-developers.com/showthread.php?t=1815607, download the repacked boot.img and flash that.
With that said, I could not get it running but it might be something wrong with my phone. Please try this out and tell me if it works or not so I may start to conclude where the error lies.
Click to expand...
Click to collapse
I did that and now my phone is still stuck on the HTC screen. Trying to restore my backup of the stock ROM atm.
---------- Post added at 04:35 PM ---------- Previous post was at 04:30 PM ----------
hmm the backup was useless... Off to the RUU it is....
irundaia said:
[/COLOR]hmm the backup was useless... Off to the RUU it is....
Click to expand...
Click to collapse
You flashed the stock boot.img before restoring?
irundaia said:
I did that and now my phone is still stuck on the HTC screen. Trying to restore my backup of the stock ROM atm.
Click to expand...
Click to collapse
I see, then it is not only I who have this problem.
And a heads up, if the backup would go wrong, I currently use this ROM and it works pretty good if you want stock or cannot be arsed to get a root exploit for the stock ROM. http://forum.xda-developers.com/showthread.php?t=2035203.
Would be great if anyone has any ideas why irundaia and I cannot make CM10 work?
TToivanen said:
You flashed the stock boot.img before restoring?
Click to expand...
Click to collapse
You're right, I forgot to do that. I does boot now, still at a loss though. Can't we downgrade our Hboot to a version in which we know that CM can be flashed?
Kinda out of ideas here...
Can you confirm that the boot.img flashes ok? (should say OKAY)
Also confirm that you have endeavoru and not evita.

One X stuck at "HTC ONE X"

ok im truely frustrated after trying to figure this out in past 2 days and reading more than 60 threads/websites.
Problem:
my one x was running 4.0.4 rooted +supre user+CWM, till i got the notification for 4.1 update. i pressed install now and downloaded around 380 MB, during the update phase a red exclamation icon appeared and phone rebooted into 4.0.4.
relocked bootloader, flashed stock recovery and downloaded it again and this time copied the OTA file before pressing install. so i installed and same issue.
uninstalled Avast AV (android) and ran through the same process again, same thing, started up into 4.0.4 again.
unlocked the bootloader, flashed CWM 5.8.4, copied ota file into phone and renamed it to update.zip. ran it from recovery menu and got status 7 error.
downloaded and ran JBFWTOOL21 and followed the instructions, during one of the steps i encountered an error and after restarting the phone i was stock at "HTC One x" with "beatsound" logo at bottom.
NOW NOTHING WORKS
what ive tried so far:
relocked loader and flashed stock recovery and tried Factory Reset, no luck.
unlocked loader and flash CWM and tried wiping cache and wiping disk. nothing.
relocked loader,flashed recovery and ran stock RUU "RUU_ENDEAVOR_U_ICS_40_HTC_ARA_1.28.415.9_Radio_1.1204.103.14_release_25679_signed" but it doesnt work, give an error related to version numbers or something.
extracted system.img, boot.img from RUU temp folder ROM.zip and tried to flash but cant flash system.img (918mb). something about not enough HEAP i think.
from the OTA JB zip extracted recovery.img, boot.img and recovery.img and flashed them. nothing.
downloaded "One_X_All-In-One_Kit_v2.1" and tried kernel flash, nothing.
clearing cache via fastboot command also doesnt work
really appreciate any helpful input guys, im really frustrated. thanks
Oh my.. First, stop unlock and relock of bootloader. Do you have a cwm backup from before all this started? Flashing cwm and restoring that backup will get you far.
The first ota attempt failed due to cwm, always return to stock recovery (recovery.img from your cwm backup image) before applying ota update!
Kind Regards
TwinAdk
unfortunately, no. no backup.
since it all started from the official update i didnt make any backups.
Stop trying flash randomly. Run the following command:
fastboot getvar version-main
it wasnt just random flashing, i starting reading different posts and so tried them all one-by-one to see which works, anyway the output:
version-main: 3.16.415.4
woomera said:
it wasnt just random flashing, i starting reading different posts and so tried them all one-by-one to see which works, anyway the output:
version-main: 3.16.415.4
Click to expand...
Click to collapse
Well that's why the older RUU wouldn't work. You have the latest.
You'll need to go to the ROM backups thread and see if you can get a backup and flash its boot.img and restore it from CWM.
Actually, reboot your PC and try to flash system.img and boot.img again. You will probably need to be locked.
but isnt that the boot.img from "OTA_ENDEAVOR_U_JB_45_S_HTC_ARA_3.16.415.4-2.17.415.2_release_304331jrfus698taf4vm1x"?
cause i have already tried it, didnt work. i have the OTA file.
Modified my post. Look up.
i have boot.img from firmware with hboot 3.16 and 3.19, which one to use?
and the system.img is from stock RUU which is "RUU_ENDEAVOR_U_ICS_40_HTC_ARA_1.28.415.9_Radio_1.1204.103.14_release_25679_signed", will that work?
the OTA JB is a zip file and doesnt have system.img.
Err.. 1.39?
yes
the firmware included in "JBFWTOOL21" is 1.36 which is used by many to manually upgrade to JB but the firmware inside the OTA file itself is 3.19 which is also the version i updated to since i thought its the reason the update doesnt work.
the Hboot version on my phone is 1.39 at the moment.
Hmmm. Looks like you'll have to find a backup in the backups thread and flash it.
BenPope said:
Hmmm. Looks like you'll have to find a backup in the backups thread and flash it.
Click to expand...
Click to collapse
i dont understand, a backup of what? the system.img?
Something similar happened to me....my phone was bootlooping. I flashed a custom rom and it booted up fine... did u try flashing a custom rom?
sridheepan said:
Something similar happened to me....my phone was bootlooping. I flashed a custom rom and it booted up fine... did u try flashing a custom rom?
Click to expand...
Click to collapse
I thought about suggesting that too, but I'm new to flashing so I didn't feel confident enough to do it..
But off the top of my head, a custom rom, complete with boot.img and everything should work..
I'm using http://forum.xda-developers.com/showthread.php?t=2013506, it's super great and support all hboot versions.
No guarantees it will work though.
Kind Regards
TwinAdk
sridheepan said:
Something similar happened to me....my phone was bootlooping. I flashed a custom rom and it booted up fine... did u try flashing a custom rom?
Click to expand...
Click to collapse
guess it worth a try even though i'd rather fix the problem in hand in another fashion.
gonna give it a try and post the results.
k so i downloaded the Blade rom and it worked, thanks "TwinAdk".
so now about JB. should i just use "JBFWTOOL21" or better if i do it manually?
and is this the right order to do it manually: ?
-unlock bootloader
-flash CWM
-flash boot.img
-install from zip in CWM
woomera said:
i dont understand, a backup of what? the system.img?
Click to expand...
Click to collapse
A nandroid backup, like what Clockworkmod recovery makes.
woomera said:
k so i downloaded the Blade rom and it worked, thanks "TwinAdk".
so now about JB. should i just use "JBFWTOOL21" or better if i do it manually?
and is this the right order to do it manually: ?
-unlock bootloader
-flash CWM
-flash boot.img
-install from zip in CWM
Click to expand...
Click to collapse
NP, glad it worked! So now you have a phone that can actually boot up and make phone calls.. Not on the stock rom you wanted, but it's better than when you started this thread
From this point on, you can use a "return to stock" thread for the HOX.
1. Make a NANDROID backup via CWM (so you can get back to what you have now!)
2. Move the backup to your computer, to avoid anything happening to it
3. See this tutorial ([TUT] Getting back to stock after flashing custom roms [Noob friendly])
NOTE: The thread says the following in the top:
NOTE: These instructions require that you have one of the ICS hboot versions in order to work (1.12.0000 or lower). If you have one of the new JB hboots 1.28, 1.31 or 1.33 there is currently no way to return to stock until a JB ruu is released for your device.
Click to expand...
Click to collapse
The "new jb hboots" also refers to 1.39.
I have the 1.39 myself, and i believe i am able to return to stock via my CWM backup of my stock phone, from before i flashed a custom rom the first time.. Is that assumption wrong? Someone more experienced than me to the rescue, please
Kind Regards
TwinAdk
BenPope said:
A nandroid backup, like what Clockworkmod recovery makes.
Click to expand...
Click to collapse
thanks for the clarification
TwinAdk said:
NP, glad it worked! So now you have a phone that can actually boot up and make phone calls.. Not on the stock rom you wanted, but it's better than when you started this thread
From this point on, you can use a "return to stock" thread for the HOX.
1. Make a NANDROID backup via CWM (so you can get back to what you have now!)
2. Move the backup to your computer, to avoid anything happening to it
3. See this tutorial ([TUT] Getting back to stock after flashing custom roms [Noob friendly])
NOTE: The thread says the following in the top:
The "new jb hboots" also refers to 1.39.
I have the 1.39 myself, and i believe i am able to return to stock via my CWM backup of my stock phone, from before i flashed a custom rom the first time.. Is that assumption wrong? Someone more experienced than me to the rescue, please
Kind Regards
TwinAdk
Click to expand...
Click to collapse
i have read the same thing, also "BenPope" mentioned it. so with this version of Hboot (1.39) i cant restore unless its a nandroid backup.
but i dont wanna go back to stock ICS! i wanna finish what i was trying to do in first place, Upgrade to JB.
but no matter what i do i get the "status 7 error". i have tried it with the OTA my phone downloaded and also downloaded it again directly from HTC website via a link from one of the threads in forum.
so status 7 apparently is related to CRC error but how can that be? and what is my option right now to do the upgrade? also bear in mind that before all these happened the normal upgrade process via the "system update" also failed with a red icon error.

[Q] Attempt to mod my phone now almost bricked

Guys,
I'm a newbie to rooting and unlocking world, and I think have done too many things to screw my phone as much as I can.
Device is a PrimeOU based. (India)
Trying to recall the series of accidents that I committed since last 24hrs on my HTC ONE V.
1. Unlocked the bootloader successfully.
2. Rooted the device successfully and installed CWM and copied the file mentioned in this post
3. Entered the recovery mode, backed up my previous ROM from CWM.
4. Flashed the ROM directly (Later I came to know there were a some other steps missed here).
5. And of course, post flashing CYANOGENMOD 10 was stuck in the boot screen.
6. Went back to recovery mode and here I made a biggest mistake, I partitioned the SD card as the CWM logs were showing that one of the ext partition could not be mounted. Because of this, I LOST ALL MY BACKUP DATA.
7. Again, referred one more post from here .. tried copying files, played around but nothing worked.
8. Flashed again from some windows based tool (Can recall its name, its not in my browser history as well). Installed TWAR.
9. Started searching for the stock ROM and found one here
Tried to recover the base ROM but no luck.
10. Found that I should try with RUU to resume my stock ROM. relocked phone flashed the image again.
I see error 155, which says that I should try with another RUU version, but the verdict is that hboot version is older.... came through another post that at this moment there is no RUU version available that suits the hboot compatibility as of now.
Conclusion:
I have now understood, that should not have messed up so much with my phone without any proper education on android rooting unlocking.
Device is now flashed with some version of RUU and recovery mode takes me to default android recovery screen which again reboots the phone.
Is my device bricked? Can we get it back functioning normally? Can we try the below?
1. Is there any way I can recover the deleted backup on my SD card and try recover again? Does the card get formatted completely if a new partition is created.?
2. Should I take it to an authorized service center? Its no longer in warranty, so they will always be happy to get things done for a price.
3. Should I take it to an unauthorized shops who can get back my phone working?
Any help is highly appreciated.Please let me know if you have any other advice too...
Thanks in advance,
Sumanth
R: [Q] Attempt to mod my phone now almost bricked
Don't worry you aren't bricked! Right now is your bootloader unlocked?
mr_nooby said:
Don't worry you aren't bricked! Right now is your bootloader unlocked?
Click to expand...
Click to collapse
Ah well, I had to relock it inorder to get through the RUU flash update.
R: [Q] Attempt to mod my phone now almost bricked
If you can't use a ruu, then you need a custom rom. In order to do that you need to unlock and root again first
mr_nooby said:
If you can't use a ruu, then you need a custom rom. In order to do that you need to unlock and root again first
Click to expand...
Click to collapse
Thanks, first of all, happy to hear that phone is still alive.
I just do not want to mess up any further, unless I get a clear step by step process to root it again.
where can I get such descriptive steps that start from ABC....?
R: [Q] Attempt to mod my phone now almost bricked
http://forum.xda-developers.com/showthread.php?t=1598964 this is a very well done guide, step by step
mr_nooby said:
http://forum.xda-developers.com/showthread.php?t=1598964 this is a very well done guide, step by step
Click to expand...
Click to collapse
Hello Nooby - Thanks a lot for your direction. I will try this and reply by tomorrow (Its 4AM here )
I may sound stupid but one last question - if something goes wrong with this one too, hope the phone wont be bricked?
R: [Q] Attempt to mod my phone now almost bricked
Don't worry you won't brick it
mr_nooby said:
Don't worry you won't brick it
Click to expand...
Click to collapse
Hi Nooby - Successfully unlocked and rooted per the steps in the thread. Now my phone boots up and stops in the CYANOGEMOD boot page, which I had tried to install at the first instance. (Similar case just before loosing my backup)
I shall continue with this stock ROM for ONE V mentioned in the post.
http://forum.xda-developers.com/showthread.php?t=1647052
Observations:
1. I see that CWM or TWRP is one of the requirements for this to work, but I have lost either of these after flashing multiple times...
2. Instructions also say that I should use "Sense kernel Titanium-KISS or Stock kernel".
3. There was an earlier failed attempt to install a CYANOGENMOD 10 but not sure if I'm using a Stock Kernel.
Please advice.
Regards,
Sumanth
R: [Q] Attempt to mod my phone now almost bricked
Ok this is twrp recovery http://forum.xda-developers.com/showthread.php?t=1721749 download it and put it in fastboot folder, then connect the phone in fastboot mode, open cmd, locate your fastboot folder and type fastboot flash recovery nameofrecovery.img, then all you need to do is flash the right kernel and your phone will work normally
---------- Post added at 02:11 PM ---------- Previous post was at 02:06 PM ----------
If now you have cm10, download this kernel http://forum.xda-developers.com/showthread.php?t=1954967 and put it in your fastboot folder, connect your phone in fastboot mode, locate the folder in cmd and type fastboot flash boot nameofkernel.img, when you type that you should see on your phone a loading bar on top right of the screen. When this is done, just reboot your phone and wait some minutes for the rom to boot
---------- Post added at 02:31 PM ---------- Previous post was at 02:11 PM ----------
ok so, now iim on the computer i can write properly u.u now that you have unlocked and rooted again, the first thing you do is flash the twrp recovery via fastboot (i guess you know how to do it if you already unlocked and rooted). once the recovery is installed you can go 2 ways:
1) Use sense rom, http://forum.xda-developers.com/showthread.php?t=1647052 this one is very good, almost like stock rom. In order to do that you follow these steps:
a) download TITANIUM KISS kernel from here http://forum.xda-developers.com/showthread.php?t=1765687
b) put the kernel in fastboot folder and flash it, you need to open cmd, locate your fastboot folder, connect the phone in fastboot mode and type fastboot flash boot nameofkernel.img, on the screen you will see the loading bar (it's very quick), once its done, reboot into recovery.
c)from the recovery, go to advanced->mount usb storage, the computer will open your phone folder, just take the rom and copy it to your sd card, when it's done copying, just do unmount usb storage.
d)from the recovery, do wipe->factory reset, it will delete the old rom on your phone
e)now you are ready to flash the rom, from the recovery goto install and select the rom from the list.
It will take like 5-6 minutes to boot the first time, so dont worry and wait.
2) Use cyanogenmod10, then you need hellboy kernel and the rom of course. steps:
a)download hellboy kernel http://forum.xda-developers.com/showthread.php?t=1954967
b)same as above
c)same as above
d)same as above
e)same as above
this will also take some minutes to boot the first time. Once its booted you wont have play store and stuff (only on cyanogen, sense has it already), so you need to do this:
f)mount usb storage
g)download gapps from here http://www.mediafire.com/?k2cb1trw8s2oio2
h)copy gapps to your sd card
i)reboot into recovery and install them, reboot the phone and you are all done!
mr_nooby said:
Ok this is twrp recovery http://forum.xda-developers.com/showthread.php?t=1721749 download it and put it in fastboot folder, then connect the phone in fastboot mode, open cmd, locate your fastboot folder and type fastboot flash recovery nameofrecovery.img, then all you need to do is flash the right kernel and your phone will work normally
---------- Post added at 02:11 PM ---------- Previous post was at 02:06 PM ----------
If now you have cm10, download this kernel http://forum.xda-developers.com/showthread.php?t=1954967 and put it in your fastboot folder, connect your phone in fastboot mode, locate the folder in cmd and type fastboot flash boot nameofkernel.img, when you type that you should see on your phone a loading bar on top right of the screen. When this is done, just reboot your phone and wait some minutes for the rom to boot
---------- Post added at 02:31 PM ---------- Previous post was at 02:11 PM ----------
ok so, now iim on the computer i can write properly u.u now that you have unlocked and rooted again, the first thing you do is flash the twrp recovery via fastboot (i guess you know how to do it if you already unlocked and rooted). once the recovery is installed you can go 2 ways:
1) Use sense rom, http://forum.xda-developers.com/showthread.php?t=1647052 this one is very good, almost like stock rom. In order to do that you follow these steps:
a) download TITANIUM KISS kernel from here http://forum.xda-developers.com/showthread.php?t=1765687
b) put the kernel in fastboot folder and flash it, you need to open cmd, locate your fastboot folder, connect the phone in fastboot mode and type fastboot flash boot nameofkernel.img, on the screen you will see the loading bar (it's very quick), once its done, reboot into recovery.
c)from the recovery, go to advanced->mount usb storage, the computer will open your phone folder, just take the rom and copy it to your sd card, when it's done copying, just do unmount usb storage.
d)from the recovery, do wipe->factory reset, it will delete the old rom on your phone
e)now you are ready to flash the rom, from the recovery goto install and select the rom from the list.
It will take like 5-6 minutes to boot the first time, so dont worry and wait.
2) Use cyanogenmod10, then you need hellboy kernel and the rom of course. steps:
a)download hellboy kernel http://forum.xda-developers.com/showthread.php?t=1954967
b)same as above
c)same as above
d)same as above
e)same as above
this will also take some minutes to boot the first time. Once its booted you wont have play store and stuff (only on cyanogen, sense has it already), so you need to do this:
f)mount usb storage
g)download gapps from here http://www.mediafire.com/?k2cb1trw8s2oio2
h)copy gapps to your sd card
i)reboot into recovery and install them, reboot the phone and you are all done!
Click to expand...
Click to collapse
Okay,, Im all set to start, Let me go back to working Sense ROM and back it up, before I start playing with CM10 any more.
Will keep you posted....
sumanthkulkarni13 said:
Okay,, Im all set to start, Let me go back to working Sense ROM and back it up, before I start playing with CM10 any more.
Will keep you posted....
Click to expand...
Click to collapse
Hi Nooby - So I dont need to flash with TWRP anymore?
Flashing with Sense kernel Titanium-KISS will suffice before I install the myONEv RC9.0 FX+ ROM?
Please advice...
R: [Q] Attempt to mod my phone now almost bricked
sumanthkulkarni13 said:
Okay,, Im all set to start, Let me go back to working Sense ROM and back it up, before I start playing with CM10 any more.
Will keep you posted....
Click to expand...
Click to collapse
Take your time
mr_nooby said:
Take your time
Click to expand...
Click to collapse
Hi Nooby - So I dont need to flash with TWRP anymore?
Flashing with Sense kernel Titanium-KISS will suffice before I install the myONEv RC9.0 FX+ ROM?
Please advice...
R: [Q] Attempt to mod my phone now almost bricked
sumanthkulkarni13 said:
Hi Nooby - So I dont need to flash with TWRP anymore?
Flashing with Sense kernel Titanium-KISS will suffice before I install the myONEv RC9.0 FX+ ROM?
Please advice...
Click to expand...
Click to collapse
You need to flash twrp first then titanium kiss then factory reset and rom at last
mr_nooby said:
You need to flash twrp first then titanium kiss then factory reset and rom at last
Click to expand...
Click to collapse
Ok, noted...
:thanksforyourpatience:
sumanthkulkarni13 said:
Ok, noted...
:thanksforyourpatience:
Click to expand...
Click to collapse
Nooby - TWRP flash Completed I'm now through TWRP successfully.
I open the link to titanium kiss download, shows me a load of file. understand that OC-UV are a kind of presets, excluding them, which one to download? Probably the recent one?
Download Link: http://www.mediafire.com/?e1chs7tzcsstc
sumanthkulkarni13 said:
Nooby - TWRP flash Completed I'm now through TWRP successfully.
I open the link to titanium kiss download, shows me a load of file. understand that OC-UV are a kind of presets, excluding them, which one to download? Probably the recent one?
Download Link: http://www.mediafire.com/?e1chs7tzcsstc
Click to expand...
Click to collapse
this one http://www.mediafire.com/?362drdxcdpkf2s0 , its the latest
mr_nooby said:
this one http://www.mediafire.com/?362drdxcdpkf2s0 , its the latest
Click to expand...
Click to collapse
Update: The ROM upgrade failed. Copied the 393 mb file into the storage sd and tried install post flashing the kernel.
See an error in the recovery that the installation zip could not be opened. I too see an error while opening from my winrar in PC.
Suspect corrupt donwload file. Started new download , 403 MB ... Update to follow...
sumanthkulkarni13 said:
Update: The ROM upgrade failed. Copied the 393 mb file into the storage sd and tried install post flashing the kernel.
See an error in the recovery that the installation zip could not be opened. I too see an error while opening from my winrar in PC.
Suspect corrupt donwload file. Started new download , 403 MB ... Update to follow...
Click to expand...
Click to collapse
yes it's corrupted, my rc9 rom is 403mb too, you need to download again. Before flashing the rom remember to factory reset, it's always better

help android 4.3 stuck at google screen

Hey I've been a long time lurker just haven't posted in forums because I haven't made enough posts Lol.
Well my question is in regards to paranoid android 4.3/3.94.
I've seen lots of people with same issue I havent figured out a fix.
Every 4.3 ROM I flash works fine, until reboot then I get stuck at Google screen. Can't backup or restore. Can't even reflash a 4.2.2. I HAVE to do a full wipe SD card and all, then use adB to sideload a rom.. I've flashed the newest primeD04 boot loader or whatever it is. Still the exact same issue.
I have twrp 4.2.2 I believe , maybe 4.2.0. If that helps..
Please help me I need to be on 4.3 .. And have had to do a full wipe more than 5 times Lol...
antwong45157 said:
Hey I've been a long time lurker just haven't posted in forums because I haven't made enough posts Lol.
Well my question is in regards to paranoid android 4.3/3.94.
I've seen lots of people with same issue I havent figured out a fix.
Every 4.3 ROM I flash works fine, until reboot then I get stuck at Google screen. Can't backup or restore. Can't even reflash a 4.2.2. I HAVE to do a full wipe SD card and all, then use adB to sideload a rom.. I've flashed the newest primeD04 boot loader or whatever it is. Still the exact same issue.
I have twrp 4.2.2 I believe , maybe 4.2.0. If that helps..
Please help me I need to be on 4.3 .. And have had to do a full wipe more than 5 times Lol...
Click to expand...
Click to collapse
sooo you are on latest bootloader latest radio , allways full wipe and it still does that? try doing a full wipe from CWM recovery and flash it again, btw are you on maguro verizon or sprint?
Woodyy said:
sooo you are on latest bootloader latest radio , allways full wipe and it still does that? try doing a full wipe from CWM recovery and flash it again, btw are you on maguro verizon or sprint?
Click to expand...
Click to collapse
I'm on toro. Verizon galaxy nexus.
Well to flash a 4.3 ROM.. I went into TWRP.. team in recovery program. Click factory reset, wipe system, cache and davlik.
Then flash 4.3 ROM, gapps and reboot.
After everything loads I try to reboot and I get stuck at Google screen... I have yet to wipe EVERYTHING because I just figured out how to use adb to side load zips.
Gonna try FULL WIPE SD card and everything then flash 4.3 using adb.
I'm on newest boot loader with fk01 and fk02 radios... Are those newest radios ?
antwong45157 said:
I'm on toro. Verizon galaxy nexus.
Well to flash a 4.3 ROM.. I went into TWRP.. team in recovery program. Click factory reset, wipe system, cache and davlik.
Then flash 4.3 ROM, gapps and reboot.
After everything loads I try to reboot and I get stuck at Google screen... I have yet to wipe EVERYTHING because I just figured out how to use adb to side load zips.
Gonna try FULL WIPE SD card and everything then flash 4.3 using adb.
I'm on newest boot loader with fk01 and fk02 radios... Are those newest radios ?
Click to expand...
Click to collapse
Yep those are the latest radios for verizon, i am on maguro, no problems here... but it seams that there are lots of problems on verizon with 4.3 roms.
---------- Post added at 09:33 PM ---------- Previous post was at 09:25 PM ----------
antwong45157 said:
I'm on toro. Verizon galaxy nexus.
Well to flash a 4.3 ROM.. I went into TWRP.. team in recovery program. Click factory reset, wipe system, cache and davlik.
Then flash 4.3 ROM, gapps and reboot.
After everything loads I try to reboot and I get stuck at Google screen... I have yet to wipe EVERYTHING because I just figured out how to use adb to side load zips.
Gonna try FULL WIPE SD card and everything then flash 4.3 using adb.
I'm on newest boot loader with fk01 and fk02 radios... Are those newest radios ?
Click to expand...
Click to collapse
Try to use latest CWM recovery and then full wipe from recovery, reinstall latest flashable bootloader, reboot in recovery again and flash again PA 3.94 and gaps without ADB sideload
Woodyy said:
sooo you are on latest bootloader latest radio , allways full wipe and it still does that? try doing a full wipe from CWM recovery and flash it again, btw are you on maguro verizon or sprint?
Click to expand...
Click to collapse
Woodyy said:
Yep those are the latest radios for verizon, i am on maguro, no problems here... but it seams that there are lots of problems on verizon with 4.3 roms.
---------- Post added at 09:33 PM ---------- Previous post was at 09:25 PM ----------
Try to use latest CWM recovery and then full wipe from recovery, reinstall latest flashable bootloader, reboot in recovery again and flash again PA 3.94 and gaps without ADB sideload
Click to expand...
Click to collapse
Going to try to side load first with twrp. If all else fails gonna try cwm recovery
Tried to side load with adb... No luck. Worked flawlessly until I rebooted then stuck on the Google screen. Please help!
*
*
*
antwong45157 said:
Tried to side load with adb... No luck. Worked flawlessly until I rebooted then stuck on the Google screen. Please help!
*
*
*
Click to expand...
Click to collapse
Ok, i want some info cuz i am allso confused).
1. what rom do you flash with adb sideload PA 3.94?
2. you said you cant flash 4.2.2 anymore?
3. if you use adb sideload you have the android sdk installed
4. if second and third point are true then use adb to wipe everything from the phone and download stock 4.2.2 img and flash from windows adb command prompt.
Woodyy said:
Ok, i want some info cuz i am allso confused).
1. what rom do you flash with adb sideload PA 3.94?
2. you said you cant flash 4.2.2 anymore?
3. if you use adb sideload you have the android sdk installed
4. if second and third point are true then use adb to wipe everything from the phone and download stock 4.2.2 img and flash from windows adb command prompt.
Click to expand...
Click to collapse
I tried flashing paranoid android 3.94 which is android 4.3 with adb. Hoping it would work different . Nope same result.
I am able to get back on 4.2.2 using adb. I'm on 4.2.2 typing this message . I just need to find out why I can't get on 4.3 with getting stuck at boot screen
This is probably a silly question , but is your bootloader locked I have the gnex toro and it can get testy at times also try flashing this ROM its what I'm currently on and it works great no issues its stock rooted 4.3 follow the steps in the post
http://rootzwiki.com/topic/36706-ro...stock-android-43-jwr66v-no-bugs/#entry1031982
Sent from my Nexus 7 using xda app-developers app
Jewveeski said:
This is probably a silly question , but is your bootloader locked I have the gnex toro and it can get testy at times also try flashing this ROM its what I'm currently on and it works great no issues its stock rooted 4.3 follow the steps in the post
http://rootzwiki.com/topic/36706-ro...stock-android-43-jwr66v-no-bugs/#entry1031982
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I believe my boot loader is unlocked. When. I reboot I see he unlocked lock. But I did flash the new boot loader so maybe I would have to re unlock it? I will try the ROM you posted
Seems like a lot of the time people who are having this stuck at Google screen issue have flashed the new boot loader. Or am I just imagining things?
toro, toro!
itslels said:
Seems like a lot of the time people who are having this stuck at Google screen issue have flashed the new boot loader. Or am I just imagining things?
toro, toro!
Click to expand...
Click to collapse
I had the issue when I tried to go directly from 4.2.2 to a 4.3 custom. The only thing that cleared it up was flashing stock 4.3 from google. After that, no more problems.
Hmm wonder what could be causing it. I did have this issue going from 4.2.2 to 4.3. Every 4.3 ROM I have flashed has booted.
toro, toro!
I solved my problem after reflashing the new boot loader and a new ROM reboot. Then power off. Battery pull then I wiped cache. I'm not sure exactly what the issue was but now I can load up any 4.3 ROM without a problem )
antwong45157 said:
I solved my problem after reflashing the new boot loader and a new ROM reboot. Then power off. Battery pull then I wiped cache. I'm not sure exactly what the issue was but now I can load up any 4.3 ROM without a problem )
Click to expand...
Click to collapse
i have the same fuking problem , what did you do ?
antwong45157 said:
I solved my problem after reflashing the new boot loader and a new ROM reboot. Then power off. Battery pull then I wiped cache. I'm not sure exactly what the issue was but now I can load up any 4.3 ROM without a problem )
Click to expand...
Click to collapse
Gz dude enjoy 4.3
antwong45157 said:
I solved my problem after reflashing the new boot loader and a new ROM reboot. Then power off. Battery pull then I wiped cache. I'm not sure exactly what the issue was but now I can load up any 4.3 ROM without a problem )
Click to expand...
Click to collapse
Thanks, I followed this and finally managed to get to 4.3
http://forum.xda-developers.com/showthread.php?t=2389721
Oh no... I installed PA 3.94 yesterday and everything seemed great. I didn't have any issues booting the first time (although it took a while), but now I'm afraid to reboot my phone in case it gets stuck at the boot screen like you guys are describing.
EDIT: I did a reboot when I got home and it booted up fine, although I felt like it took longer than on previous versions.
oynoy said:
Oh no... I installed PA 3.94 yesterday and everything seemed great. I didn't have any issues booting the first time (although it took a while), but now I'm afraid to reboot my phone in case it gets stuck at the boot screen like you guys are describing.
Click to expand...
Click to collapse
Gotta be able to reboot your phone brother lol. Give it a shot. If it locks up there is always a way to fix the issue... Good luck. Best wishes
FIX for issue getting stuck on google screen after 4.3 reboot
I don't know if anyone has posted this elsewhere. I had the same problem yesterday - after a lot of playing around this is how I fixed it:
***Note1: you need adb and fastboot.
***Note2: make external backup of things (i.e. photos) you want to keep using adb.
Procedure:
1. Download 4.2.2 image from google (can't post link because of spam prevention rules - you can search for "google developers nexus images")
2. extract files to location of choice
3. Download latest custom recovery image of your choice. I prefer TWRP (latest 2.6)
3. reboot to recovery, do a full factory reset (wipe everything, you will lose all your storage).
4. Reboot to bootloader (from phone off, power plus volume rocker).
5. flash stock image via fastboot (change names and paths acordingly):
Code:
fastboot devices (make sure fastboot can see your device)
adb reboot bootloader
fastboot flash bootloader bootloader-toro-<current_ver>.img
fastboot reboot-bootloader
fastboot flash radio /path/to/radio-toro-<current_ver>.img
fastboot reboot-bootloader
fastboot flash radio-cdma /path/to/radio-cdma-toro-<current_ver>.img
fastboot reboot-bootloader
fastboot -w update /path/to/image-mysid-<version>.zip
5. After this last step, the phone should reboot.
6. Go through the phone setup process.
7. power off, and boot to bootloader
8. flash custom recovery:
Code:
fastboot flash recovery /path/to/custom-recovery.img
9 reboot to recovery. TWRP will ask you if you want to root when you reboot to system.
10. Phone rooted and like new!
I think that is all - you can flash your ROM of choice after this!

[CLOSED] Delete Thread.

Due to the disrespect of certain members here I will no longer share the tutorials.
how long does it take to move past the N/A screen. also where in this do you flash the stock boot.img if you get error 1s? please be more specific.
I should've seen this first
So... I found this thread AFTER the fact. Phone's a day old, rooted, and softbricked. I have TWRP and fastboot but kernel's gone.
You have everything there except the what if...
How'd you un-softbricked your device?
quotrice said:
how long does it take to move past the N/A screen. also where in this do you flash the stock boot.img if you get error 1s? please be more specific.
Click to expand...
Click to collapse
Hi, sorry for the late reply. Been busy tinkering with the phone.
It can take up to 30 seconds (granted, I counted out loud on reboot just now) to move past the N/A screen and go to the chick saying "hello Moto" and then the Metro PCS flash screen.
If you get the error1s the original boot.img may have either been corrupted, deleted, or the phone is being a **** and has somehow altered it where its modified, and therefore cannot start up right. With me, that happened after flashing different TWRPs and then repetitively flashing the files for root. That is why I said this:
5. Installing any of the .zip files may mess with the boot.img. I personally think unlocking the bootloader did that because I followed directions on here to a T and had problems eith Error 1 off the bat. So, if you start seeing Error 1 messages when you attempt to flash the necessary files for root in TWRP, you will have to do this step below I did.
5. Go into the Stock Rom file and extract the boot.img file. Put it in the Minimal ADB file folder (the same as you did for the recovery.img file).
-In Minimal ADB type "fastboot erase boot "
-In Minimal ADB type "fastboot flash boot boot.img" That should restore your original boot image to stock and correct any error 1 problems. And the best part is you don't have to erase and re-flash all the original stock rom files to get it back in order, potentially messing up the bootloader unlock!
Click to expand...
Click to collapse
You do not have to flash the rom unless you want to, and trust it is a pain as you have to extract all the contents of the ROM and flash them via TWRP one by one. I've updated in my original post on how to go about that. So, if the boot.img is your prob, all you have to do is extract the boot.img file from the rom and follow the instructions above. However, if you've deleted or altered more than the boot.img, you will have to flash the rom, but at this step you shouldn't of. I too had the error1 thing, and after tinkering with it for 9 hours, just flashing that boot.img on a humbug solved the problem alone. Just open it in WinRar/WinZip and pull it out, and follow the instructions above.
HmonGrL123 said:
So... I found this thread AFTER the fact. Phone's a day old, rooted, and softbricked. I have TWRP and fastboot but kernel's gone.
You have everything there except the what if...
How'd you un-softbricked your device?
Click to expand...
Click to collapse
My softbrick was the corruption of the boot.img. I was unable to get the phone to load past the N/A after that. Flashing the boot.img from the stock solved it.
If your kernel is truly gone, which please mention what guide you used to try and get root, you will have to flash stock via TWRP. And let me just say, it isn't as easy as flashing it as a ROM. You will have to extract the entire Stock Rom files to Minimal ADB Fastboot folder and flash the files one by one (refer to my updates in my original post on how to restore the stock rom).
---------- Post added at 07:06 PM ---------- Previous post was at 07:03 PM ----------
Articul8Madness said:
My softbrick was the corruption of the boot.img. I was unable to get the phone to load past the N/A after that. Flashing the boot.img from the stock solved it.
If your kernel is truly gone, which please mention what guide you used to try and get root, you will have to flash stock via TWRP. And let me just say, it isn't as easy as flashing it as a ROM. You will have to extract the entire Stock Rom files to Minimal ADB Fastboot folder and flash the files one by one (refer to my updates in my original post on how to restore the stock rom).
Click to expand...
Click to collapse
I finally got it going. I had to flash system.sparsechunk. it failed a few times afterwards too but i figured it was su that was causing it. I finally got it back to stock. Flashed magisk, and now I'm running resurrection. Thank you
Should I post exactly what i did in case someone stumbles upon my same problem?
HmonGrL123 said:
---------- Post added at 07:06 PM ---------- Previous post was at 07:03 PM ----------
I finally got it going. I had to flash system.sparsechunk. it failed a few times afterwards too but i figured it was su that was causing it. I finally got it back to stock. Flashed magisk, and now I'm running resurrection. Thank you
Should I post exactly what i did in case someone stumbles upon my same problem?
Click to expand...
Click to collapse
Couldn't hurt
HmonGrL123 said:
---------- Post added at 07:06 PM ---------- Previous post was at 07:03 PM ----------
I finally got it going. I had to flash system.sparsechunk. it failed a few times afterwards too but i figured it was su that was causing it. I finally got it back to stock. Flashed magisk, and now I'm running resurrection. Thank you
Should I post exactly what i did in case someone stumbles upon my same problem?
Click to expand...
Click to collapse
PLEASE DO!!!! As you see we all are having different problems getting the E4 on the way to root. I encourage you to make a footnote of it in this thread, and I'll direct people to it on the original post. If we can't get this down, flashing a rom is going to be a *****. :good:
Articul8Madness said:
PLEASE DO!!!! As you see we all are having different problems getting the E4 on the way to root. I encourage you to make a footnote of it in this thread, and I'll direct people to it on the original post. If we can't get this down, flashing a rom is going to be a *****. :good:
Click to expand...
Click to collapse
So don't do this yet?
mookey1986 said:
So don't do this yet?
Click to expand...
Click to collapse
@HmonGrL123 had a specific issue when flashing, as a different guide was followed first. This guide is to simplify the process.
I just wanted to add:
At step
13. Hit Install and install Magisk.zip. Afterwards, go back to main menu.
Click to expand...
Click to collapse
I ran into the error 1 problem.
After that, I powered down the phone. Then I went into fastboot and flashed the boot.img
Then I used fastboot to get back into TWRP.
Then I went back to step 13.
And Rebooted.
And I finally got root. All working.
wktra said:
I just wanted to add:
At step
I ran into the error 1 problem.
After that, I powered down the phone. Then I went into fastboot and flashed the boot.img
Then I used fastboot to get back into TWRP.
Then I went back to step 13.
And Rebooted.
And I finally got root. All working.
Click to expand...
Click to collapse
Glad you got it working. Maybe no matter what step is taken is going to initially corrupt the boot.img, so reflashing that is probably going to be essential. I'll test it out on the significant other's phone and see if that is the case.
At the step after the wipe, no matter what I do and trying 2 different versions of twrp, I cannot get the data partition to mount. I can keep clicking it over and over but the box will not check.
Been searching and googling and I cannot figure it out.
nm after sever tries it mounted
Just wanted to thank the op for this awesome guide! Rooted, did a full back up and a nandroid back up, now I'm running resurrection remix to great effect.
Sent from my XT1765 using Tapatalk
Just so you know, the reason why you (and other people in the thread) keep getting error1 when installing Magisk is because of Step 12:
"12. Hit Install and install Superuser.zip. Afterwards, go back to main menu."
Installing the superuser.zip modifies the boot.img .... then the very next step, step 13, is when Magisk will complain about the boot.img being modified. You don't need the superuser.zip at all it's redundant, flashing magisk roots the phone as well. Skip step 12, I'm fully rooted without it and you will literally never get Magisk to say the boot.img is unmodified as long as you keep modifiying the boot.img right before it.
Rooted and bootloader unlock....roming now....wish me luck
So I have officially unlocked my motoE4 on metropcs and have installed superuser. Trying to custom rom and kill the stupid metro pcs bootloader. I deoxed it and removed bloat....but can we tweak? we'll c soon working on it all nite. ill keep you posted
InFamousD147 said:
So I have officially unlocked my motoE4 on metropcs and have installed superuser. Trying to custom rom and kill the stupid metro pcs bootloader. I deoxed it and removed bloat....but can we tweak? we'll c soon working on it all nite. ill keep you posted
Click to expand...
Click to collapse
Magisk works better for root (plus you get magisk modules) and can pass safetynet.
So how long does it take for it to flash each item in twrp? I flashed the first thing (no-verity), and it's just hanging out after it shows "Done Installing!" "Updating partition details...". How long is this suppose to take?
nekomancey said:
Just wanted to thank the op for this awesome guide! Rooted, did a full back up and a nandroid back up, now I'm running resurrection remix to great effect.
Sent from my XT1765 using Tapatalk
Click to expand...
Click to collapse
You're welcome! I went through a time getting this thing to root, so I just wrote what worked on my variant. How's the resurrection remix. Looking for a good rom.
Steel Froggy said:
Just so you know, the reason why you (and other people in the thread) keep getting error1 when installing Magisk is because of Step 12:
"12. Hit Install and install Superuser.zip. Afterwards, go back to main menu."
Installing the superuser.zip modifies the boot.img .... then the very next step, step 13, is when Magisk will complain about the boot.img being modified. You don't need the superuser.zip at all it's redundant, flashing magisk roots the phone as well. Skip step 12, I'm fully rooted without it and you will literally never get Magisk to say the boot.img is unmodified as long as you keep modifiying the boot.img right before it.
Click to expand...
Click to collapse
I am only going by what worked for me with the metropcs variant. I had tried other tutorials, but there was not a definitive one that dealt with the problems of the MetroPCS trying to get root. So I can't say it's redundant when it wasn't just as simple as flashing magisk on this version of the phone for me. And granted, I went by pieces of people's tutorials, trial, and error.

Categories

Resources