Hi guys,
As I said I'm a total noob that just got my Amaze and I'm looking for some guidance to tune it up a bit.
I've been reading LOTS! on the rooting and other procedures but the problem is that most of it it'sd just giberish to me.
So if anybody there is willing to hold my hand for a bit over the first steps so I don't wack my head on the floor too many times I'd be appreciated.
Basically I'm pretty sure I can do the rooting by myself. I already downloaded allthe soft and guides in advance for it.
But then I'll probably need help chosing roms and other stuff.
I've been following Xboarder's posts but if you loose one day reading you just fall back like a 100 pages and as I said it's hard when you don't understand all the lingo (I like to understand the way things work).
Anyway, here I am almost ready to start with it but I'd like to have somebody on my back before I start...
I know it's seems pretty safe to root but since I really need this phone and there's no way I can get another one here I cannot afford to screw it.
Thanks in advance,
F.
Ok, bootloader unlocked and I think I rooted it too.
this is what I've got...
Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00017118
[*] Scooting ...
[*] Sending 149 zerglings ...
[+] Zerglings found a way to enter ! 0x10
[*] Sending 149 zerglings ...
[*] Trying a new path ...
[*] Sending 149 zerglings ...
[*] Trying a new path ...
[*] Sending 149 zerglings ...
[*] Trying a new path ...
[*] Sending 149 zerglings ...
[+] Zerglings caused crash (good news): 0x401219c4 0x0054
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd26051 0xafd39f47
[*] Poping 24 more zerglings
[*] Sending 173 zerglings ...
[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root... enjoy!
C:\Users\Fer\Desktop\phone rooting tools\Zerg rush root>adb wait-for-device
Am I done? Does it means that the whole process it's done? or do I need to do anything else?
Thanks,
Restart your device and install root checker. It should have rooted your phone
Sent from my HTC Amaze 4G using XDA App
Cool! I have it.
Now into more study about which rom or how to remove bloat
Thanks,
Looks like your off to a good start. I find it helpful to iterate what you understand about what you've read. Then let others correct/help you where you're wrong, this helps with the learning process. That is if you want to learn, not just flash the latest rom.
Sent from my HTC_Amaze_4G using XDA App
moved.....
Related
Hello everyone.
I know this topic is listed everywhere in this forum but somehow am getting very confused with what I've read so I hope you guys can help me out here instead.
---
This is my situation.
I'm currently using an O2 Atom Exec with a WM5 OS and I would really LOVE to change it to WM6/WM6.5 (seeing all the Youtube videos having touchflo/HTC & iPhone features) are really interesting.
So I tried downloading several ROMs today and none of them is working on me. I've done all the steps required (copy the 6 files to C:/Windows/Temp and then run the DSUU).
After a few minutes, my mobile will just get disconnected with the PC and it says "No Download Target Found" and the "Connection Error" will appear after.
---
So am just wondering what is wrong because I tried during it for the whole afternoon already and it just won't work. I'm getting frustrated.
Hope you guys can help out with some step-by-step tutorial or a pictorial tutorial will be fantastic. Thanks a lot.
I was attempting to flash the sbf last night and when rsd was finishing up I received a pass on rsd but my phone came up with the error" failed to boot 4 starting RSD mode" . I have reinstalled drivers ,reinstalled rsd lite , tried it on two different computers and used two different cables all with the same result. I also cannot get into any screen other than this on my phone as holding the buttons does nothing but stay on this screen. Anyone know what to do with this error?
gkeller16 said:
I was attempting to flash the sbf last night and when rsd was finishing up I received a pass on rsd but my phone came up with the error" failed to boot 4 starting RSD mode" . I have reinstalled drivers ,reinstalled rsd lite , tried it on two different computers and used two different cables all with the same result. I also cannot get into any screen other than this on my phone as holding the buttons does nothing but stay on this screen. Anyone know what to do with this error?
Click to expand...
Click to collapse
Did you receive the update, then attempt to SBF back to froyo?
I was attempting to sbf to install gingerbread hoping I would catch the ota last night . I was running the Affinity Rom at the time of flashing .Here is the process RSD is going through :
1. Phone (0000) Creating Image File
2. Reboot
3. Phone (0000) Interface AP-OS Flashing code group (group numbers ascending till it gets to group 65
4. Reboot
5. Switching device to BP pass through mode while rebooting
6. Interface BP Flashing Code group 5
7. Reboot
8. Phone is being rebooted (at which point always says Executed 26% then immediate 100 and PASS is on screen, phone still has Failed to Boot 4 Starting RSD mode
I had the same problem all day yesterday and fixed it by uninstalling the moto drivers and rsd lite then reinstalling them. make sure you have the newest version and reboot your computer after they are installed
I did try that several times and still was getting the same error . I posted in another forum and someone had walked me through going the linux route and ended up with still the same error .This is from the command:
>> waiting for phone: Connected.
>> uploading RDL03: 100.0%
-- OK
>> verifying ramloader
-- OK
>> executing ramloader
-- OK
>> waiting for phone: Connected.
>> sending erase
-- OK
>> uploading CG02: 100.0%
-- OK
>> uploading CG03: 100.0%
-- OK
>> uploading CG39: 100.0%
-- OK
>> uploading CG42: 100.0%
-- OK
>> uploading CG47: 100.0%
-- OK
>> uploading CG56: 100.0%
-- OK
>> uploading CG58: 100.0%
-- OK
>> uploading CG59: 100.0%
-- OK
>> uploading CG60: 100.0%
-- OK
>> uploading CG62: 100.0%
-- OK
>> uploading CG65: 100.0%
-- OK
>> rebooting
[email protected]:~/Desktop$ sudo ./sbf_flash VRZ_MB870_DTN-14.8_1FF_01.sbf
SBF FLASH 1.23 (mbm)
Perhaps your SBF file is corrupt? Try re-downloading a fresh SBF.
I tried three sbf files from different sources and still no dice. Ive tried pulling sd card , with it in, two different charged batteries, 3 different cables ,2 different computers , linux and rsd , reinstalled drivers and rsd 5 or 6 times .Nothing is working ,this is so frustrating ,especially since this thing isnt even a month old yet. Im at a loss as to what is wrong .
Still have been trying to flash with all kinds of different methods, anyone have a idea or seen this before?
I'm having the same problem on my Droid X2. I backed up all my media onto sd card and removed before I began any of the sbf flashing process. The phone was running 2.3.4 and i accordingly downloaded the latest 2.3.4 sbf and flashed it. Now I'm where you are, the phone does nothing for 15 - 20 seconds then reads Failed to Boot 4 and Starting RSD mode. I haven't been able to try anything else yet, because my battery is too low, with 3 batteries and a desktop charger en route. Have you had any luck yet?
Quote from OP on anther forum "Just wanted to update this post. I received my new one from Verizon today . However I saw the new sbf that was posted and thought what the hell I will see what happens before I send this other one off and of course it worked . So now I guess ill have to call verizon and act dumb and tell them my old one magically works." So I would say try a different SBF file. Maybe go back to 2.3.3 and then update?
Just a quick question on the occurrence of real bricks with the x2? Anyone ever hear of one or experience one?
Have never seen real bricked x2
I think ur problem was ur battery not charged enough.
This error seems to come up time to time and I've seen it remedied by getting new battery or charging the one u have somehow.
ashclepdia said:
Have never seen real bricked x2
I think ur problem was ur battery not charged enough.
This error seems to come up time to time and I've seen it remedied by getting new battery or charging the one u have somehow.
Click to expand...
Click to collapse
Had the same issue. Battery was fully charged. I can't pinpoint what the cause was.
Sent from my DROID X2 using Tapatalk
Just in case someone has this issue and comes up here like I did, here's what finally worked for me.
I was coming off of 2.3.5 Eclipse 2.2.1, and tried to sbf to 2.3.4. I was stuck through multiple boots, unable to enter any kind of recovery. I finally decided to try a different 2.3 version (went with the 2.3.5 sbf) and it knocked it loose. The world is good again.
I just got my new g2 yesterday.
And I wanted to root it. When I tried the visionary app I pressed on the temproot now and all I get is loading. After the loading screen I get a black screen for the app, but the notification bar is still visible. I don't get root permission from terminal, so I have no idea. I googled the problem, no one seems to have encounted my problem. If they have, they don't get help.
Hello i have the same prb with my device and after more than 5 houres of googling i found the right way to do it.
You must downgrade. it's work 1000% & you have to replace your rom after all.
follow the guide : http://forum.xda-developers.com/showthread.php?t=905003
Bonne chance !
I tried reflashing my atrix with the 1.8.5 update and my atrix is now pretty much bricked. Starting it up now presents a boot error, "Failed to boot (0x1000)", followed by a quick "NVFlash" message then it shuts off. I'd be willing to pay for someone to fix/help me fix it if they think they have the skills necessary. (If it's cheaper than buying a new atrix.)
Anyone have any help?
Thanks.
There is no fix for this
sent from cm7 atrix 1.3ghz
For what it's worth, motorola has informed me that they offer a repair service for $110 + tax.
hesif said:
For what it's worth, motorola has informed me that they offer a repair service for $110 + tax.
Click to expand...
Click to collapse
Sounds like moto caught on to what's been happening. I wonder if they send a refurb or actually fix "your" device for the $110? Another poster in the HARD BRICK WARNING thread said Moto had no idea what this problem (your problem with the NVFlash and all) is or how to fix it. The poster then went on to say Moto sent him a refurb as his was not fixable. May contact him and get more info.
Either way, you took the risk and didnt read all the warnings. Sucks to say it, but you will have to pay to play. Welcome to voiding warranties . On another note, $110 isnt that bad of a deal considering its a $500 phone and hell my insurance deductible is that ($110) alone so I think you're possibly coming out on top here.
Yeah. I really don't mind spending up to ~$100. Purchasing an out-of-contract Atrix brand new would suck much worse.
if u haven't got someone to unbrick your device yet, mobiletechvideos met be able to help you. they do jtag unbrick fixes, which is a hard brick. I would go to his website and shoot him an email explaining your situation. He only charges $40.
i got same problem .just bought this atrix 4 days ago..
Can anybody help?
Please help!
I was using the sbf (post 22) and instructions (post 27) from the "Gingerbread on Telstra yet?" thread on Atrix Forums on my Telstra stock Atrix:
And it was all going well until I got:
"phone 0000 switching device to bp pass through mode"
That fails and I get:
"Failed flashing process interface ap-os error flashing subscriber unit device api error 0xE003003F address 0x12000150 command addr 0xE023203f phone connected"
It shows the logo while booting and freezes at "Failed to boot 4 Starting RSD mode"
I can still get connected through RSD-lite but I don't know how to proceed
I have tried it 3 times, same result.
I put pudding intl-fix-try1.sbf on there and that seems to work but still fails to boot but now the device just powers off when I try to put it into fastboot mode.
Thanks for looking.
Richard
---------- Post added at 04:00 PM ---------- Previous post was at 03:01 PM ----------
Fixed using sbf flash on my mac, phew!
> Fixed using sbf flash on my mac, phew!
hi, may I know which file you flashed to fix it ?
I got same error msg as you
Thanks so much
First things first, DO NOT POST UNLESS YOU KNOW WHAT YOU ARE TALKING ABOUT!
Sorry, but telling me simply stupid responses will only annoy others who may be in the same situation while they are reading this and it will annoy me as well.
So this brick is highly complex and I hope someone knows what to do here. I have NvFlash enabled with the blob.bin, followed the guide here and check out this thread as it is highly similar to mine in the beginning. I see flumpster seems to know quite a bit, I hope he is still active on forums . So if I do the normal wheelie --blob.bin, it stops at
Code:
[+] Sending bootloader...
If I do the wheelie -r --blob blob.bin
Code:
Sending file: 100 %
Although this time the pad goes to the "Eee Pad" screen with the "Entering NvFlash recovery mode . Nv3p Server". and the chip uid.
I've tried two different computer both running Windows 7 64-bit and one of those also booted into its main operating system Ubuntu 12.10 64-bit. All with the exact same results. Terminating wheelie in with "-r" results in NvFlash just hanging at "[Resume Mode]" if I try to continue the process of unbricking. Before all this I used option 1b in this guide after a bootloop started after my tab crashed while playing a game. I hope someone can help me
Anyone know what to do, I don't want my thread to disappear into oblivion
It's been so long and not a single reply . I'm just going to weekly bump this and hope that at least one person knows what to do. :fingers-crossed:
I'm just gonna bump again in hopes that someone on this forum can help.
Suggest you start your post again with a better sentiment, It's pretty obvious why you have had no replies. Ask a mod to close this one and try to start your new one with a nicer tone
sbdags said:
Suggest you start your post again with a better sentiment, It's pretty obvious why you have had no replies. Ask a mod to close this one and try to start your new one with a nicer tone
Click to expand...
Click to collapse
Looking back at my OP I now realize that it did seem a bit mean although looking at other threads they often get flooded with obvious things. Sadly my brick needs someone who is a complex understanding of wheelie and nvflash. I think I'm going to try and get in contact with the AndroidRoot team.