Related
Hello, xda!
I've been around on the forums for some time, flashing and messing with ROMs before, but with an old HTC Touch Pro. So forgive me for seeming like a leecher.
I've come here to ask a few questions reguarding Andriod roms and flashing/upgrading procedures. I'm comfortable with using RUUs to upgrade, but who isnt...
I've had my HTC Hero for about 2 weeks now and I accidently bricked one already. I've rooted manually once, and got no signal on the stock Sprint ROM so I tried to go back to the original flash recovery but killed my phone instead.
Could someone help me out. I've read guides and been very, very anxious to upgrade and root but as you've read, I've already bricked my phone once so I'm pretty cautious now.
From what I understand, I need to root to 1.2.3, NAND backup, WIPE sd card & phone, then flash damage control's rom.....
So do I have it right or should I read a bit more?
Any help and tips from some experienced flashers would be much appreciated. Thanks!
mjones832 said:
From what I understand, I need to root to 1.2.3, NAND backup, WIPE sd card & phone, then flash damage control's rom.....
So do I have it right or should I read a bit more?
Any help and tips from some experienced flashers would be much appreciated. Thanks!
Click to expand...
Click to collapse
First off; we're happy you chose not to give up and came back a second time.
What you do need to do is; 1) Root and flash a Recovery image 2) Make a Nandroid back up, 3) Wipe ONLY your phone (not your SD Card, unless you want to do Apps2SD) and 4) Flash the ROM of your choice.
**The rooting guide I linked above is the way I prefer to do it; via adb commands. However, you could also you use Flipz's kitchen to do all of this for you.
.
For more information about Flipz's kitchen, please go here: Flipz's Kitchen
Also, do note -- for other tutorials/guides/references; go HERE
I was seriously nervous to start the process as well. As I told someone else, being nervous is a good thing. That just means you'll be careful.
I seriously recommend reading this thread and following instructions. Do not skip steps, do not pass go, do not collect $200. I've personally used the Windows guide and the Linux guide. Both are very well done and I can verify that they work.
Beyond that, the Search function is fantastic and provides lots of information. Don't be afraid to ask questions, either. Most of us are nice and like to help, even if we do call people n00bs.
WOW! Insanely quick replies. Thanks for that guys. This is what I wanna hear so I'll be doing the flash when I get home.
I'm using the 2.1update1 sprint beta ROM right now so should I revert back to the 1.56 and THEN do all this or can I just jump right in. I've always been confused as to which rom needs what flash rec root file or w/e.
And yes, I do want the A2SD thing as thats one problem I'm having right now. I've only got 16MB of storage left of my current storage area but my 8GB sd card is almost empty except for a few songs and pictures. Also, should I upgrade my sd card to a higher class if my 8GB is a class 2?
Thanks again guys!
Also, I mentioned that the last time I tried to root, I had no service after I did so. Why is that and what do I do to fix this? I couldn't find anything on this in google searches.
mjones832 said:
Also, I mentioned that the last time I tried to root, I had no service after I did so. Why is that and what do I do to fix this? I couldn't find anything on this in google searches.
Click to expand...
Click to collapse
Some people say to toggle airplane mode on and off. Some people say reboot. The last time this happened to me I just played a video game for ten or fifteen minutes and it fired up.
mjones832 said:
And yes, I do want the A2SD thing as thats one problem I'm having right now. I've only got 16MB of storage left of my current storage area but my 8GB sd card is almost empty except for a few songs and pictures. Also, should I upgrade my sd card to a higher class if my 8GB is a class 2?
Click to expand...
Click to collapse
I've not used apps2sd myself, but I'm told the higher class card the better, for obvious reasons.
Thanks, subcypher! I've got absolutely no reason to not do this. I'll be doing it as soon as I get home.
mjones832 said:
Thanks, subcypher! I've got absolutely no reason to not do this. I'll be doing it as soon as I get home.
Click to expand...
Click to collapse
Have fun! We'll be here when you get back.
yes.. a faster class sd card is highly recommended!!! other wise with a2sd, you might see more lag... and issues.
I personally, would not do a2sd at the same time as you upgrade. finish the upgrade first. make sure all is good...
then do the a2sd. and do a nandroid backup again before.
So I just tried to go back to 1.56 with the signed RUU that sprint gives out and it gave me an error. Failed to load bootloaded or something similar to that.
Remember, I'm on the 2.1update1 beta release of sprint's rom but I wanna root and flash to DamageControl's 2.1.
I've tried looking into how to root my current 2.1update1 beta ROM but I didn't come across anything worthwhile.
Anyone know whats going on???
mjones832 said:
So I just tried to go back to 1.56 with the signed RUU that sprint gives out and it gave me an error. Failed to load bootloaded or something similar to that.
Remember, I'm on the 2.1update1 beta release of sprint's rom but I wanna root and flash to DamageControl's 2.1.
I've tried looking into how to root my current 2.1update1 beta ROM but I didn't come across anything worthwhile.
Anyone know whats going on???
Click to expand...
Click to collapse
What steps did you take to use the Sprint RUU?
In order to run the Sprint RUU, you need to do:
**Make sure you have the appropriate drivers to detect HTC Sync**
1. Install HTC Sync on your computer
2. After install, open and leave the HTC Sync Window open
3. Connect your phone; and click on the sync option. You should be able to sync, if not - then you're having driver issues.
4. After you've successfully synced, NOW run the Sprint 1.5 RUU.
5. Upon a successful RUU, you'll have your phone back to its factory settings.
Now you can reroot, flash whatever ROM you like, and flash any/all add-ons.
As far as the signal goes, the following are from the Fresh 2.0d install page.
A reboot after the first bootup finishes is recommended, especially if you were previously having PRI/PRL problems.
Click to expand...
Click to collapse
If after flashing you end up with any data issues then first try rebooting. If that doesn’t resolve it for you then try updating your profile and PRL. This is a side effect of the different PRI’s and PRL’s that people have ended up on. You may actually need to update your profile and PRL a couple times to get everything going but I promise it will. You should end up on PRL 60663.
Click to expand...
Click to collapse
I personally had no problems, but I was flashing Fresh, not Damage.
Ok, I've got it rooted, and nand-backup stored on my PC.
DamageControl says to wipe before his install. Do I "wipe data/factory reset" or "wipe Dalvik-cache" or any other options?
If its the same as Fresh, they want you to do a Wipe data/factory reset
Thanks everyone! I'm installing DamageControl right now! I'll let you know how it goes.
Success! I've got the phone rooted, at least I think I do, and flashed to DamageControl v2.08.
My next task is I really want to get my apps to install to my sdcard. I've got a 8GB class 4 sdcard. Should and can I put my apps onto this? I've heard that the hero doesnt even read and write faster then 2Mbps so I'm good, right?
Not sure if I'm rooted. I've installed a few apps that require SU and when they try to do a "SU Request" the screen sits at a black screen with that title at the top.
Any idea on whats going on?
If you were able to flash a damage less rom you're rooted.
On the black window there should be am option on the bottom to allow, select it.
-------------------------------------
Sent via the XDA Tapatalk App
The black screen for SU is caused by not having USB Debugging turned on as it is required for superuser permissions. I have not tried A2SD because I only have a class 2, but have read that unless you have a class 6 it can be slow.
Did the 1 click root successful and loaded up cyanogen 6 and then tried thinking I was a big dog and screwed around and f'd up my phone,it won't get past any of the recovery screens,I will link what I have gone through over at nof.net,sorry for the link but I suck at typing because it takes me forever so please read,also I will paypal 20 bucks who can get me out of this debacle. Thanks.
oops can't link cause I'm new but If you are kind enough to go to nexusoneforums.net and read it ,It's titled In deep doodoo.
Basically it won't boot past the x no matter what i do,but I can see everything is still on my memory card through my laptop
direct link to his post
http://www.nexusoneforum.net/forum/nexus-one-development-hacking/8483-deep-doodoo.html
thank you
10 char
I think you need to locate a stock, signed update zip file and put it on your sd card. I'd do this seperate from the phone. Take the card out and put it in your laptop or whatever you have to read it.
I'd then get back to where your were on page four of your other thread where it says apply update zip.
you don't know if you have the stock recovery img still? or Ra or clockwork?
your phone isn't broke, I wouldn't worry too much.
You also don't know if you bootloader is unlocked or not?
heres frf91 full if you choose to go this route http://www.mediafire.com/?xniymzimojg
Stock ROM's here: http://www.mediafire.com/n1passion
Sounds to me like you need to relax a little and read a bit more before jumping in with both feet... Rooting isn't necessarily for everyone.
I won't ever ever attempt this again.
Macklessdaddy said:
I won't ever ever attempt this again.
Click to expand...
Click to collapse
ahh don't do that! I don't even want to begin to count how many bootloops I've had, I'm pretty sure I've seen more of that X than I have of my home screen. I think once you've messed up once and had someone help you to fix it it kinda implants into your head how to fix it in the future. My only advice for future attempts is to Nandroid backup (make sure you have atleast 1 sure working back up, then do further updated back ups along side it)
Can someone tell me which file I need in post #5 for a tmobile n1.Thanks
http://www.mediafire.com/?xniymzimojg
jbrinkley,I downloaded the file and put it on the memory card,but I'm still getting the same x screen,anything else I can try.
I won't ever ever attempt this again.
Click to expand...
Click to collapse
The only way to master something is through multiple failures
Sent from my Nexus One using XDA App
Somebody help me,I had no clue this phone meant so much to me.
wrench115 said:
The only way to master something is through multiple failures
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I don't want to fail with my phone.Trust me when and If I get it working I will stay in my lane and leave the rooting to you guys.
Flashing back to thw original stock rom should fix it there's a link posted above. Atleast it worked when I had a g1 and royally screwed up. I would try that first.
Sent from my Nexus One using XDA App
I cant,or obviously don't know how to flash back to the original rom.Don't mean to sound ungrateful but it appears nobody is reading about the problem I'm having ,again I'm stuck at the x and can't get out.
I will paypal 20 bucks to the person who helps me out of this mess
OK, relax... take a deep breath... and try this out...
1. Download a full ROM zip (e.g. Passion-EPE54B.zip) from http://mediafire.com/n1passion
2. Pop out your SD card and pop that zip onto your SD card, be sure to rename it to PASSIMG.zip
3. Boot into bootloader mode (power off -> trackball + power)
4. The phone should pick up the PASSIMG.zip and ask you if you would like to update it... select yes!!
This will restore you to the stock EPE54B image, you can then download the FRF91 OTA or re-root you phone...
Craig,I downloaded the file from post#9 and renamed it PASSIMG.zip and went to bootloader and the x came up again,do I need to use the 54 one you were talking about to get to 91,sorry but I'm smartphone illiterate as hell.I get a message that says no image or wrong image
If I try to apply sd card update I get this message
failed to open\sdcard\update.zip(no such file or directory)
E signature verification failed
Installation aborted
Does it matter where on the memory card the file is at?
what we don't know is what recovery you have, if you bootloader is unlocked or not.
I don't know anything about that one click method. if you have a nandroid file on you sd look in there and see if you have actual backups.
and now i can't remember if you got to the restore menu or not.
jbrinkley said:
what we don't know is what recovery you have, if you bootloader is unlocked or not.
I don't know anything about that one click method. if you have a nandroid file on you sd look in there and see if you have actual backups.
and now i can't remember if you got to the restore menu or not.
Click to expand...
Click to collapse
bootloader not locked,under clockwork mod I see recovery and there is 3 backups under recovery
Flashing the official gingerbread in u8800 its irreversivel process, at least for now.
If you flash it you have to keep it as no way of going back.
If you root it using the only available method, bye bye!
Everytime you reboot the endless bootlooping starts and the only way to stop it is formatting data.
Which means everytime you reboot = bye bye all data and apps etc.
I think is something that its major importance and no one is mentioning this!!!!
I don't know, maybe I've been preaching to deaf ears or something...but...you can re-install the old ROM back, the CWM recovery won't work with the official GB - that much is true - but you will be able to downgrade to an official 2.2.2 (I used the B162) version with the regular update method (at least I was and everything is working just as normal as it used to).
So, irreversible - I don't think so
with the current CWM recovery - it's a no-go
edit: that being said, what works for me, doesn't necessarily work for everyone, so be careful and blame the guy in the mirror -not me, if it doesn't work for you. =)
I think Huawei says wrong here. I flashed 2.3 yesterday. After that, because of the haptic issue I flashed back to official 2.2. Only problem after the 2.2, recovery console had opened. I did factory reset there and phone started without a problem. Then, I had upgraded to 2.3 again. Still haptic don't vibrate. Other than, no problem here. Maybe, I will go back again to 2.2.
Well you are lucky then because you are the only one.
Perhaps what is saying in the official intructions that will be impossible to dowgread after this upgrade won't apply to you.
I have try it with at least 8/9 versions of official release and nothing works!!!!
what 2.2 version is that and you did it after or before rooting?
Have you tried with internal sd? I copied dload folder to internal and started the upgrade process from Storage-Upgrade Firmware. Where did your phone stuck?
Edit: I didn't root my phone. Waiting proper solution. I had used B138.
no, I'm using external SD.
now I'm downloading another official release to try to downgrade using another one...
this time is U8800 V100R001C17B162CUSTC17D001
Druida69 said:
Well you are lucky then because you are the only one.
Perhaps what is saying in the official intructions that will be impossible to dowgread after this upgrade won't apply to you.
I have try it with at least 8/9 versions of official release and nothing works!!!!
Click to expand...
Click to collapse
Well, like I said, what works for me doesn't necessarily work for you.
Anyway, this is what I did and it worked, maybe it can help others.
0. Copy the original B162 ROM ("dload"-folder which has two files, UPDATE.APP AND UPDATE_CUST.APP) to the root of your SDCARD
1. Update to B162 by holding down +- keys while turning on the phone
2. After the first reboot, it's giving error messages for not being able to mount this and that...just ignore it and...
--> Wipe data / factory reset --> remove battery
3. Update the B162 again --> this time everything should go OK, if so, your phone is back to stock B162 and you're ready to use it or update a custom rom (just install Clockwork recovery like you used to and start from there)
The last point (3) may be unnecessary, but I did so just to make sure everything's ok.
Edit: OK, and I meant b162, not b160...
Druida69 said:
no, I'm using external SD.
now I'm downloading another official release to try to downgrade using another one...
this time is U8800 V100R001C17B162CUSTC17D001
Click to expand...
Click to collapse
For me it also works. I have downgrade without any problem and I use to the b 162 version. Now Ian back to oxygen
Sent from my u8800 using XDA App
yes I made it with this B162.
**** this **** I'm going back to custom rom.
No point of using this official release if future customs will use the libs from this one.
Druida69 said:
yes I made it with this B162.
**** this **** I'm going back to custom rom.
No point of using this official release if future customs will use the libs from this one.
Click to expand...
Click to collapse
And then there's the fact that the official gb is still beta, it's not supposed to work perfectly. But as long as the dev team here stays active, I think that I'm gonna stick with custom roms too.
ho my god.
didn't work.
is always booting into recovery
I am stuck here also (
Nothing worked
I tried clockwork recovery - it doesnt get to. It is just rebooting.
I tried with various dload UPDATE.IMG's (GB Overseas, GB orig chinese,B162,B138) nothing is working - stucked in "Step 1/2 Unpacking" window forever.
Anyone has solution for this ?
Two weeks ago I've flashed the U8800Pro version - real mistake
I've started a topic here:
http://forum.xda-developers.com/showthread.php?t=1327715
katu2006 and on the second page flibblesan gave me a method to start my phone working well.
Post #4, #11 and #13.
Maybe this will help you,too?
sbasil said:
Anyway, this is what I did and it worked, maybe it can help others. (...)
Click to expand...
Click to collapse
You sir are a LEGEND. My phone "lives" again! On CM7 again...
manage to install miui.
several versions now up to the newest one.
I noticed on all of them that it mount the SD card when connected to USB but only shows the system files and not allow writing, copy, cut, etc.
Saying that I dont have permission to change the SD
Druida69 said:
Flashing the official gingerbread in u8800 its irreversivel process, at least for now.
If you flash it you have to keep it as no way of going back.
If you root it using the only available method, bye bye!
Everytime you reboot the endless bootlooping starts and the only way to stop it is formatting data.
Which means everytime you reboot = bye bye all data and apps etc.
I think is something that its major importance and no one is mentioning this!!!!
Click to expand...
Click to collapse
I have just flashed with new U8800V100R001C00B517G001(Beta1.0)(Overseas Normal)(Gingerbread) but after flashing I kept waiting for start my phone. I restasted many times but same, then I format data its worked and when restarted again it goes in same condition any help ?
until flash disk is writable and it is - there will always be way to go back to old versions it just files.. like reinstalling windows on your pc.
Since the new Rom is public I have read all posts about it here. Maybe I had lucky, or simple due it without messing with the files.
Yesterday I made the upgrade to the new rom, directly from the last Oxigen version, without downgrade to 2.2. I simply create the dload folder on SD card, put there de update file, boot with +- Power, and chose upgrade from SD card.
After step 2 I reboot the phone a install step 3 upgrade. Everything as installed fine, no boot loops, nothing...
Also the root method decribed in this forum as work on first time.
24 hours after the upgrade, and some reboots to test, I never se the boot loops, and the phone is working well.
The new ROM, even in beta stage, to me is a great improvement.
Well either you were lucky or me and the majority were unlucky.
But issues only start to happens when rooting.
So that you can see it fried me the 1 USB cable. This cable is only good to charge the battery now....
Also, ****ed the device USB storage MOUNT.
I connect it to the computer and the computer sees it as a CD drive not allowing any changes.
Also when press the button to mount the USB on the device it never gets mounted and gives the messages that the SD can now be removed.
So I have put this issue many times but up to the moment no one even reply to help.
Hi all,
Need help with my phone... :\
So I wanted to install ICS on my phone today (http://forum.xda-developers.com/showthread.php?t=1492957) and I looked at the instructions, obviously you have to have a stock ROM installed first before going for the ICS update. At this time I had CM7.1 installed. So I chucked the files on my SD Card to install (the ICS and Stock) and went ahead into clockwork recovery to try and install the stock ROM first. This didn't work, as at the time I didn't know you have to install it via the pink screen and extract the zip folder and put the dload folder in the root of the sd card. So when I tried to install it, it said starting installation, and then would say installation aborted, I had no idea why, so I tried another couple of times, still didn't work. I then updated my clockworkmod recovery to the latest version for the U8800 and it still didn't work (as I was obviously doing it wrong...). I also happened to have an update for CM7 on the SD card that I never got around to installing (7.1.0.1), and so I tried to install that and again it said installation aborted (not sure why that didn't work, should of...). So then I thought, that's odd, nothings working, betcha the ICS ROM won't install either, see if something else is wrong, so I pressed install... and it started installing... not exactly what I wanted or was expecting. So it seemed to install alright with no errors, so I did a reboot out of recovery. It then stuck on the white Huawei logo screen and just stayed there... some folders got created on my SD card (apps that I had installed on CM7), no idea why, it didn't seem to boot, left it for 5 minutes and still just the white logo screen.
So I then did some more reading and learnt that I needed to put the official ROM's dload folder to the root of the SD card and install it via the pink screen. I tried this, unpacks it fully and completes step 1, but it gets to step two, and 5 seconds later after it starts attempting to install the ROM it says, Installation Failed.
So I was looking around for people who had a similar problem as me, and found some, they found a way to fix it which was to put the dload folder in the root of the internal SD card, unfortunately I have no idea how to get to that when the phone doesn't boot up into the OS. I tried putting it in the internal storage via the pink screen, but that's only 200-250MB in size, and the file needs around 300MB, so there wasn't enough room. I tried repartitioning the storage hoping this would increase it, or return it to normal (as I had partitioned it before to the 1.42GB/1.12GB partition that others had posted up previously) and it didn't change a thing. So I have no idea how to get to internal storage D:
Not having fun so far... so I thought I might try and install CM7 again, and then go to stock, and then to ICS, or maybe just leave it on CM7 and give up for now. Unfortunately the version of CM7 I had isn't available anymore, and the newer version you have to have stock ROM installed first, so I decided to grab oxygen instead. Downloaded it and chucked the zip folder onto my SD card and tried to boot into recovery (Power+VolUp) and now it won't even go into that! It goes to the pink screen (Power+VolUp+VolDown) without any issue and I can connect to the computer and access the files on there.
So basically, I've bricked my phone and I would love it so much if you could help me get it back, I really don't want to have to go back to my old Nokia 2760 (http://www.gsmarena.com/nokia_2760-1975.php) where the speaker doesn't even work, so if I make/receive a call, I have to put it to loud speaker or headphones to actually hear their voice... would be much appreciated.
Thanks,
Gunny
I think you have some hope left if you can go in the pink screen mode. You should find some istructions from general section and Q&A section. If you can go to pink screen you should be able to install official Huawei rom.
Pressa00 said:
I think you have some hope left if you can go in the pink screen mode. You should find some istructions from general section and Q&A section. If you can go to pink screen you should be able to install official Huawei rom.
Click to expand...
Click to collapse
I finally got it all sorted, if it wasn't for that pink screen, I'd be stuffed!
I had to go back to a 2.2.1 ROM before it would finally accept it and install. Had a bit of cache and corruption, but android eventually cleared/cleaned itself and put itself back to normal. Now I've got the official version of Gingerbread on my phone, and I'm not sure if I should upgrade to the official version of ICS or whether I should upgrade to Aurora's (http://forum.xda-developers.com/showthread.php?p=22682229#post22682229) version of ICS. Thoughts? And don't worry, this time I won't screw it all up!
Thanks all!
Alright, just discovered my official ICS ROM is for the U8800 pro, not the standard one, so I guess I will be going for Aurora!
Gunny007 said:
This didn't work, as at the time I didn't know you have to install it via the pink screen and extract the zip folder and put the dload folder in the root of the sd card.
Click to expand...
Click to collapse
I have a Huawei U8860 and wants to go from custom rom MIUI to stock rom B925. Can I just follow your advice here and install it via the pink screen?
hi. so I just bought my a500 used in the forums never rooted or unlocked already on the ice ota. I tried to unlock the bootloader' but everything just freezes while flashing. I am just stock rooted for now' but I really want to do some good dev work since my a2 has a locked boot loader. thanks/for any help and sorry if this had been covered. I may seem like it but I am not a complete noob.
Sent from my A500 using xda premium
lkrasner said:
hi. so I just bought my a500 used in the forums never rooted or unlocked already on the ice ota. I tried to unlock the bootloader' but everything just freezes while flashing. I am just stock rooted for now' but I really want to do some good dev work since my a2 has a locked boot loader. thanks/for any help and sorry if this had been covered. I may seem like it but I am not a complete noob.
Sent from my A500 using xda premium
Click to expand...
Click to collapse
Which OS are you on? ICS? HC?
Which "one step" app are you using to change out bootloaders?
MD
Moscow Desire said:
Which OS are you on? ICS? HC?
Which "one step" app are you using to change out bootloaders?
MD
Click to expand...
Click to collapse
I am on stock rooted is. it came stock ics and I just rooted it. I have tried pretty much all the tools available in windows, and done it manually with no flash in ubuntu. I can give u the. exact nvflash error later, but it falls I think on the step of actually flashing the new bootloader
Sent from my A500 using xda premium
lkrasner said:
I am on stock rooted is. it came stock ics and I just rooted it. I have tried pretty much all the tools available in windows, and done it manually with no flash in ubuntu. I can give u the. exact nvflash error later, but it falls I think on the step of actually flashing the new bootloader
Sent from my A500 using xda premium
Click to expand...
Click to collapse
Well, if you can't use the tools, (you don't need to give the NVFlash error, I already know what it is), then first try the following. (no matter how silly they sound.
1. Different PC
2. Different USB port. (mine has 4)
3. A good USB cable. Using one that comes with the printer or camera, or an el-cheapo won't work. Data pins aren't always the same. I use my HTC cable.
4. Make sure anti-virus and such is off.
If that doesn't work, only recourse is to roll back to 3.0, preferably by RUU. Problem is, you need an HC UID number to run the ruu. That should set your partitions in place. It's possible you might be able to run an HC 3.2 full update, grab the UID, then run the RUU.
After that, do the NVFlash to get the bootloader/CWM.
At least if it were me, that's the route I would take. Never did it before, but seems sound.
A Pity you bought it already with ICS.
MD
Moscow Desire said:
Well, if you can't use the tools, (you don't need to give the NVFlash error, I already know what it is), then first try the following. (no matter how silly they sound.
1. Different PC
2. Different USB port. (mine has 4)
3. A good USB cable. Using one that comes with the printer or camera, or an el-cheapo won't work. Data pins aren't always the same. I use my HTC cable.
4. Make sure anti-virus and such is off.
If that doesn't work, only recourse is to roll back to 3.0, preferably by RUU. Problem is, you need an HC UID number to run the ruu. That should set your partitions in place. It's possible you might be able to run an HC 3.2 full update, grab the UID, then run the RUU.
After that, do the NVFlash to get the bootloader/CWM.
At least if it were me, that's the route I would take. Never did it before, but seems sound.
A Pity you bought it already with ICS.
MD
Click to expand...
Click to collapse
Alright, thanks.
I feel like such a N00B right now, LOL. This is like when I first bought my Atrix 2.
I bought it used on the forums and figured I was good, I don't have to even update it and stuff since it is on ics, and the bootloader is unlocked, so I will have aokp on it by the end of the night I get it. I guess I was wrong....
Anyways, I tried other ports, and I was using the good motorola cable, but tried the one that came with i as well, so I guess I have to go back to HC. Why would that help? is the idea that I can then just unlock it some other way? If so, how might I go about getting the UID.
Also, is it worth trying to flash the honeycomb bootloader? any better chance there? cause with that I could just flash the new one with a zip or fastboot. also, Is there any way to just put the new one on by simply putting it on the partition using cat or something. I know I did that on my a2 with recovery, but it would brick with the bl.
Thanks for your help.
Thanks everyone, I got it, here's what I did. As usually I massively screwed things up in the process, but I got it:
So first, I tried to flash again in a few different ways, no success, no harm.
Then I downloaded a HC 3.1.2 or something full rom and put it on my sdcard and rebooted and applied it. BRICK. boot verification failed. So that clearly didn't work, and I realized that is because I had an HC rom with ICS bl.
Long story short I tried to get back with an ics update.zip with no luck, so I tried using a stock rom EUU, but it got to the part where it was looking for the tablet with adb debugging so I cancelled it, since obviously that was not going to do anything. Then I tried a few more zips, with no luck at all and somehow ended up in fastboot, which makes no sense since nothing flashed (or at least I though). From there I tried flashing cwm so I could recover, but it just kept saying "not supported in lock mode" so I gave up on that.
Now comes the accidental fix part. I tried the other exe in the EUU just to see what it did, and it appeared the same, so I just kept hitting continue, and when it got to the usb debugging part, I must have hit minimize instead of close. about 30 minutes and me being really pissed that I somehow hardbricked later I realized there were now 2 windows of the EUU thing open. One said that it could not find my device, and to manually put it in apx mode. WOW, so I was just too impatient before.
Long story shorty again, that worked and it was back on stock honeycomb, and I flashed the HC unlocked BL with no issues, but that did me no good, so I put aokp on my sdcard and flashed the ICS BL with no problem at all this time. I rebooted into recovery and flashed aokp, watched the boot animation that reminded me it was made by a 7 year old girl for a few while the dalvik cache built, and then I was good to go screw with the unusually large number of settings included and flash gapps.
So, yeah, basically I am an impatient moron, but hey! it worked.
Now I just have to find a good OC'd kernel that will work with aokp and I an good to go.
Just a heads up, I plan on building JB aokp and releasing it, so get ready for some serious unicorn swagger in a few months when I finally decide to do it.
I like that process. Flash everything till something works :laugh::laugh::laugh:
At least it works for me sometimes
Glad you got it going.
Listen, edit your post and link to the EUU files you were successful with. Might help some others.
MD