Related
Hey all,
I’ve heard that the Rezound is impossible to brick, but all I can guess is that I managed to do the impossible.
I bought a used Rezound a month or so ago. The previous owner had already rooted it and upgraded it to ICS – I honestly wasn’t happy he did this and didn’t mention it in his listing; I just wanted a stock phone and didn’t want to mess with rooting. I didn’t know exactly what he had done to it, so my idea was to reflash it myself, so I knew exactly what was on the phone. Battery life and overheating had been a real problem with the phone, so I was suspecting he might have done something to cause it, so I wanted to rule that out before concluding it was a hardware issue.
ANYWAY – I used cwm, backed everything up, wiped the phone’s memory, then booted back into recovery mode to flash the new ROM. I was able to pick the new ROM and get the process started. It worked its way through the process, rebooted, then sat on the intro screen for-ever. No matter how long I let it sit, it would not complete the install. At that time, I was able to boot back into recovery mode, at which point I cleaned out all the data caches, wiped it as clean as I could, and then tried to repeat the install. Eventually, I used every option in recovery mode and nothing made a difference – I never managed to get the phone working again.
In my last effort, I left the phone on overnight, figuring I’d give it all the time I could to sort itself out, settle into the new ROM, etc. NOW, the battery is dead and the phone won’t charge it. If I remove the battery, put it back in, and plug it in, the charge light goes on for about 5 seconds and then turns back off. At this point, the phone is completely dead.
Do I have any options at this point? Or am I just pretty much SOL?
And no, I don’t know WTF I’m doing, clearly the main issue is probably typing on the keyboard right now. Any help is appreciated.
phermes1 said:
Hey all,
I’ve heard that the Rezound is impossible to brick, but all I can guess is that I managed to do the impossible.
I bought a used Rezound a month or so ago. The previous owner had already rooted it and upgraded it to ICS – I honestly wasn’t happy he did this and didn’t mention it in his listing; I just wanted a stock phone and didn’t want to mess with rooting. I didn’t know exactly what he had done to it, so my idea was to reflash it myself, so I knew exactly what was on the phone. Battery life and overheating had been a real problem with the phone, so I was suspecting he might have done something to cause it, so I wanted to rule that out before concluding it was a hardware issue.
ANYWAY – I used cwm, backed everything up, wiped the phone’s memory, then booted back into recovery mode to flash the new ROM. I was able to pick the new ROM and get the process started. It worked its way through the process, rebooted, then sat on the intro screen for-ever. No matter how long I let it sit, it would not complete the install. At that time, I was able to boot back into recovery mode, at which point I cleaned out all the data caches, wiped it as clean as I could, and then tried to repeat the install. Eventually, I used every option in recovery mode and nothing made a difference – I never managed to get the phone working again.
In my last effort, I left the phone on overnight, figuring I’d give it all the time I could to sort itself out, settle into the new ROM, etc. NOW, the battery is dead and the phone won’t charge it. If I remove the battery, put it back in, and plug it in, the charge light goes on for about 5 seconds and then turns back off. At this point, the phone is completely dead.
Do I have any options at this point? Or am I just pretty much SOL?
And no, I don’t know WTF I’m doing, clearly the main issue is probably typing on the keyboard right now. Any help is appreciated.
Click to expand...
Click to collapse
Well, not sure about the installation issues...but the reason the phone died is because you have CM recovery. Known issue .. probably a hundred threads just not recently because people have either switched or don't let their phone run down. Phone can't charge from CM recovery and you need to switch back to Amon Ra recovery. http://forum.xda-developers.com/showthread.php?t=1434532
Basically, pull battery and then replace and hold volume down and power at the same time to boot into bootloader. Plug phone into computer . Put Amon recovery img into the same folder containing fastboot. Then make sure phone is in fastbootUSB . http://forum.xda-developers.com/showthread.php?t=1339679&highlight=amon+ra
Latest is 3.15 .. so once it is placed in the right folder type fastboot flash recovery recovery-ra-vigor-3.15-gnm.img ... this will flash amon ra recovery.. then you can charge. Once charged then you can attempt to recover your rom.
Sounds like you need an external charger to get the battery a little juice. I never thought that it was possible for a battery to not be able to charge because it was super dead unit I saw it happen on a Thunderbolt. You could take the battery to Verizon and have them give it a quick charge, just to get you back on your feet or got to an electronics store and buy a charger (can always take it back). Get it to boot again then work it from there maybe flash the Stock or Leaked PH98IMG just to get back to working so you can breath again..
Getting yourself out of a jam is part of the learning curve in flashing phones.
Yep, known problem with CWM. Plug it in powered off for a long time. It might not seem like it is charging, but it is, very little.
What ROM did you flash?
Also need to know the firmware version.
Once you get into hboot, tell us what radios you have and what version of hboot. You have three options, 2.11, 2.21, and 2.25. Also tell us if it has S-On or S-Off.
All of this is crucial for us to help you get back to stock.
Great, thank you for the good info! I was about ready to toss the thing in the trash, but it sounds like there may be hope yet!
EmerikL said:
Yep, known problem with CWM. Plug it in powered off for a long time. It might not seem like it is charging, but it is, very little.
What ROM did you flash?
Also need to know the firmware version.
Once you get into hboot, tell us what radios you have and what version of hboot. You have three options, 2.11, 2.21, and 2.25. Also tell us if it has S-On or S-Off.
All of this is crucial for us to help you get back to stock.
Click to expand...
Click to collapse
I'll have to get back to you on all of that - I'm not entirely sure right now, and everything is at home. Pretty sure it was a Venasaur ROM.
I wish the mods would delete any and all links to CWM. These threads keep cropping up.
its possible you need to flash the ICS firmware patch as well and thats why its not booting
Sorry to hassle you guys with what has probably already been answered a few times. I did some searching – yes, I should have done a little more - and the results I found were all folks that had phones that would still power on to some degree. I didn’t find many where the phone was completely dead, and if I did the responses were generally, “You’re screwed, throw it out.” Issues with cwm really didn’t cross my mind, so I didn’t think to search on that.
Anyway, I appreciate the help. I’ll sit down tonight and see if I can’t figure this thing out.
It is likely that he is S-ON and if he had a sense 4 rom installed, the new rom won't boot.
To the OP, can you please tell us the hboot version # (2.xx) it is either 2.10, 2.11,2.21, or 2.25. Also tell us if it says S-ON or S-OFF and unlocked, locked, or relocked, or juponutbear in purple at the top.
Easiest way to brick it is to take out battery while flashing a hboot haha.
No worries about the question, we're glad to help (since you didn't post this in the Development section lol)
Anyway, as long as you are S-ON, it shouldn't be too bad of a process, just lengthy. First, you'll need the Android SDK so you can get Fastboot, etc, as well as all the HTC device drivers installed, and you'll need to flash Amon RA recovery over.
Amon RA can be found here:
http://forum.xda-developers.com/showpost.php?p=23781936&postcount=428
**Make sure the Recovery file is in .img format, not .zip or anything, and place in the same folder as Fastboot (which is located in the Android SDK folder).**
You'll need to pull the battery, plug the USB cable into the computer, plug into the phone, replace battery, and hold down 'Power' + 'Volume Down' until the screen flashes the HTC screen. (Not sure if that's the only order, but it works). This will take you into Fastboot.
Next, you'll need to open a command prompt and 'cd' to your folder with Fastboot in it. Type:
Code:
fastboot flash recovery recovery-ra-vigor-3.15-gnm.img
into the command prompt and hit enter. It should show on the command prompt a couple lines of time it took, etc. and when done you will have Amon RA recovery.
Now you will at least be able to charge your phone!! From the phone, you can select 'Bootloader' then 'Recovery' and you will boot into recovery, which will allow you to charge your battery. You can check the charge status of the battery while in recovery in one of the menus, can't remember which one. (Fun tip: you can use 'Home'/'Menu' to scroll up/down, 'Back' to go back and 'Search' to select, since the hardware buttons are so difficult to press)
Once you get the phone charged, you have a couple of options. Since you stated you wanted to go to stock, I'll explain the steps to get back to the state the phone shipped with.
Once you get a good charge, you will also need to re-lock the bootloader to go back to stock, which is also done in fastboot by typing:
Code:
fastboot oem lock
(Get to fastboot by Battery Pull>Battery Put Back>Power + Volume Down, all while connected to a computer, just like when doing the Recovery flash)
BACK TO STOCK::
You can do this one of two ways, either run the revert using a .zip, or as a .exe connected to your computer. Personally, (and I know I'll probably lose credibility here lol) I prefer the .zip method, although many swear by the 'True RUU' .exe method.
**Here's a little aside to get you so you can get all of these files onto your phone. There's an option in Amon RA that mounts as removable storage to your computer so you can transfer files. Select 'USB-MS toggle' and then select 'USB-MS Toggle SDCard'. Then you can transfer all the files you need before continuing.
First, download the stock "ruu" zip from here:
http://goo.im/stock/vigor/ruu/RUU_V..._1.12_9k_1.83_V_APT_release_221502_signed.zip
and you will need to rename it to PH98IMG.zip and it will need to be placed on the root of your SDCard, not in any folder. Then download the MainVer.zip from here:
http://forum.xda-developers.com/showpost.php?p=23169557&postcount=4\
which can be placed anywhere on the SDCard, but I would place it in the same place as the PH98IMG file for ease.
Once you have the PH98IMG file on the root of the SDCard, and have the MainVerLow zip there also, continue on.
To flash, go to the 'Flash zip' menu in recovery, and locate the setMainVerLow.zip. All this does is set the Main Version low, so hboot (or whatever) doesn't kick it back saying you can't downgrade. This flash will only take a second, and when complete, go back to the main Recovery menu.
It probably doesn't matter, but I would wipe data/factory reset again just to be safe. Do this by selecting 'Wipe' then 'Wipe ALL data/factory reset'. Once done, go back to the main Recovery screen.
Now you will want to reboot into bootloader, which I believe is under either 'Other' or 'Developer Options'
The phone will reboot, and book back into a screen similar to what you saw in fastboot. Some purple text will scroll saying stuff about looking for some file, and will find the one you just put on there and ask if you want to update now. Click the power button to confirm the update. It will show a progress bar on the side, as well as list the parts it has updated for you. It will get around halfway done or so and reboot itself, but DON'T TOUCH ANYTHING OR REMOVE THE BATTERY!!! lol it will reboot and finish the second half of the install. Once it's done, I think you need to hit 'Power' one more time to reboot, but once it does you will be rebooted and load up the completely stock ROM that originally shipped with the Rezound. Of course, from here you can go to the system update menu and update to the latest released OTA.
EDIT:: Just wanted to add, none of what I have written was developed/discovered/first-posted by me, it is the work of other, MUCH more intelligent people other than myself. So don't thank me for anything other than putting them all here lol
con247 said:
It is likely that he is S-ON and if he had a sense 4 rom installed, the new rom won't boot.
To the OP, can you please tell us the hboot version # (2.xx) it is either 2.10, 2.11,2.21, or 2.25. Also tell us if it says S-ON or S-OFF and unlocked, locked, or relocked, or juponutbear in purple at the top.
Click to expand...
Click to collapse
Will try to do that tonight.
I need to get it to power up first. I've had it plugged in at my desk all day and no luck so far. Let me get that taken care of and I'll go from there.
See if you can borrow a friends battery. A thunderbolt or my touch 4g slide battery will work too. You can also manually charge your battery by wiring a USB cable directly to it. Then you can get rid of the broken recovery and charge the battery fully.
good luck.. if you figure all this out you might like being rooted. i had several issues coming from an htc incredible to rezound the cwm was one.
Definitely get Amon Ra.
Sent from my ADR6425LVW
con247 said:
You can also manually charge your battery by wiring a USB cable directly to it. Then you can get rid of the broken recovery and charge the battery fully.
Click to expand...
Click to collapse
OK, that looks interesting. How do I do that?
EDIT - NEVER MIND - just found it.
phermes1 said:
OK, that looks interesting. How do I do that?
EDIT - NEVER MIND - just found it.
Click to expand...
Click to collapse
might be worth your while:
http://www.amazon.com/HTC-Thunderbo...ords=htc+thunderbolt+external+battery+charger
It doesn't charge very fast, but nice to have around.
Hopefully im not too late, but click my name and look at the threads that i have started. I used a ghetto IMO method to charge a dead droid x battery. You njeed a useless usb cable and a little time. Basically you strip the red and black wires and respectively touch them to the + and - leads on your battery. This will charge it relatively fast, you only need to hold it on the battery for a minute or so, just long enough.
But use this as a last plan method, i dont know how safe this is because the voltages may go in wrong or damage the battery, but to this day my droid x still works and i got it on the release week so its relatively old.
If you can, you should get a legit charger instead but if you want it done fast, give this a try or find another way. hope i helped but just make sure that if the battery heats up if you try this, you stop immediately. That could mean that the battery is about to explode or its breaking.
hope i helped, but if you want more help there is bound to be youtube videos on how to do this.
If you try this and something goes wrong its not my problem, but i have done this before and it should work.
Here is the link to the forum i made:
http://forum.xda-developers.com/showthread.php?t=1656547
Yakuzagang5 said:
No worries about the question, we're glad to help (since you didn't post this in the Development section lol)
Anyway, as long as you are S-ON, it shouldn't be too bad of a process, just lengthy. First, you'll need the Android SDK so you can get Fastboot, etc, as well as all the HTC device drivers installed, and you'll need to flash Amon RA recovery over.
Amon RA can be found here:
http://forum.xda-developers.com/showpost.php?p=23781936&postcount=428
**Make sure the Recovery file is in .img format, not .zip or anything, and place in the same folder as Fastboot (which is located in the Android SDK folder).**
You'll need to pull the battery, plug the USB cable into the computer, plug into the phone, replace battery, and hold down 'Power' + 'Volume Down' until the screen flashes the HTC screen. (Not sure if that's the only order, but it works). This will take you into Fastboot.
Next, you'll need to open a command prompt and 'cd' to your folder with Fastboot in it. Type:
Code:
fastboot flash recovery recovery-ra-vigor-3.15-gnm.img
into the command prompt and hit enter. It should show on the command prompt a couple lines of time it took, etc. and when done you will have Amon RA recovery.
Click to expand...
Click to collapse
Update on my efforts. The steps above are where I'm currently at - so I haven't gotten far.
I got the $5 charger as suggested, so my phone will power on and I can at least get to the bootloader screen.
For whatever reason, it will NOT power on if I follow the steps above. It won't power up when I have it plugged into the PC. I can only power it on with it unplugged. So, when I run through the command prompt to install Amon Ra, it seems to be unable to connect to the phone. It displays 'Waiting for device' and nothing ever happens. At this point, it looks like I have everything I need on the PC side, but the phone is too boogered up to communicate with it.
I'm trying the options to clear out the memory right now. The problem there is that it goes to the screen with the top hat and orange circular arrow, and just sits there forever. It never acknowledges that it's done clearing memory.
While flashing my phone, I apparently softbricked it and I haven't been able to enter download mode to flash back to stock.
Here, I list the chronological actions I took before it softbricked and all the ways I've found across this and many other forums to get into that mode:
1) On my 2.1 Samsung Galaxy S Vibrant, I downloaded z4 through my dropbox account and universally rooted the phone.
2) Downloaded ROM manager and installed CWM Recovery. Got ICS Euphoria through my dropbox account.
3) Booted into recovery. successfully created backup. wiped data/cache.
4) Began to flash new ROM. It loads up, I see the Team Passion ASCII logo, I believe, for about two seconds and then it reboots into the screen with Vibrant/Samsung in white text over a black background.
Methods I've tried and that have proven to fail me:
1) Battery out. SD out. SIM out. Hold BOTH volume buttons. Reinsert battery. Boots same screen. (no other response.)
2) Battery, SD and SIM out. Hold both volume buttons, home button, power button. Reinsert battery. Same screen. Release after black screen. Reboots same screen. (no other response.)
3) Battery, SD, and SIM out. Hold vol down or vol up + power. Reinsert battery. Boots same screen. (no other response.)
4) Battery, SD and SIM out. Hold both volume buttons. Plug in USB from PC. Reinsert battery. Boots same screen. (no other response.)
5) ODIN method. I've downloaded the PIT, PDA(tar file) files. Loaded up Odin3 and put them in their respective places in the UI.
Battery out. Hold both volume buttons. Plug in USB. Battery in. Boots same screen. (no other response.)
Again, I've scoured for answers across this and many others forums including youtube videos for hours and I'm at my wits end with no other options and nowhere left to turn.
I am usually a full on DIY guy, so I have never had to post anything before, anywhere and I'm usually pretty good at finding information if it's out there.
PLEASE.
Can somebody help me?
EDIT: after awhile of messing around, I managed to get it into the dashed circle loading symbol screen and eventually the download mode but after two times of successful download mode, turning it off and trying again, now I only get that dashed circle loading screen. My hands are in the air. I give up. I'm just going to order another with the $150 I don't have.
corpsedog said:
While flashing my phone, I apparently softbricked it and I haven't been able to enter download mode to flash back to stock.
Here, I list the chronological actions I took before it softbricked and all the ways I've found across this and many other forums to get into that mode:
1) On my 2.1 Samsung Galaxy S Vibrant, I downloaded z4 through my dropbox account and universally rooted the phone.
2) Downloaded ROM manager and installed CWM Recovery. Got ICS Euphoria through my dropbox account.
3) Booted into recovery. successfully created backup. wiped data/cache.
4) Began to flash new ROM. It loads up, I see the Team Passion ASCII logo, I believe, for about two seconds and then it reboots into the screen with Vibrant/Samsung in white text over a black background.
Methods I've tried and that have proven to fail me:
1) Battery out. SD out. SIM out. Hold BOTH volume buttons. Reinsert battery. Boots same screen. (no other response.)
2) Battery, SD and SIM out. Hold both volume buttons, home button, power button. Reinsert battery. Same screen. Release after black screen. Reboots same screen. (no other response.)
3) Battery, SD, and SIM out. Hold vol down or vol up + power. Reinsert battery. Boots same screen. (no other response.)
4) Battery, SD and SIM out. Hold both volume buttons. Plug in USB from PC. Reinsert battery. Boots same screen. (no other response.)
5) ODIN method. I've downloaded the PIT, PDA(tar file) files. Loaded up Odin3 and put them in their respective places in the UI.
Battery out. Hold both volume buttons. Plug in USB. Battery in. Boots same screen. (no other response.)
Again, I've scoured for answers across this and many others forums including youtube videos for hours and I'm at my wits end with no other options and nowhere left to turn.
I am usually a full on DIY guy, so I have never had to post anything before, anywhere and I'm usually pretty good at finding information if it's out there.
PLEASE.
Can somebody help me?
EDIT: after awhile of messing around, I managed to get it into the dashed circle loading symbol screen and eventually the download mode but after two times of successful download mode, turning it off and trying again, now I only get that dashed circle loading screen. My hands are in the air. I give up. I'm just going to order another with the $150 I don't have.
Click to expand...
Click to collapse
Hmmm...well, let's see. There is a lot to respond to, so I'll do my best to be as clear as possible...But, first and foremost, you need calm down and relax because from what you are describing, you don't seem to be in too bad of shape in regards to getting your phone up and running again.
The first thing I'd like to note is that it seems as though your first problem was trying to flash an ICS rom straight from 2.1. You really should have referred to Wood's awesome "How to update to ICS thread" which can be found here: http://forum.xda-developers.com/showthread.php?t=1464423
You never want to jump right into tweaking with your very expensive toys without reading EVERYTHING humanly possible about the subject, because nobody wants a $200 paperweight. With that being said, let's now try and figure out how exactly to fix this problem. I'm not sure what you mean by "dashed circle loading symbol" but you did mention that you were able to get into download mode, which is good.
It looked like such:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
right?
What key combination did you use to get into DL mode? (There are different ways). My point being, is that if you can get into DL mode, you should be okay...try and get there again and from there use the AIO toolbox to assist in your recovery: http://forum.xda-developers.com/showthread.php?t=954509
So, to review...first get into DL mode again, next plug your device into your computer while in DL mode, make sure AIO toolbox is installed, and that you have the proper drivers installed, and while still in DL mode (as pictured above) and connected to your computer via usb cable, use AIO to flash back to stock. From there, follow Wood's ICS upgrading guide CAREFULLY to get yourself up and running an ICED out device.
Good luck.
Xenoism said:
Hmmm...well, let's see. There is a lot to respond to, so I'll do my best to be as clear as possible...But, first and foremost, you need calm down and relax because from what you are describing, you don't seem to be in too bad of shape in regards to getting your phone up and running again.
The first thing I'd like to note is that it seems as though your first problem was trying to flash an ICS rom straight from 2.1. You really should have referred to Wood's awesome "How to update to ICS thread" which can be found here: http://forum.xda-developers.com/showthread.php?t=1464423
You never want to jump right into tweaking with your very expensive toys without reading EVERYTHING humanly possible about the subject, because nobody wants a $200 paperweight. With that being said, let's now try and figure out how exactly to fix this problem. I'm not sure what you mean by "dashed circle loading symbol" but you did mention that you were able to get into download mode, which is good.
It looked like such:
right?
What key combination did you use to get into DL mode? (There are different ways). My point being, is that if you can get into DL mode, you should be okay...try and get there again and from there use the AIO toolbox to assist in your recovery: http://forum.xda-developers.com/showthread.php?t=954509
So, to review...first get into DL mode again, next plug your device into your computer while in DL mode, make sure AIO toolbox is installed, and that you have the proper drivers installed, and while still in DL mode (as pictured above) and connected to your computer via usb cable, use AIO to flash back to stock. From there, follow Wood's ICS upgrading guide CAREFULLY to get yourself up and running an ICED out device.
Good luck.
Click to expand...
Click to collapse
Hey, thanks for the reply.
The thing is now, I can't seem to get it back into DL mode no matter what I do.
No manner of button combinations work. Taking out the battery, holding vol +/-, inserting battery and plugging USB up used to do it but now I get nothing. It seemed to work once or twice while in Odin, but during download mode, I still had no yellow COM5 connection and so I would close it, power off the phone and start over. After that second time, it just didn't show up anymore and now all that happens is what looks like a circle with dashes making up the circumference that would typically highlight in a cylindrical fashion while waiting for, say, a youtube video to load, but this symbol doesn't move. It's just frozen in place and the phone only reboots into that screen with the USB in if I power off/on.
thanks again for the reply. I did order a new phone, but I'd love to fix this one and use the other as a backup if possible.
EDIT: Also, I apologize for my rash behavior and bad attitude. I just lost a lot of sleep over this and I had a lot to do today. Haha. I'm sure you've all been there with these issues. Thanks for putting up with me, though.
Worst case scenario you can send it to www.mobiletechvideos.com . For $40 they will do a JTAG fix and unbrickable mod.
Just to be sure, do you have a stock front facing camera?
Sent from my SGH-T959 using xda premium
samsgun357 said:
Worst case scenario you can send it to mobiletechvideos. For $40 they will do a JTAG fix and unbrickable mod.
Just to be sure, do you have a stock front facing camera?
Sent from my SGH-T959 using xda premium
Click to expand...
Click to collapse
No, I'm pretty sure I only have the T959. No FFC.
corpsedog said:
No, I'm pretty sure I only have the T959. No FFC.
Click to expand...
Click to collapse
Lol OK have just seen a lot of that lately.
Sent from my SGH-T959 using xda premium
Update!
Success!
I managed to get it into DL mode again after buying a new USB cable and preparing to make the jig for it.
Now a new issue has come up.
I tried the one-click unbrick java app and have been getting the (phone-!-pc) icon and was prompted to install the USB drivers but they failed to install.
Any ideas?
Thanks so much for your help thus far.
USB debugging mode?
Okay, so after a few more tries and using different apps to install the drivers since Heimdall seems to think they 'are not properly installed', whatever that means, I've come to the point of using PDANet and once installing the drivers again, I was prompted to enter debug mode but.. how am I supposed to do that when all my phone can do is boot loop and enter download mode?
EDIT: After messing around some more, I found USBDeview which allows me to see all USB devices that are either connected or disconnected.
Samsung USB Composite Device and Samsung Mobile Modem both show up in the device manager and under USBDeview they list as connected.
The only thing Heimdall/OneClickUnbrick says after clicking 'unbrick' is "The USB drivers are not installed properly. Attempting to install." and then upon opening Zadig, selecting Samsung USB Composite Device and the Windows 32bit drivers for my Vista OS, the install fails.
Odin just doesn't recognize it at all. Nothing special.
Why aren't they recognizing my phone?
FINAL EDIT: I don't exactly know how I did it and over the painstaking processes that I've been through, I'm groggy, uncollected and somewhat irritable but I finally managed to flash the stock ROM back onto the phone and I am back in business. Thanks everyone for any and all of your help. It was much appreciated!
Good to hear that you are back from the brink. Believe me we have all been there.
Read my ICS install guide (linked above) and if you need any files, they should all be in the Repo thread in the Dev section. Above all, read, read and when you are ready, read just a bit more. That way you will have some foundation for when you are ready to flash and not be reading at the same time as doing.
As fundemental as this sounds, I always suggest it because it gives you a better sense of troubleshooting. I suggest you download some 2.2 ROMs and kernels and try going from 2.1 to 2.2 by using CWR update.zip method, and then Odin back to JFD (2.1) and try another. Do this a few times and you will inevitably run into some issues like the differences of key combos between Froyo and Gingerbread Bootloaders, differences between Voodoo and non-Voodoo kernels,... This will tremedously help when you do take the jump to ICS/JB and the very real possiblity of doing something wrong.
And FWIW, the way you could have gotten out of the predicament in your OP was to re-flash the ROM.zip over itself. 90% of the time that cures the initial flash bootloop on ICS ROMs.
Good luck and if you need anything search first (this device is almost 3 years old, so most problems have already happened/solved) and then ask.
That's awesome corpse! If you need anything don't hesitate to pm me or ask the community if you can't locate the answer.
Sent from my SGH-T959 using xda premium
Ok, girlfriend bought a used TF201, it had some version of cynogen mod installed that was too unstable for her to use. Android was 4.1.1, so I began/completed the nvflash backup instructions
After the files were safe and stored triplicate, I flashed TWRP 2.3.3.0, and attempted to install androwookie 1.51. The device had the cache, dalvik cache, and a factory reset performed. The install was completed without a hitch, upon rebooting, the wookie pops up for a few seconds and i eventually get kicked out back into TWRP.
I can not acess ADB mode (I think), when I boot with the Volume Down pressed, it has no options and boots to recovery in ~5 seconds. I have attempted to restore with nvflash files but for whatever the reason I can not get the thing to boot back up. I have also attempted to use the 'how-to unbrick' guide without success
I have attempted to revert to the stock JB files but those fail to boot as well and im forced to flash TWRP again. Clearly im a noob, and I need some help, anything would be appreciated before she does something horrible to me
Ive been messing with this for so many hours im burned out. I eventually was able to reflash the stock ICS roms on to the device, and it booted up a nasty wookie/asus ics hybrid. I attempted to run the OTA update, and it failed... I think this is now a 'hard brick'.
I have the nvflash files, an unblobed JB, unblobed ICS, androwookie, the JB/ICS versions of twrp, and ran through hundreds of pages of information that didn't end up helping. Now when I try to get wheelie to bootstrap it gets stuck at 100%, the tablet doesn't light up, maybe I had a bad flash im not sure...
My guess is that you are trying to install androwook with the ICS bootloader. You have to install the stock jellybean ROM first (from asus's website...unzip it once after you download...extracted file should be another zip...use this extracted zip file to install the os. After that reinstall twrp for jellybean, then install androwook.
laggyprime said:
My guess is that you are trying to install androwook with the ICS bootloader. You have to install the stock jellybean ROM first (from asus's website...unzip it once after you download...extracted file should be another zip...use this extracted zip file to install the os. After that reinstall twrp for jellybean, then install androwook.
Click to expand...
Click to collapse
Sadly when attempting to go into apx mode the device is recognized by my pc, but when bootstrapping? To get into nvflash mode wheelie gets stuck sending the file 100%. I think I flashed something wrong (was typing commands by hand) and mixed up a 5 with a 4... Anyways the screen won't even display anything at all anymore, it's blank. Do I need to contact asus now, or is there a way to get wheelie/nvflash working?
DocCox said:
Sadly when attempting to go into apx mode the device is recognized by my pc, but when bootstrapping? To get into nvflash mode wheelie gets stuck sending the file 100%. I think I flashed something wrong (was typing commands by hand) and mixed up a 5 with a 4... Anyways the screen won't even display anything at all anymore, it's blank. Do I need to contact asus now, or is there a way to get wheelie/nvflash working?
Click to expand...
Click to collapse
I suggest you contact the dev's in the nvflash thread first... being very poilte of course since in your situation you need all the friends you can get. If they can get you back to ics then go to the hairy bean (androwook) thread, the OP should have all the info you need to go up to jellybean. You should be able to go directly from ics to jb by following the instructions of course. If you have questions prior to making the leap, ask in the thread, the folks there are quite helpful.
Gage_Hero said:
I suggest you contact the dev's in the nvflash thread first... being very poilte of course since in your situation you need all the friends you can get. If they can get you back to ics then go to the hairy bean (androwook) thread, the OP should have all the info you need to go up to jellybean. You should be able to go directly from ics to jb by following the instructions of course. If you have questions prior to making the leap, ask in the thread, the folks there are quite helpful.
Click to expand...
Click to collapse
A very good suggestion, I dont have high hopes for this transformer but it would be nice to see it come back to life. I looked over the 60 something pages of posts in the dev thread but can't post there because i lack the minimum post count. I don't see people with the inability (recently) to get their prime to switch over to nvflash mode using a wheelie bootstrap unless they missed something obvious. As mine was working for 12 solid hours of trying to restore its clear I flashed something wrong, but the nvflash,adb,etc installs are fine.
I will attempt to send a PM, and hope for the best. Thank you Gage_Hero
DocCox said:
A very good suggestion, I dont have high hopes for this transformer but it would be nice to see it come back to life. I looked over the 60 something pages of posts in the dev thread but can't post there because i lack the minimum post count. I don't see people with the inability (recently) to get their prime to switch over to nvflash mode using a wheelie bootstrap unless they missed something obvious. As mine was working for 12 solid hours of trying to restore its clear I flashed something wrong, but the nvflash,adb,etc installs are fine.
I will attempt to send a PM, and hope for the best. Thank you Gage_Hero
Click to expand...
Click to collapse
Ok, for a start if you have the files you created doing nvflash backed up you can always save the device.
Can you still get to fastboot by holding down the power button and volume down button for about 10 seconds until the icons appear?
flumpster said:
Ok, for a start if you have the files you created doing nvflash backed up you can always save the device.
Can you still get to fastboot by holding down the power button and volume down button for about 10 seconds until the icons appear?
Click to expand...
Click to collapse
Hearing that is great
Heres the current situation, I mistyped a 5 with a 4 and told the unit to restart.
So
Power Vol+ = computer recognizes APX mode - however wheelie sends the blob and gets stuck at 100%
Power = Blank screen. HDMI also has no output.
Power Vol- = Blank screen, HDMI has no output.
Using the reset button, i receive the same results
I may be the only idiot to ever brick a prime this hard
DocCox said:
Hearing that is great
Heres the current situation, I mistyped a 5 with a 4 and told the unit to restart.
So
Power Vol+ = computer recognizes APX mode - however wheelie sends the blob and gets stuck at 100%
Power = Blank screen. HDMI also has no output.
Power Vol- = Blank screen, HDMI has no output.
Using the reset button, i receive the same results
I may be the only idiot to ever brick a prime this hard
Click to expand...
Click to collapse
Try following the instructions in this post. If wheelie is still failing try another computer.
http://forum.xda-developers.com/showthread.php?t=1927818&highlight=nvflash
flumpster said:
Try following the instructions in this post. If wheelie is still failing try another computer.
http://forum.xda-developers.com/showthread.php?t=1927818&highlight=nvflash
Click to expand...
Click to collapse
Step 4 always results in the same issue. I have also tried older versions of the universal drivers without success.
Wheelie sends the file, reaches 100%, returns to the next line and remains blank. After sending the command, attempting to send it again from another window (or to send additional commands) the device will not communicate until it is restarted.
I have attempted this on all 3 machines I own (2x windows 7 x64, and a windows 7 X86)
In the past the apx commands worked fine but ever since I messed up the flash and told the device to restart it has had this issue . I have also drained the battery down and attempted to get it working again, and finally opened the device and turned off the mb power and flipped it back on without a change in results.
I also downloaded and ran a linux live CD to run the commands and it was unsuccessful. The screen always remains blank and wheelie always sends 100% and stops.
I appreciate the assistance flumpster
DocCox said:
Step 4 always results in the same issue. I have also tried older versions of the universal drivers without success.
Wheelie sends the file, reaches 100%, returns to the next line and remains blank. After sending the command, attempting to send it again from another window (or to send additional commands) the device will not communicate until it is restarted.
I have attempted this on all 3 machines I own (2x windows 7 x64, and a windows 7 X86)
In the past the apx commands worked fine but ever since I messed up the flash and told the device to restart it has had this issue . I have also drained the battery down and attempted to get it working again, and finally opened the device and turned off the mb power and flipped it back on without a change in results.
I also downloaded and ran a linux live CD to run the commands and it was unsuccessful. The screen always remains blank and wheelie always sends 100% and stops.
I appreciate the assistance flumpster
Click to expand...
Click to collapse
Step 4 isn't really doing anything except putting you into nvflash mode ready to run the next commands.
When it says " 2. Extract wheelie, nvFlash and the unblob'd ROM to a directory (avoid spaces in the directory path)" are you also putting all the files you backed up when you did the nvflash process in the first place in the same folder?
flumpster said:
Step 4 isn't really doing anything except putting you into nvflash mode ready to run the next commands.
When it says " 2. Extract wheelie, nvFlash and the unblob'd ROM to a directory (avoid spaces in the directory path)" are you also putting all the files you backed up when you did the nvflash process in the first place in the same folder?
Click to expand...
Click to collapse
Yes, I copied all of the backed up files into the same directory. Its where all the files are, TWRPJB and TWRPICS, three seperate roms, adb files, etc. Step 4 is (if im remembering correctly, im currently not at home) when the device actually enters nvflash mode - which it fails to do, and the cmd window just sits there. The directory all the files are placed into are c:\android just to keep it simple for me
DocCox said:
Yes, I copied all of the backed up files into the same directory. Its where all the files are, TWRPJB and TWRPICS, three seperate roms, adb files, etc. Step 4 is (if im remembering correctly, im currently not at home) when the device actually enters nvflash mode - which it fails to do, and the cmd window just sits there. The directory all the files are placed into are c:\android just to keep it simple for me
Click to expand...
Click to collapse
I'm in bed at the moment but give me a shout later when you're home and I'll run the commands myself again and see exactly what happens.
But basically wheelie should just use the file you backed up from before on step 4 to enter nvflash mode so nothing should go wrong at that point.
flumpster said:
I'm in bed at the moment but give me a shout later when you're home and I'll run the commands myself again and see exactly what happens.
But basically wheelie should just use the file you backed up from before on step 4 to enter nvflash mode so nothing should go wrong at that point.
Click to expand...
Click to collapse
You betcha, thank you sir
ok so ive reinstalled everything, grabbed one of my backup blobs just in case something went wrong with the one ive been using
Heres a screenshot of what the window looks like after an hour of waiting
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
is there a next step other than contacting asus?
DocCox said:
Ok, girlfriend bought a used TF201, it had some version of cynogen mod installed that was too unstable for her to use. Android was 4.1.1, so I began/completed the nvflash backup instructions
After the files were safe and stored triplicate, I flashed TWRP 2.3.3.0, and attempted to install androwookie 1.51. The device had the cache, dalvik cache, and a factory reset performed. The install was completed without a hitch, upon rebooting, the wookie pops up for a few seconds and i eventually get kicked out back into TWRP.
I can not acess ADB mode (I think), when I boot with the Volume Down pressed, it has no options and boots to recovery in ~5 seconds. I have attempted to restore with nvflash files but for whatever the reason I can not get the thing to boot back up. I have also attempted to use the 'how-to unbrick' guide without success
I have attempted to revert to the stock JB files but those fail to boot as well and im forced to flash TWRP again. Clearly im a noob, and I need some help, anything would be appreciated before she does something horrible to me
Click to expand...
Click to collapse
Not for nothing, and please moderate my knowledge, but I can sell you mine ( unlocked, with Twrp installed, running Hairy Bean 1.5.1 tweaked.... no glitches, score 15,000 on AnTutu....PM me, I'll make the sale and guarantee it's valuable!
Inserted 20¢ for the first three minutes
DocCox said:
ok so ive reinstalled everything, grabbed one of my backup blobs just in case something went wrong with the one ive been using
Heres a screenshot of what the window looks like after an hour of waiting
is there a next step other than contacting asus?
Click to expand...
Click to collapse
Guessing you didnt go back to flumpster... he can help you.... I think you are still safe but dont experiment....
Im unbricked but apparently not out of the woods. Updating past 4.0 seems to be impossible for me right now.
The command to force this type of brick back into nvflash mode is
Code:
wheelie -r --blob blob.bin
Notice it requires "-r" to be added. That was it!
Yea, I just wasted so many hours on this I could have purchased a new tablet. If I had hair I would have pulled it out of my head already!
The first boot looked good, the tegra was bottom right but was stuck loading, I installed TWRP for JB and put myself into another brick. Long story short, I have ICS running 4.0.3, but cant update for the life of me. The screen will go blank (original brick style) or gets into a boot loop or has the unrecoverable boot error
Ive tried just using the update from asus (US version, as is tablet) and it always appears to update correctly (blue progress bar) but never ends up booting. I tried getting out of the boot loop using a guide here and it wasn't effective. I also tried flashing one of the unblobed 4.0's and it didn't work either. Every time ive been forced to reflash 4.0.3. This has/is a learning process for me, my tf700 updates fine and I can flash between roms but I cant get this darn tf201 to do anything without bricking. My ultimate goal here is to get a stable version 1.51 Androwook w/ the 1.7 and data2sd enabled. Anybody willing to hold my hand from my current 4.0.3 state to the final completion?
DocCox said:
Im unbricked but apparently not out of the woods. Updating past 4.0 seems to be impossible for me right now.
The command to force this type of brick back into nvflash mode is
Code:
wheelie -r --blob blob.bin
Notice it requires "-r" to be added. That was it!
Yea, I just wasted so many hours on this I could have purchased a new tablet. If I had hair I would have pulled it out of my head already!
The first boot looked good, the tegra was bottom right but was stuck loading, I installed TWRP for JB and put myself into another brick. Long story short, I have ICS running 4.0.3, but cant update for the life of me. The screen will go blank (original brick style) or gets into a boot loop or has the unrecoverable boot error
Ive tried just using the update from asus (US version, as is tablet) and it always appears to update correctly (blue progress bar) but never ends up booting. I tried getting out of the boot loop using a guide here and it wasn't effective. I also tried flashing one of the unblobed 4.0's and it didn't work either. Every time ive been forced to reflash 4.0.3. This has/is a learning process for me, my tf700 updates fine and I can flash between roms but I cant get this darn tf201 to do anything without bricking. My ultimate goal here is to get a stable version 1.51 Androwook w/ the 1.7 and data2sd enabled. Anybody willing to hold my hand from my current 4.0.3 state to the final completion?
Click to expand...
Click to collapse
Get it back to where you have it working and add me on Google talk on computer.
I will pm you my email for it now.
Also you need to know that I'm UK and we seem to be missing each other time wise so you might have to do this earlier in the day for you.
flumpster is the man. I can't say enough for this guy, he spent countless hours helping me through this unique brick (and lost a nights sleep over it!) when so many others had no interest or were straight up hostile when contacted for help via pm's. My girlfriends tablet is running androwook right now, and I get to sleep in the bed agian!
For others, the brick resulted in anything not ICS resulting in fatal bootloops, impossible to recover from. Power and Volume down resulted in no options avaliable, and unless flashed manually nothing would install. The twrp's would crash repeatedly when sideloaded, installing, using external SD cards, or doing anything but sitting on the home screen. Not sure what caused the issues, not sure how to reproduce it, but flumpster still guided me through the process. The only solution was working with nvflash through linux to gain acess to more advanced commands, and with the knowledge I gleaned from this wizzard I was able to complete the process. Many thanks flumpster.
/me off to bed finally!
UPDATE (04/29/2013): If you are having issues with rooting or jelly bean is too unstable, there is another way. I found this a while back, but did not know that JB had a lot of bugs. First off, all credit goes to Apache Thunder. First off you want to download PHA44IMG. Now open the zip (do not extract), and look for android_version.txt. Where it says "mainver" change the number to 2.12.651.5 (JUST THE NUMBER, NOTHING ELSE!) Now Save the file while it is still in the zip. Now copy the zip to your SD card without putting it inside any folders (basically the root of your SD card). Once you do that, go into your boot loader (take battery out, put it back in, hold down Vol Down + Power). Wait for the white screen to come up with the three androids at the bottom, and once it finds the file, then you can hit Vol Up, and it will re-load the stock software. Obviously, this will overwrite ANYTHING you have on the phone itself, so if you need to back up something, then back it up (common sense). I hope this helps.
Well, I have been looking, and looking, and looking. I just could not find a way to root this device. The codename for this phone is called "Kingdom." So I am not sure if this works on the Sprint version, but I can confirm this works directly on Boost Mobile on ICS. I am going to make this guide as easy as possible. I take NO credit for what is in this guide, only for posting it here. I seen guides, but they are either out of order, or just do not make sense. This is my first guide, so I do not know how to make it fancy or what not. Before you criticize the way the guide is set up, make sure the information is correct. This works for me, and it is the right and easy way to root the phone. I used forums before, but this is new to me. I wrote this guide from memory from a phone that I did literally three hours ago.
------
What this guide will do for you is root your device, and install jelly bean software. Before you go any farther, please back up ANYTHING you want. Your SD card will not be affected but you will lose apps (that can be re-downloaded), contacts, SMS messages, etc on the phone. Your contacts can be restored using Gmail. Just be aware that I am not responsible for ANYTHING that happens to your phone. However, I can help you if you need it, though.
------
Here are the people possible for this guide:
LOLINTERNET
2fast4u88
------------
The things you will need:
Boost Mobile HTC EVO Design 4G (please upgrade to ICS, it makes things so much easier)
Internet
Patience
Skills to Read
Ensure that HTC drivers are installed. If you have Win7, they should automatically install.
Basic/Novice computer skills
Common Sense
Here are the files:
boosthtcdesignevo4g-root.zip
cm-unofficial-kingdom.zip
gapps-jb-20120726-signed.zip
----------
First thing is first, you need to unlock your bootloader. This is very easy, and quick. If you are familiar with HTC phones, you are probably familiar with htcdev.com. If not, then you are in the right spot. First off, go and visit www.htcdev.com and register with a valid email address. It is very important you provide a REAL email address, because you will get a file emailed to you. Now, after you register, go to the home page, and click on "Unlock bootloader," and Get Started. which is the second icon. After that, there will be a list on the right hand side. Go all the way to the bottom and select "All Other Supported Models" and click "Begin Unlock Bootloader." There will be two popups, on the first one, click Yes, and on the second one, click check both checkmarks, and click on "Proceed to unlock." Scroll down to the bottom, and click the green button, and do the same on the next page.
Now, that we have that out of the way, we have to get a special token inside of your phone. To get this, we will need to use fastboot. Go ahead and extract the boosthtcdesignevo4g-root.zip to your computer. I recommend using the C:\ folder and in a new folder called "root", as it will make it easier to navigate. In fact, this guide will imply that it has been extracted to C:\root. Once it is extracted, click Start, and type in "cmd" and hit enter. If you are not on Windows Vista/7, then click Start>Run and type in "cmd." This is our command prompt, a black screen. Now navigate to where you extracted the files at, in this case, we will type "cd C:\root" (or whatever you extracted it to. Now take out the battery, and put it back in. you will hold down the Vol Down and Power down button. A white screen should pop up. If not, try again. You are in the right spot if it says "**LOCKED**" in purple. Use the VOl Down to go down to "Fastboot" and hit the Power button (kind of like the Enter button). If it says something like "reading PH4IMG.zip" in green, don't worry. Let it finish, and when you see the options again, use Vol Down and highlight fastboot and hit the Power button. Connect your phone via USB, and it should switch from Fastboot to Fastboot USB. If not, unsure that you USB connection is secured.
In the command prompt, type in the following without quotes "fastboot oem get_identifier_token." You will get a long screen of numbers, that will start with <<<< Identifier Token Start >>>>. This is probably the most hardest part, which is copying the token correctly. You want to right click and hit Mark. Now start at the first "<<<<" and end it at the "<<<<< Identifier Token End >>>>>". It should look exact like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
.
Now, once it is highlighted, right click, and it will be copied. Go back to the browser, and scroll down to the bottom, where it says: "My Device Identifier Token:" and right click on the white edit box, and paste it. and click submit. If you get errors, re-copy it, and try again. Like I said, this is the hardest part, so that means this whole process is pretty easy. Anywho, once you have done that, you should get a confirmation about a file being emailed to you. Remember that email I told that should be real, well this is it. Check your email, it should be from [email protected] and the subject should be "The key to unlocking your HTC Device". Check the email for attachments, as it should be a file that says Unlock_code.bin. Copy that to C:\root. Now go back to the command prompt, and type in "fastboot flash unlocktoken Unlock_code.bin." Now once you do that, your phone should go to a black screen, and it should look like this:
All you have to do is hit the Vol Up button, and hit Power. There you have it, your bootloader is unlocked.
-------------------------------
Now here comes part 2A of the rooting process. We need a custom recovery. Go back to that white screen on your phone, the HBOOT, and select Fastboot again (just like last time). Once you have selected that, go ahead to your command prompt and type fastboot flash recovery recovery.img. Once that finished, you have clockwork mode recovery. I am not going into details what the recovery does, as there are a PLETHORA of information about it. Just know it is one of the special things you need.
Here is part 2B. Next, look in the C:\root folder, and get ready to copy the Superuser-3.0.7-efghi-signed.zip file onto your SD card on your phone. You need to get to the white screen again on your phone, you know taking at the battery, ya-da-da-ya-ya. Anywho, just use Vol Down to go down to RECOVERY, and you will see a black screen with blue text. You will use Vol Up/Vol Down to select items. Go down to mount and storage and hit Power. Then select USB storage. Once you do that, you should see it pop up on your computer, and just copy the zip over. While we are at, copy over cm-unofficial-kingdom.zip & gapps-jb-20120726-signed.zip. Just keep this file at the root of your SD card, it will make things MUCH easier. Now, just choose, "Go Back" and select "Install .zip from SD Card." Make sure you do not select the one with "update.zip" as this is the wrong one. Once, you do that, hit Vol Up, to go to the bottom first, and go up until you get to Superuser-3.0.7-efghi-signed.zip, and hit the Power button. Then you will see a whole bunch of No's, obviously, you will want to click on Yes - Install Superuser-3.0.7-efghi-signed.zip. That should be quick, and simple. Guess what, your phone is rooted!!! Select reboot now, and you can verify it by installing the "Root Checker" app from the play store. You also may need to contact Boost Mobile, to re-activate your phone. Once you download an app that requires root, it will get permission from Superuser, which is basically the "root police" on the phone. If you are aware of the root, select "Grant," if not, select "Deny." Common sense.
------
Now time to install jelly bean. This is simple as well. Just go back to the white screen, like we did a hundred times already throughout this whole process. Select RECOVERY, and this time, we will go to install zip from SD Card, just like last time. Go ahead and select cm-unofficial-kingdom.zip and install it, just like the last time. DO NOT REBOOT YOUR PHONE! Once you are done with that, do the same thing for gapps-jb-20120726-signed.zip. Now go ahead and reboot the device. Now you are not only rooted, but have the Jelly Bean software as well. Follow the on-screen prompts, and you will be able to use your phone
----
Again, I am not responsible, for anything that happens to your phone, and of course you void your warranty. If you have any questions, please do not be afraid to ask me. If you need more help, I am always happy to help.
Out of curiosity, will this allow me to pop in a non-Boost SIM such as one from T-Mobile or AT&T?
I think there is an app on the play store. But from what I remember the global sim function is locked
Sent from my Carbon-ize Evita using xda-developers app
Thanks but
Hello and thanks for your guide. I just would like to say that perhaps you could add a notice in VERY BIG LETTERS to remember to backup your ROM before proceeding before or after you Root your device! I followed your guide to the letter and without thinking (Obviously) did not do a stock recovery and am now screwed. I have been fighting this problem for 2 weeks because no one has a current stock image that has the latest Boost PRL61009 and other (Radio) issues, the list goes on. Also when you do this (and it works great I must say!) your now at a newer HBoot version and can not go back without another nightmare problem (Main Version Older error). So just as a precaution against people like me who go line by line (with blinders on) please insert the precaution to Back UP! Thanks again.:crying:
awesome
Thank you so much for this guide.
I have been wanting to install jelly bean for quite awhile now.
Quick question(s)
1. Is there any way to get the official boost mobile wi-fi hotspot application installed ?
I noticed the official one uses less battery. I don't mind paying for the ability to tether my phone.
2. Is there anything broken with rom such as video recording and sms.
Once again thank you so much for posting this guide.
HELP
Alright so, this morning I attempted to restore my phone to factory defaults and it did not like that. I am rooted so my bootlocker is unlocked. When I attempt to go into recovery, the phone reboots and goes to an image of the phone with a red triangle/exclamation point in it. As of now my phone is unusable so any help woould be greatly appreciated
Followed the guide,with some problems
Probably didn't read the guide well.
Couple of things
1) this is for the us cellular network
2) used titanium backup, it didn't work when I tried to restore everything back to original
There are some good things with the jelly bean rom, but 4g is missing and here are some other things that I am nor happy with so I want to flash back to the original boost mobile stock rom
I have access to another stock boost mobile evo design 4g phone, so if there is anyone that know if it is possible to coy the stock rom and transfer it to my modified handset, I would greatly appreciate it.
Thanks
Well I can update the guide to go back to stock. Thank you for putting the bugs out there.
Also. This is boost mobile not us cellular. If us cellular works, then I will update the guide. However it is intended for boost mobile. I just moved, so when I unpack my PC, I will update it to reflect stock ROMs.
Sent from my Carbon-ize Evita using xda-developers app
t_haggerty said:
Alright so, this morning I attempted to restore my phone to factory defaults and it did not like that. I am rooted so my bootlocker is unlocked. When I attempt to go into recovery, the phone reboots and goes to an image of the phone with a red triangle/exclamation point in it. As of now my phone is unusable so any help woould be greatly appreciated
Click to expand...
Click to collapse
How did you attempt to restore? From the ROM or the boot loader?
Sent from my Carbon-ize Evita using xda-developers app
boogiedownandroid said:
Thank you so much for this guide.
I have been wanting to install jelly bean for quite awhile now.
Quick question(s)
1. Is there any way to get the official boost mobile wi-fi hotspot application installed ?
I noticed the official one uses less battery. I don't mind paying for the ability to tether my phone.
2. Is there anything broken with rom such as video recording and sms.
Once again thank you so much for posting this guide.
Click to expand...
Click to collapse
I heard that MMS has a hard time working well. As far as the hotspot, not sure. You can check then market
Sent from my Carbon-ize Evita using xda-developers app
Carbon238 said:
Hello and thanks for your guide. I just would like to say that perhaps you could add a notice in VERY BIG LETTERS to remember to backup your ROM before proceeding before or after you Root your device! I followed your guide to the letter and without thinking (Obviously) did not do a stock recovery and am now screwed. I have been fighting this problem for 2 weeks because no one has a current stock image that has the latest Boost PRL61009 and other (Radio) issues, the list goes on. Also when you do this (and it works great I must say!) your now at a newer HBoot version and can not go back without another nightmare problem (Main Version Older error). So just as a precaution against people like me who go line by line (with blinders on) please insert the precaution to Back UP! Thanks again.:crying:
Click to expand...
Click to collapse
EDIT: OP has been updated to revert back to stock.
Thanks for the info. I wrote this guide from experience and was able to flash jelly bean and go back to stock. I will upload a image file so you can flash stock and still keep root. Sorry for everyone who is having issues.
Sent from my Carbon-ize Evita using xda-developers app
Shows carrier as us cellular and not boost mobile???
Overall good post followed the steps and downloaded the zip files. Trying to,get back to stock rom and having problems. Noticed that the carrier shoe us cellular, thought the rom was for the boost mobile evo design 4g phone. Could this be the reason I am having a problem flashing a boost mobile rom?
Anyone have a stock rom for boost mobile evo design 4 g, purchased feb 2012, trying to get back to original state, thanks
Shouldn't matter. That pha4img.zip should work just fine. This guide is intended for boost mobile
Sent from my Carbon-ize Evita using xda-developers app
Nice Rom
This is a really nice rom, just one question, is the rom being worked on, or just being provided. This looks like the same rom that 2fast was working on, but that thread seemed to go dead, so I am wondering if it has been picked up again and if we are going to see all the features of the phone working soon.
Can you help me back to stock rom
Herc08 said:
Well I can update the guide to go back to stock. Thank you for putting the bugs out there.
Also. This is boost mobile not us cellular. If us cellular works, then I will update the guide. However it is intended for boost mobile. I just moved, so when I unpack my PC, I will update it to reflect stock ROMs.
Sent from my Carbon-ize Evita using xda-developers
Click to expand...
Click to collapse
htc evo design boost mobile
:good:,,ok first i want to let u know guys my english is not perfect,,i want to said thanxxx for this post i did step by step and my htc evo is workin perfect with jelly bean also i waste like 3 days trying to find the best way to unlock root my cell this one help me to do evrithing plus jelly bean is easy and im glad this post is perfect,,,,,thaxxx again and all credit to this guy thxxx again
Any news on this working for the US Cellular version(Hero S)? Just got one to replace my cappy and I'm having a lot of trouble trying to find a good up-to-date rooting guide, and roms, for this Hero S. Also trying to figure out what ROMs are available to me.
So now what...
Hello and thank you for the guide, very easy to follow. I am having one small issue however which is after installing the last two zip files the gapps and unofficial. zips my phone is stuck at the boot screen showing the Alien Android character and the CMX | CyanogenMod 10 at the bottom and does not go any further. So where did I screw up? Please help asap Thankyou,
Joeatheist
Attempted to reload stock software and no
after following directions to reload stock software It seems to stick while on white screen after loading takes place it says Parsing.... [PH44IMG.zip and goes no further. Yikes! Everything was fine until I tried to load those last two zip files and install jelly bean it was rooted and ICS loaded up just fine then once I went for jb this thing is useless. Any help would be greatly appreciated guys. Am I just being impatient is it gonna take an hour or two for this parsing message to clear? I s the re a way ouit of thisa/ Did I brick my phone? Anyone? Bueller...? Bueller...?
Respectfully,
JoeAtheist
---------- Post added 21st September 2013 at 12:49 AM ---------- Previous post was 20th September 2013 at 11:54 PM ----------
Well, I ended up pulling the SD card. Went to white screen and hit factory data rest. rebooted and it still tried to load CMX mod. And it booted fully! Apps are restoring and all is good in the world again. Thanks for baring with me and thank you for the root guide. Very happy so far. Whew!
Respectfully,
JoeAtheist
cmx
so I followed all the instructions and completeted everything. Only problem is(and it is a bit of a big one) when I went to reboot after installing the last two zip files the screen just stays stays at the screen where it displays some human like figure and the word "cmx cyanogenmod 10" is on the bottom. I know it isn't frozen since the blue animation at the bottom continues to happen but it never makes it way to the home screen. Anyone know how to fix this?
---------- Post added at 07:44 PM ---------- Previous post was at 07:11 PM ----------
aimtimes100 said:
so I followed all the instructions and completeted everything. Only problem is(and it is a bit of a big one) when I went to reboot after installing the last two zip files the screen just stays stays at the screen where it displays some human like figure and the word "cmx cyanogenmod 10" is on the bottom. I know it isn't frozen since the blue animation at the bottom continues to happen but it never makes it way to the home screen. Anyone know how to fix this?
Click to expand...
Click to collapse
Ignore this post. Followed Joeathesist's post and let it sit a little big longer this time and it worked! Jelly Bean is now running
As the topic reads, I've been trying most of the day to unlock the bootloader, I went through the process of obtaining my unlock code and my phone status when typing out a code suggested that it allows unlocking of the bootloader - I'm thinking okay cool, hopefully I'll have Cyanogenmod 12.1 on this thing in no time, right? WRONG! The device needs me to download and install fastboot drivers, which I thought should be an easy process but no matter what I do when I look at my phone through the device manager all I see is 'S1Boot Fastboot' - I even attempted using Flashtool (not Emma) and it too says install failed when trying to download the files needed. I just really need some help getting through this part of the problem, I've downloaded the SDK downloaded the USB drivers, updated them with the file from Sony but the end result remains the same. If it makes any difference (which I'm sure it will) I'm on Windows 10.
Thanks for any and all replies .. Edit // I forgot to mention the model is C833 and I recieved the latest OTA update from Sony for Lollipop 5.1.1
Installing the SDK is quite the overkill.
- Install ADB and Fastboot by downloading and running this tiny installer. It'll do the job for you.
- Install Flashtool and be sure that it recognizes your device. The device should be powered on when you open Flashtool the first time.
- Click the "BLU" button and copy/paste the unlock code you received from Sony.
You're done
Be sure to backup important stuff on your phone, in case something goes wrong. Move photos etc. to your SD card or something.
Klaos3000 said:
Installing the SDK is quite the overkill.
- Install ADB and Fastboot by downloading and running this tiny installer. It'll do the job for you.
- Install Flashtool and be sure that it recognizes your device. The device should be powered on when you open Flashtool the first time.
- Click the "BLU" button and copy/paste the unlock code you received from Sony.
You're done
Be sure to backup important stuff on your phone, in case something goes wrong. Move photos etc. to your SD card or something.
Click to expand...
Click to collapse
I appreciate the reply, and I managed to get the bootloader unlocked (I think) as both ADB and Fastboot are acknowledging my phone now. Problem I have now is while in Cyanogen Recovery, I hit the first option and may have soft bricked this phone - the cyanogen wiki stated I could make a backup by booting back into Android which is what I tried to do. I'm in the process now of repairing it with the PC companion hopefully and then I'll give it another go, this isn't my main phone though so basically I'm just tinkering/trying to learn the basics of installing custom ROMs. Thanks again for the reply, and if you have any other suggestions for me be sure to leave em here. BTW, I never installed the full Android Studio, just the zip file for the ADB and Fastboot files, I attempted that at first but found out you didn't really need em in the first place.
The CM Recovery is... pretty crappy, so don't use it if you don't have to. If you soft brick it (i.e end up in a bootloop or something), then just flash or hotboot a kernel with recovery, and you're good to go again, so you don't have to re-flash a ROM.
You can either use fastboot to flash a kernel (if you know how to use a terminal), or you can use Flashtool, QuickIMG etc, so:
Soft brick?
- Download a custom kernel with recovery. Doesn't matter which one if you're planning to flash a ROM straight away. You're planning to flash CM12.1, so you can use a random Ultra kernel like this one.
- Let's say we'll use Flashtool to flash it (since you already have it installed). Open it, hit the lightning bolt, click "fastboot", and then "kernel". Browse and choose the kernel you downloaded. Now disconnect from the computer and remember to press VOL up to enter recovery when it vibrates or the LED lights up.
- You're now in recovery again and you can go ahead and flash CM12.1. Remember to WIPE before or after you've flashed CM12.1. You'll end up with a bootloop if you don't do it. If you do, flash that kernel again and you're back on track.
Klaos3000 said:
The CM Recovery is... pretty crappy, so don't use it if you don't have to. If you soft brick it (i.e end up in a bootloop or something), then just flash or hotboot a kernel with recovery, and you're good to go again, so you don't have to re-flash a ROM.
You can either use fastboot to flash a kernel (if you know how to use a terminal), or you can use Flashtool, QuickIMG etc, so:
Soft brick?
- Download a custom kernel with recovery. Doesn't matter which one if you're planning to flash a ROM straight away. You're planning to flash CM12.1, so you can use a random Ultra kernel like this one.
- Let's say we'll use Flashtool to flash it (since you already have it installed). Open it, hit the lightning bolt, click "fastboot", and then "kernel". Browse and choose the kernel you downloaded. Now disconnect from the computer and remember to press VOL up to enter recovery when it vibrates or the LED lights up.
- You're now in recovery again and you can go ahead and flash CM12.1. Remember to WIPE before or after you've flashed CM12.1. You'll end up with a bootloop if you don't do it. If you do, flash that kernel again and you're back on track.
Click to expand...
Click to collapse
Gonna give all this a shot since the PC companion doesn't seem to be doing anything - I'll post my findings in a few if you're around. Thanks again man, I really appreciate your help.
Edit // Okay, nothing seems to be working now .. Flashtool says that my device has USB Debugging disabled, and whenever I power on the device you see the Sony logo, then a violet led and then the screen stays on and every once in a while it'll show a small battery indicator.
D2084 said:
Gonna give all this a shot since the PC companion doesn't seem to be doing anything - I'll post my findings in a few if you're around. Thanks again man, I really appreciate your help.
Edit // Okay, nothing seems to be working now .. Flashtool says that my device has USB Debugging disabled, and whenever I power on the device you see the Sony logo, then a violet led and then the screen stays on and every once in a while it'll show a small battery indicator.
Click to expand...
Click to collapse
Hmm, plug in the wall charger and charge it for a bit. I highly doubt that it's hardbricked since that's very very hard to achieve on a Sony device. Just kick it into fastboot by holding VOL UP while you plug it into your computer. The blue LED will light up. Then open Flashtool and flash the kernel, or download QuickIMG and flash the kernel (.img) with it. Be sure that it says "connected" before you do anything. Keep also in mind that you have to be in fastboot.
Klaos3000 said:
Hmm, plug in the wall charger and charge it for a bit. I highly doubt that it's hardbricked since that's very very hard to achieve on a Sony device. Just kick it into fastboot by holding VOL UP while you plug it into your computer. The blue LED will light up. Then open Flashtool and flash the kernel, or download QuickIMG and flash the kernel (.img) with it. Be sure that it says "connected" before you do anything. Keep also in mind that you have to be in fastboot.
Click to expand...
Click to collapse
I seem to have a brand new issue now, umm whenever I unplug the device and press VOL UP, I get this distorted screen. It's blue and has what looks to be white wording in the middle, I can't make it out though, this is after I put the kernel you recommended on my device. The kernel is the IMG file, correct?
Just thought I'd give you a bit of an update, I now have Cyanogenmod 12.1 on my Xperia Z Ultra - I flashed the custom recovery that came with the nightly I downloaded and then moved the actual zip to an SD card since like you said Cyanogen Recovery is a bit wonky (I tried sideloading to no avail). I have a couple question though, during the install process I noticed it said something about there 'no such volume' and I was sure I seen two failed prompts too but the ROM is on my phone? Should I look into that at all or is it fine? Most things seem to work .. camera, bluetooth, gonna have to throw my sim in there one of these days and test the cellular radios, but I just wanna say thanks again .. I learned a lot and managed to make something happen even if it's something small like installing a custom rom lol
D2084 said:
Just thought I'd give you a bit of an update, I now have Cyanogenmod 12.1 on my Xperia Z Ultra - I flashed the custom recovery that came with the nightly I downloaded and then moved the actual zip to an SD card since like you said Cyanogen Recovery is a bit wonky (I tried sideloading to no avail). I have a couple question though, during the install process I noticed it said something about there 'no such volume' and I was sure I seen two failed prompts too but the ROM is on my phone? Should I look into that at all or is it fine? Most things seem to work .. camera, bluetooth, gonna have to throw my sim in there one of these days and test the cellular radios, but I just wanna say thanks again .. I learned a lot and managed to make something happen even if it's something small like installing a custom rom lol
Click to expand...
Click to collapse
Just ignore that error. I've seen that myself a couple of times, and I don't know what it means, but it doesn't seem to affect anything.
There are a couple of things to keep in mind. CM12.1 has had some glitchy WiFi in the past, and I believe some people are still experiencing issues, so if you also experience some WiFi issues, it's a CM issue and not a hardware issue. Also, keep in mind that the Ultra GPe (Togari GPe) exists and is also supported by Cyanogen, so be sure to not flash the wrong version since the partitions are different between those two. I believe the recovery system will stop you from flashing it though.
Since Sony devices do not have a default recovery system, we have to bundle it with the kernel, so all custom ROMs around here, including CM, will have a recovery system added, but if you flash a ROM without a recovery system (like a stock ROM that you flash with Flashtool), you'll have to flash a kernel with a recovery yourself.
It's pretty easy to recover from issues and stuff on a Sony device once you know how things work. It's also a good idea to learn how to use flashboot through a terminal since that will potentially save you a lot of time down the road
Klaos3000 said:
Just ignore that error. I've seen that myself a couple of times, and I don't know what it means, but it doesn't seem to affect anything.
There are a couple of things to keep in mind. CM12.1 has had some glitchy WiFi in the past, and I believe some people are still experiencing issues, so if you also experience some WiFi issues, it's a CM issue and not a hardware issue. Also, keep in mind that the Ultra GPe (Togari GPe) exists and is also supported by Cyanogen, so be sure to not flash the wrong version since the partitions are different between those two. I believe the recovery system will stop you from flashing it though.
Since Sony devices do not have a default recovery system, we have to bundle it with the kernel, so all custom ROMs around here, including CM, will have a recovery system added, but if you flash a ROM without a recovery system (like a stock ROM that you flash with Flashtool), you'll have to flash a kernel with a recovery yourself.
It's pretty easy to recover from issues and stuff on a Sony device once you know how things work. It's also a good idea to learn how to use flashboot through a terminal since that will potentially save you a lot of time down the road
Click to expand...
Click to collapse
Everything seems to be working quite well so far, including the wifi but I'll keep what you said in mind. I used the same process to install GApps on it too so now I have the play store and google apps install as well. I have another question though, whenever I plug in a charger to charge the device .. I notice the screen never goes off but stays black and has nothing on display sorta like ambient display, would you know if that's a feature of Cyanogenmod or did I goof somewhere during the install? Thanks in advance for your reply.
D2084 said:
Everything seems to be working quite well so far, including the wifi but I'll keep what you said in mind. I used the same process to install GApps on it too so now I have the play store and google apps install as well. I have another question though, whenever I plug in a charger to charge the device .. I notice the screen never goes off but stays black and has nothing on display sorta like ambient display, would you know if that's a feature of Cyanogenmod or did I goof somewhere during the install? Thanks in advance for your reply.
Click to expand...
Click to collapse
Could it be Daydream? Go to Settings -> Display -> and disable Daydream. Now check again. If it's not Daydream causing it, then it might be a bug. Do a reboot in case it's a small glitch of some kind. If it's still on when charging, then I'm not sure what it could be (other than a bug, that is).
Sorry for the late reply, but I figured out the reboot issue .. I had to turn off the 'wake up' feature when you plug in your device. I have a whole new issue though, I'm not sure if it can be resolved though - I was on the phone with MetroPCS for about an hour trying to figure out why my phone wouldn't connect to their network. I know Cyanogenmod comes with APN's pre-installed but even after the representative tried helping me set up a new APN .. it was a no go, so I switched back to the current phone I'm using - Alcatel Idol 3 4.7 .. anyways, I'd like to hear your input on what the issue could be as I'd really like to go back to using this phone since the software aspect is far more flexible with a custom ROM like Cyanogenmod.
D2084 said:
Sorry for the late reply, but I figured out the reboot issue .. I had to turn off the 'wake up' feature when you plug in your device. I have a whole new issue though, I'm not sure if it can be resolved though - I was on the phone with MetroPCS for about an hour trying to figure out why my phone wouldn't connect to their network. I know Cyanogenmod comes with APN's pre-installed but even after the representative tried helping me set up a new APN .. it was a no go, so I switched back to the current phone I'm using - Alcatel Idol 3 4.7 .. anyways, I'd like to hear your input on what the issue could be as I'd really like to go back to using this phone since the software aspect is far more flexible with a custom ROM like Cyanogenmod.
Click to expand...
Click to collapse
Are you talking about connection to their network altogether, or just data? Do you have reception? Check that data is enabled in Settings -> Data usage.
I can guarantee that this is a software issue, BUT one last question. How old is your SIM card? There have been a few cases when people have been in the same situation as you, got a new SIM, and that fixed the issue. You could do that, or flash another ROM. CM12.1 is beta, so bugs have to be expected, and it's far from a solution if you plan to just flash something and use it for a longer period of time. If you want something very stable and stock, then highly recommend Scrubber's GPe 5.1 port, which is rock solid.
Well my sim card isn't too old, had it for about a year. Once she laced the sim card to the new phone I could make calls and texts but for some reason the Internet wasn't working - she had me go through all the steps to make sure things like data was enabled and airplane mode was off but it still resulted in not being able to establish a connection to the web. So I'm gonna try and flash the GPE rom you're talking about later on tonight once I get home from work and see what happens then - mind leaving me a link to the rom/recovery? Thanks in advance.
D2084 said:
Well my sim card isn't too old, had it for about a year. Once she laced the sim card to the new phone I could make calls and texts but for some reason the Internet wasn't working - she had me go through all the steps to make sure things like data was enabled and airplane mode was off but it still resulted in not being able to establish a connection to the web. So I'm gonna try and flash the GPE rom you're talking about later on tonight once I get home from work and see what happens then - mind leaving me a link to the rom/recovery? Thanks in advance.
Click to expand...
Click to collapse
Sure. Here it is. Remember to download 5.1, and not 5.0. Recovery is included in the ROM, so you don't have to flash anything else.
Quick update, I've flashed the ROM but so far it seems to be stuck in a bootloop, its been stuck on the swaying Google logo for about 10 minutes now. It might be because I sideloaded using a micro SD card because for some odd reason the 'flash the system' option on Flashboot wasn't working for me. So I turned the phone off and will give it another try tomorrow, if you have anymore tips for me I'll be glad to hear em.
D2084 said:
Quick update, I've flashed the ROM but so far it seems to be stuck in a bootloop, its been stuck on the swaying Google logo for about 10 minutes now. It might be because I sideloaded using a micro SD card because for some odd reason the 'flash the system' option on Flashboot wasn't working for me. So I turned the phone off and will give it another try tomorrow, if you have anymore tips for me I'll be glad to hear em.
Click to expand...
Click to collapse
How did you flash it? It must be flashed in recovery on the device and not using Flashtool. Flashtool is strictly for stock Sony ROMs or FTFs. Never use it for anything else besides flashing FTFs and kernels. So:
- Go into recovery
- Remember to wipe! If you don't, you'll get a bootloop
- Install from SD card
- It will probably throw an error at you, but don't touch anything. It's still flashing.
- Reboot
- Wait a couple of minutes.
Klaos3000 said:
How did you flash it? It must be flashed in recovery on the device and not using Flashtool. Flashtool is strictly for stock Sony ROMs or FTFs. Never use it for anything else besides flashing FTFs and kernels. So:
- Go into recovery
- Remember to wipe! If you don't, you'll get a bootloop
- Install from SD card
- It will probably throw an error at you, but don't touch anything. It's still flashing.
- Reboot
- Wait a couple of minutes.
Click to expand...
Click to collapse
Just did everything you just said, will update you tomorrow with results.
Well I did what you said and left the phone to charge overnight - it was in bootloop when I went to sleep and .. bootloop when I woke up (at least it's charged now lol) I'm gonna try again though. I see that CWM has a sideload option, so I'm gonna wipe everything and try to sideload it from the ADB through the command prompt and see what happens. Feel free to leave any other suggestions though.
Got a question though, when I sideload the zip file should I sideload everything within the zip file or just the system image file? Maybe I'm getting bootloop because I'm installing a kernel on top of another kernel?
D2084 said:
Well I did what you said and left the phone to charge overnight - it was in bootloop when I went to sleep and .. bootloop when I woke up (at least it's charged now lol) I'm gonna try again though. I see that CWM has a sideload option, so I'm gonna wipe everything and try to sideload it from the ADB through the command prompt and see what happens. Feel free to leave any other suggestions though.
Got a question though, when I sideload the zip file should I sideload everything within the zip file or just the system image file? Maybe I'm getting bootloop because I'm installing a kernel on top of another kernel?
Click to expand...
Click to collapse
Sideload/flash the .ZIP. Do not extract it. You should simply just boot into recovery, choose "ScrubberPortRom_GPE5.1_LMY47D.zip", flash and wait for a couple of minutes and then reboot. That's it. The first boot should take around 5 minutes.
- Remember to do a full wipe in recovery before you flash
- Flash ScrubberPortRom_GPE5.1_LMY47D.zip
- Reboot
And do share any error messages if you get any while flashing.