Related
Ok, so I tried to flash my G4 wizard to wm6, went all the way through the flash, got to 99% and stopped, giving me a comm error. I did the recovery and im in an endless flash to 99% loop. When I turn it on, I get the bootloader (3 stripe) screen, with the following:
RUU upper right corner
IPL 2.25.0001
SPL 2.25.0001
USB lower left corner.
I have spent the last 4 hours reading posts and cannot fix this thing. Any help would be greatly appreciated.
did u flash it back to carrier rom?
Flash it back to the original carrier ROM (should be available on the website) and then use ShellTool to flash the ROM. make sure that you follow the instructions exactly, otherwise, you will end up with a bricked rom.
-Nstefanelli-
The only rom I can find on Cingular's web site, once downloaded says its corupted, and I cant find one on XDA at all. Anybody know where else I might find one?
Wizard Love rom is another one you could try.
Wizard Love got me goin again, I love me some wizard.
Thanks for the help guys!!!
Same Problem I Have Faced.... And Also Solved.
u have Radio Rom problem....
search the latest radio rom and upload to your rom... and restart your pda...
reply me..... sooon because same problem i had faced and solved also.
Same problem
I was having the same problem yesterday. Eventually i got it to work again. It was a little confusing though because i used the rom from the HTC website to get it up and running again with wm5 and then used ShellTool from the sticky in this forum to flash it with a wm6 rom. From what i gather it's because my phone was CID locked, something that none of the roms include in their instructions to watch out for. Maybe a sticky in the forum for newbs like me containing things to watch out for while flashing roms?
A side note:
I had to download the rom from the HTC site twice in order for it to flash back to the original OS. The first time i downloaded the rom i kept getting an error. I guess it was a bad download or something but the second one worked in the first shot.
think i bricked my wizard
oops !!!!
think i flashed a g3 rom onto my g4 wizard and for a while it stayed in bootloader screen (tricolour) now the wizard is dead with no charging light when plugged in and performing hard reset does nothing
please help !!!!!!!!!!!!!!!!!!!!!!
gripper said:
oops !!!!
think i flashed a g3 rom onto my g4 wizard and for a while it stayed in bootloader screen (tricolour) now the wizard is dead with no charging light when plugged in and performing hard reset does nothing
please help !!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
There is no help for you if you did flash a non-official G3 rom onto your phone.
Recent Official carrier releases are the only roms that contain bootloaders that are safe to flash into a G4. (Note older carrier releases could possibly fry your phone as well as they may not contain G4 bootloaders)
If you flashed a custom rom with IPL/SPL your device is done for good.
Though you said it went to the bootloader prior to going dark so you may just have a dead battery and a bad flash. Get a battery from a friend or buy one and then see if the device will power on. If you can't get it to power on with a known good battery then it is most likely fried. If it does boot at least to bootloader then you should be able to recover your device. Most chargers will not charge the battery of your phone unless the phone is fully booted into windows. So it is very important to have a contingency plan in case of a bad flash with these phones as playing/troubleshooting while trying to recover from a bad flash will drain your battery possibly leaving you with not enough juice to complete a flash.
hi zzan
thanks for the reply, i think your right about the battery it actually turns on for about 10 seconds now into bootloader but then the battery dies again so i gonna source a battery.
gripper said:
oops !!!!
think i flashed a g3 rom onto my g4 wizard and for a while it stayed in bootloader screen (tricolour) now the wizard is dead with no charging light when plugged in and performing hard reset does nothing
please help !!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
Remove the battery for about 5 minutes, then put it back in.. then try booting in bootloader mode <tri color screen> .. then flash with an OFFICIAL Carrier ROM ..
I flashed my hermes yesterday <changing the spl and stuff> and it was dead for a little bit, until I took the battery out and put it back in.. <for some reason it was like a de-fibrilator..>
Try that.
hi madcap,
not looking good i toook it to a phone engineer and he says it is corrupt ? he has tried flashing it, apparently there is a guy who will put in a new chip ? i am such a fool i bricked my phone just to get rid of o2 stuff !!!!!
gripper said:
hi madcap,
not looking good i toook it to a phone engineer and he says it is corrupt ? he has tried flashing it, apparently there is a guy who will put in a new chip ? i am such a fool i bricked my phone just to get rid of o2 stuff !!!!!
Click to expand...
Click to collapse
A new chip?!?!??
The problem is the in the IPL area which can now be flashed only via JTAG (cable system that doesn't require booting files since it operates directly on the chip)
Take it to an official repair.
Hi,
I have almost the same problem. I tried to flash to WM6.1 for wizzard, it got to 99% and failed (connection lost). I then tried the recovery process but that didnt work.
Now I can boot to the booloader, and see the IPL/SPL versions (2.25.0001) and can see USB on the lower left. But , it is not making a connection to my PC. None of the RUU, ROMS, HardSPL, or SoftSPL apps can connect to it.
They all report some connection error, "Device not found", or "Connection Error 264"...
I have read a bunch on this forum, and tried alot of stuff but nothing worked.
I started up my own thread on my issue, but hope someone could help me, help someone else in the process here..
How can I get this thing flashable again?
Thanks
Madcap180 said:
Remove the battery for about 5 minutes, then put it back in.. then try booting in bootloader mode <tri color screen> .. then flash with an OFFICIAL Carrier ROM ..
I flashed my hermes yesterday <changing the spl and stuff> and it was dead for a little bit, until I took the battery out and put it back in.. <for some reason it was like a de-fibrilator..>
Try that.
Click to expand...
Click to collapse
This worked for me and now I can connect the apps to the phone again. But after I try to install the default rom, everytime at 80% it looses the connection again.. .
Anyone know a good WM6.1 rom that works with 8125 G4
end123 said:
This worked for me and now I can connect the apps to the phone again. But after I try to install the default rom, everytime at 80% it looses the connection again.. .
Anyone know a good WM6.1 rom that works with 8125 G4
Click to expand...
Click to collapse
Fully recharge your battery, then try to flash again. Low/dead/misreporting battery will kill a flash as surely as disconnecting the cable in mid-flash. Oh, and try WizFlo...really cool! (I had to fiddle with the Opera Browser install to get the Internet connection to work correctly, but who cares, it was worth it!)
I have this HTC HD2 and after i flashed a stock Rom and updated my rom again this occurred. Every time I turn on the Phone I am stuck at the Boot loader screen and I have no way to reverse it. My SPL states that I am on 3.03 but there are certain numbers missing from the top of the screen. I have tried to flash the Rom many times after and every time it reaches 2% the phone restarts and i get invalid Vendor ID, please see the screenshot. Thanks
my most important question is if the Phone is bricked and nothing can be done
Could have been a bad flash indeed.
But, the good news is that in most cases, as long as you get into the bootloader, you can get in working again.
"Invalid vendor ID" means that the ROM you tried to flash was not made for your HD2. In case you have a branded device, you must flash the ROM which was made for your operator, if it´s a free device, you must flash an HTC ROM.
You now need to find the proper ROM for your device and flash it through the SD card method, this will re-flash SPL as well.
im afraid this issue has come up a few times (only 2 or 3 that ive noticed) and is not fixable. there are a couple of threads where people have posted pics of bootloaders with those missing/strange characters and it seems to be unfixable and occur for an unknown reason..... sorry.
jtag may resolve the issue if your able to find a way having it done
conantroutman said:
im afraid this issue has come up a few times (only 2 or 3 that ive noticed) and is not fixable. there are a couple of threads where people have posted pics of bootloaders with those missing/strange characters and it seems to be unfixable and occur for an unknown reason..... sorry.
jtag may resolve the issue if your able to find a way having it done
Click to expand...
Click to collapse
In another thread, a few other users succeeded with this:
1. Took out the battery for about 30 seconds.
2. Put one of the LEOIMG.NBH on storage card
3. After putting the battery held the volume down button and pressed power button.
4. It went into HSPL mode straight away and started loading the win 6.5 OS.
Click to expand...
Click to collapse
But only with some other previously unseen data in the bootloader...
Maybe this still helps here.
tictac0566 said:
In another thread, a few other users succeeded with this:
But only with some other previously unseen data in the bootloader...
Maybe this still helps here.
Click to expand...
Click to collapse
good find! I didn't see that one, hope it works.
thanks for the info. will update you as soon as I try all those methods. the only thing is i believe that i haven't try the SD card method will update.
I don't know where to begin so I'll just list the problems I have been encountering why trying to flash a stock ROM into my TMO HD2.
Preloaded with Android Gingerbread 2.3+HSPL 2.08+Magldr 1.11
Stuck at 123456 Go Go Go
Digitizer cracked & removed
Tried flashing stock TMO 3.14 ROM to ascertain if it is lack of digitizer causing problem
Was able to perform Task 29 normally initially
Could not run 3.14 RUU successfully nor via SD card method with HSPL 2.08 intact. RUU stuck at 8% & SD method stuck at Radio forever
Upgraded HSPL to 3.03 successfully using HSPL 4
Still could not run 3.14 RUU; same as above
Rolled back to SPL 2.08.000 using HSPL 4
Started having problems with Task 29; could not complete properly
Tried MTTY (v.1.42) but could not format NAND
Upgraded to HSPL 2.08 using HSPL3
Still could not perform Task 29 successfully. Sometimes successful & other times not. Mostly met with limited success using SD card method & CustomRUU Task 29 met with numerous connection error (262, 266, 284)
.....
Now, managed to roll back to HSPL 2.08 after redoing SPL 2.08.0000 even though 'We hacked it' screen stayed on with HSPL3 tool 'Critical error'
Trying to flash stock 3.14 RUU met with Error 284
Tried flashing from SD card, screen displayed 'Loading...' perpetually
After pulling battery for about 10 mins, powering up to 'Stick Together' splash screen without any red letters
Now when trying to flash using RUU, it would fail with Error 284/266 & the driver would spontaneously change from HTC USB Sync to Qualcomm Diagnostic Interface 3197 (COM17)??!!
Question:
I think my phone is not bricked but can it be salvaged?
Will the lack of a digitizer prevent it from being flashed?
Can it be salvaged with JTAG?
I cannot charge the battery in the phone now even with power off. Would the remaining battery power prevent or negatively influence the flashing?
Anyone who have met with success in recovering from something like this...or anyone who has dealt with similar symptoms, please advise me what to do from here.
I really need help.
Thanks!
Konker
RUU stuck at 8% & SD method stuck at Radio forever
Click to expand...
Click to collapse
Stuck radio, not a good sign,, (often sticks at 9% too, anything from 7 to 10 is usually the radio)
Can it be salvaged with JTAG?
Click to expand...
Click to collapse
probably your only option, though I would guess at a hardware issue, bad nand blocks, or similar with a ll the varied errors.
You could also try chilling teh phone in eth fridge, in a sealed bag for half an hour, with teh sd card ready to flash stock rom straight away, , if this is sucessfull, then you have thermal issues.
samsamuel said:
Stuck radio, not a good sign,, (often sticks at 9% too, anything from 7 to 10 is usually the radio)
probably your only option, though I would guess at a hardware issue, bad nand blocks, or similar with a ll the varied errors.
You could also try chilling teh phone in eth fridge, in a sealed bag for half an hour, with teh sd card ready to flash stock rom straight away, , if this is sucessfull, then you have thermal issues.
Click to expand...
Click to collapse
Thanks for the response!
Am I suppose to see the R... at the bottom of the splash screen if the radio is working normally despite having completed Task 29?
I know the OS is wiped but the radio is still there....I think.
Does JTAG restore the radio?
The phone does not get anywhere near hot or very warm when I'm doing all these steps so will putting it in the freezer make a difference? I was under the impression that this works when the device has been exposed to heat or is hot for an extended period of time.
Task 29 doesnt touch the radio, only the rom. You may be able to flash cooked roms, and maybe magldr, just not anything with a radio included. Fridge probbly won't help if you're happy that it isn't heat related.
samsamuel said:
Task 29 doesnt touch the radio, only the rom. You may be able to flash cooked roms, and maybe magldr, just not anything with a radio included. Fridge probbly won't help if you're happy that it isn't heat related.
Click to expand...
Click to collapse
I'm not seeing the R... at the bottom of the splash screen now so does that mean that my radio is fried?
Also, can you comment if not having a digitizer installed would prevent WM6.5 from flashing properly? I've read in the Android thread that it will prevent Android from booting, which is why I decided to flash a WM ROM first to ascertain the hardware condition.
I'll give the 'cold treatment' a try & see how it goes & am in the process of downloading a custom ROM to try. The current HSPL is 2.08 but I'm not sure if it is working properly since the last HSPL attempt ended with the 'We hacked it' stuck on the screen without a reboot & a critical error for the HSPL tool.
Lastly, any idea why it would switch from standard driver to diagnostics driver? It's weird & I can't explain it.
konker said:
i'm not seeing the r... at the bottom of the splash screen now so does that mean that my radio is fried?
Samsamuel... it's a bad sign, but there are situations where that info doesn't show, however combined with it sticking at 8%, which is about when the radio gets flashed.....
Also, can you comment if not having a digitizer installed would prevent wm6.5 from flashing properly? I've read in the android thread that it will prevent android from booting, which is why i decided to flash a wm rom first to ascertain the hardware condition.
Samsamuel........ No, people have flashed successfully with broken digitizers, shouldn't affect winmo, up until it requires input after initial boot.
I'll give the 'cold treatment' a try & see how it goes & am in the process of downloading a custom rom to try. The current hspl is 2.08 but i'm not sure if it is working properly since the last hspl attempt ended with the 'we hacked it' stuck on the screen without a reboot & a critical error for the hspl tool.
Samsamuel....... Id try a different pc if at all posible, though i have had to pull battery myself at the hacked it screen, (not even sure it does reboot itself, from memory, hehe)
lastly, any idea why it would switch from standard driver to diagnostics driver? It's weird & i can't explain it.
Click to expand...
Click to collapse
that's worrying, too, because that's what happens when tmous gets radio bricked,,,phone becomes utterly unresponsive and pc searches for qualomm diagnostic drivers.
I too in similar situation. I can't get NAND android to boot up get stuck on 123456 GO GO GO! Try flashing the stock rom and get stuck on 8% Task 29 still work for me. If I flash Task29 you think I'm able to flash a custom rom that doesn't touch the radio? The only problem is that i was able to flash the radio with no problem.
itzstevo said:
I too in similar situation. I can't get NAND android to boot up get stuck on 123456 GO GO GO! Try flashing the stock rom and get stuck on 8% Task 29 still work for me. If I flash Task29 you think I'm able to flash a custom rom that doesn't touch the radio? The only problem is that i was able to flash the radio with no problem.
Click to expand...
Click to collapse
Do you still have magldr on the phone?
If not, do you see the R...when the default splash screen shows up after powering up the phone?
If not, you might be in a similar situation as me.
I cannot ascertain if my radio is really bricked as there's no way to see or detect that & as samsamuel indicated, having the PC detect a diagnostic port might suggest that my radio is bricked.
I did try to flash a compatible radio to my phone but it failed everytime.
Magldr is still on the phone. I am able to flash new radio with no problem. are you able to flash just a rom and not a a rom & radio?
samsamuel said:
Stuck radio, not a good sign,, (often sticks at 9% too, anything from 7 to 10 is usually the radio)
probably your only option, though I would guess at a hardware issue, bad nand blocks, or similar with a ll the varied errors.
You could also try chilling teh phone in eth fridge, in a sealed bag for half an hour, with teh sd card ready to flash stock rom straight away, , if this is sucessfull, then you have thermal issues.
Click to expand...
Click to collapse
yes you are right my bro ... had same problem ... after cooling phone in fridge for 5-10 min it will go perfect BUT still it wouldnt boot into winm so i decided to try android in nand , flashing went ok but after that it wouldnt boot Fatal hit ( magdlr) so i put phone in fridge again for 5-10 min and Yes it booted in android - tried same with WP7 ... But after using a while it will get hot and will stock or restart
konker said:
[*]Can it be salvaged with JTAG?
Click to expand...
Click to collapse
No my bro... jtag only writes boot - repair files
itzstevo said:
Magldr is still on the phone. I am able to flash new radio with no problem. are you able to flash just a rom and not a a rom & radio?
Click to expand...
Click to collapse
I think your HD2 is in a lot better shape than mine.
At least you can flash your radio...I can't flash either ROM or radio.
But I suspect your problems might be due to corrupted NAND.
Have you tried Task 29 with mtty?
At least you can see error messages with mtty when doing Task 29.
ubejd said:
yes you are right my bro ... had same problem ... after cooling phone in fridge for 5-10 min it will go perfect BUT still it wouldnt boot into winm so i decided to try android in nand , flashing went ok but after that it wouldnt boot Fatal hit ( magdlr) so i put phone in fridge again for 5-10 min and Yes it booted in android - tried same with WP7 ... But after using a while it will get hot and will stock or restart
Click to expand...
Click to collapse
ubejd, you gave your HD2 the 'cold treatment' after it turned warm & refused to boot or rebooted automatically am I right?
Would it do my HD2 any good to put it in the freezer when it is cool as room temperature? It has been sitting there unplugged & unpowered for at least 8 hours. I have not tried the 'cold treatment' but flashing custom ROMs with HSPL 2.08 also failed.
Seems like a combination of radio brick & NAND failure...
konker said:
ubejd, you gave your HD2 the 'cold treatment' after it turned warm & refused to boot or rebooted automatically am I right?
Would it do my HD2 any good to put it in the freezer when it is cool as room temperature? It has been sitting there unplugged & unpowered for at least 8 hours. I have not tried the 'cold treatment' but flashing custom ROMs with HSPL 2.08 also failed.
Seems like a combination of radio brick & NAND failure...
Click to expand...
Click to collapse
yes you are right my Bro
you can try, it wouldnt do any harm but just put in isolated place - bag before putting in the fridge - to keep safe phone from getting wet and dont let more then 5-10 min maximum... but as i told it will not boot again in win mob - i hope it does but i doubt ... if it fails to boot than consider to go with android or winp7
i have one question how it began to act like this... did it fall or you bought like that
i hope you success
best regards from me
Gave it a go with the freezer test. I was surprise that i was able to boot up into CWM, & load up Android. Now I can only use the phone for maybe 20 min or so before it get hot again and I have to put it back in the freezer. Is there a way to tell which HD2 is bad batch?
I first one had no problem beside the bad screen, my 2nd HD2 is having heating issues. Seem like I can't win.
itzstevo said:
Gave it a go with the freezer test. I was surprise that i was able to boot up into CWM, & load up Android. Now I can only use the phone for maybe 20 min or so before it get hot again and I have to put it back in the freezer. Is there a way to tell which HD2 is bad batch?
I first one had no problem beside the bad screen, my 2nd HD2 is having heating issues. Seem like I can't win.
Click to expand...
Click to collapse
I gave my HD2 the 'cold treatment' & I was mildly surprised that it reached the 2/3 mark when using the SD card method to flash a custom ROM but that was it. Back to square 1...
itzstevo said:
I first one had no problem beside the bad screen, my 2nd HD2 is having heating issues. Seem like I can't win.
Click to expand...
Click to collapse
if you have both of them take motherboard from the one who has bad screen and put in one who has heating issues this way you will have at last one working hd2...
I had the same problem too. I knew I wasn't the only one with this problem.
Now I'm sure, MAGLDR makes the NAND corrupted (over 8%). My phone won't charge too, gets stuck at 8%, get stuck on splash screen and doesn't show any red lines...
PasSlert said:
I had the same problem too. I knew I wasn't the only one with this problem.
Now I'm sure, MAGLDR makes the NAND corrupted (over 8%). My phone won't charge too, gets stuck at 8%, get stuck on splash screen and doesn't show any red lines...
Click to expand...
Click to collapse
Flash failing at 8/9% has been happening long before magldr, , and seems to be connected to the radio being corrupted.
But I can flash a radio via RUU... if my radio were corrupted, flashing a radio should not be possible. Am I right ?
With RUU : I'm stuck about 1 minute on 8% then the process resume up to 100% without any error, but whatever the ROM I flash, no one reach splash screen.
With SD : No problem.
Like the OP, my phone is acting weird when I plug on charge.
With cable to PC : autoboot (MAGLDR 1.13 issue)
With cable to AC : red led but when I plug off the cable, the red led is still on (until I remove the battery).
It's clear that in any way, MAGLDR is not completly removed of my HD2 (yeah, I flashed some stock ROM with SD card).
I think I'll send it to repair, I'll leave feedback if I send it.
Hi, I believe my MoPho is bricked and was just trying to see if there were any recovery methods so that I would not have to send it off and lose files I had stored on my internal SD card. My problems started after I left my phone on the charger. I came back to see that it was stuck on the bootloader screen and wouldn't go any further. I was running j0kersax's MIUI ICS build and hadn't had any trouble with the rom prior to this. I've tried entering fastboot, rsd, and android recovery through the vol down+power method, but when I do it always freezes; either while I am scrolling the menus or waiting for it to boot into one of the aforementioned modes. At one point I was able to get to fastboot, but when I attempted to enter it, an error message came up saying something like "the battery is too low to flash", so I attempted to charge it. However whenever I plug it into the A/C adapter it simply starts up and stays on the boot loader. So is it possible to recover or is my photon a vegetable now?
Maybe you should SPF back to stock. You can find the release keys anywhere. This video is helpful: :victory:
http://www.youtube.com/watch?v=J94VcWk-CJc
I_MayBeSmall said:
Maybe you should SPF back to stock. You can find the release keys anywhere. This video is helpful: :victory:
http://www.youtube.com/watch?v=J94VcWk-CJc
Click to expand...
Click to collapse
thanks for the suggestion, but I can't even get the battery to charge so that I can even attempt to do this. I've accepted the brick and I'm just going to go to Best Buy and order a replacement. Thanks again.
I have the exact same problem as OP. Right now, my battery is dead, so I can't flash anything to help fix my problem. My theory on how to get this working again is to charge the battery or borrow someone elses battery so there's enough charge.
Anybody think that'll work?
nikalus said:
I have the exact same problem as OP. Right now, my battery is dead, so I can't flash anything to help fix my problem. My theory on how to get this working again is to charge the battery or borrow someone elses battery so there's enough charge.
Anybody think that'll work?
Click to expand...
Click to collapse
I've tried a battery swap and now it won't even power on. I've yet to order a replacement, so for now I'm on an Evo.
I am kind of having the same issue I tried to flash CM10 just a few moments ago and it wont flash!?
I have flashed CM7 to my Electrify before and was trying to flash over that. Now my battery is dead, I can't boot the phone at all.
What do I do!
My phone is bricked!
I unlocked using this guide
m.youtube.com/#/watch?v=S6a0BWquqAc&desktop_uri=%2Fwatch%3Fv%3DS6a0BWquqAc
Which is same as
http://forum.xda-developers.com/showthread.php?t=1182871
Using this auto unlocker
http://j.mp/Ate8E5
and I also installed cwa from there
I then installed this rom on my phone and my Phone is now bricked! I can get into recovery and fast boot and all that but the problem now is that the battery is low and Apparently the phone doesn't charge while in recovery mode !?!?!??'. I know for a fact my battery is fine so that is not the issue. When plugged into wall I can turn the phone on but it won't go past the Motorola logo, I can make it go into recovery but as soon as I unplug it, it turns off. When I plug it into laptop it does not turn on so apparently the battery is not charging in this state? If anyone can help me I would really appreciate and would reward some how
Thanks
quetzalcoatl2435 said:
That's a softbrick. You could try flashing another ROM while plugged in to a charger, or you could charge your battery first with an external charger...
Click to expand...
Click to collapse
I can't flash another rom because the battery is so dead that it doesn't turn on when plugged into laptop
I can't charge my battery because apparently the battery doesn't charge while in android recovery or on boot logo, and I can't leave the phone off because when ever I plug it in it turns on automatically and gets stuck at he boot logo or goes to recovery if I hold the buttons down. I know for a fact my battery and charger and charging port are perfectly fine because they were working this morning before I started this whole mess that I have been trying to fix for the last 11 hours.... Please help
quetzalcoatl2435 said:
You have to charge your battery first. Either with an external charger, another Atrix phone, or a jumper USB cable. The most important thing is that you said it still boots to recovery/fastboot. That means that it's not a hardbrick. Now you have to get the battery charged and flash another ROM (don't use RSD, just try CM9/MROM/Nottach or something else).
Click to expand...
Click to collapse
- I don't have another atrix or external charger does android really not allow it to be charged at the boot logo or in recovery? Is there any bypass to allow a charge?
- is there really no other fix for this? You might as well consider this a hard brick
quetzalcoatl2435 said:
- When you plug it in when off, does a battery icon show up? It flickers for a while and then goes blank but it does charge. The kernel does allow charging in recovery/off mode, but from what you've said, you got a bad flash. (Maybe the zip file was corrupt?)
- I haven't seen anyone getting a brick from this ROM per se. There might be some softbricks caused by bad flashes from corrupted zips (or compatibility problems), but as I said those are easily fixed by flashing the proper zip/another ROM, so there are no reasons to pull this release. Besides, this ROM came with a clear warning/disclaimer.
Assuming your phone still goes to recovery/fastboot, the boot.img flashed properly, so try point one above. There's no visual feedback for the charging process (still in the works), so you'll have to leave it plugged in for a while and try again later.
Above all, don't panic. Panicking cause reckless behaviour, reckless behaviour will make things worse.
Click to expand...
Click to collapse
No the battery logo never shows up,if I plug it in to pc a bright green light comes and the screen never turns on but it is not charging because I left like this for hours and the battery is still dead. If I plug it into a wall outlet the boot logo comes up and I can go into recovery. But still not charging
On a side note I have been looking for pc apps that will increase the USB power to trick my phone into thinking its plugged into a wall outlet "if that's what the issue is. Unfortunately I haven't been able to find any
On another side note I'm wondering if I can use a memory card reader to put a stock rom on a micro sd card and flash my phone while it's plugged into a wall outlet through the micro sd card, unless you think the issue is the bootloader and then I ask you two questions. What makes you think it's the bootloade?r and is there any way to fix the bootloader from a Micro sd card or any other fix u can think of?
There is absolutely no charging being done, in pc always off but green light on, in outlet always on won't stay off but doesn't go past boot logo.
Also would like to add that I don't get that "failed to boot" message that is talked about in the other threads so this is a different type of brick
quetzalcoatl2435 said:
I was just about to suggest that. If you can get into recovery, copy the new ROM on your sd card and flash while plugged in.
That should work.
But no stock ROMs, you need RSD to flash those sbf files, and you risk bricking your phone for real. Just download nottachtrix if you want a stock experience.
Click to expand...
Click to collapse
But if the issue is the bootloader then can I do anything?
Can you link me some known working roms that you would suggest?
quetzalcoatl2435 said:
The recovery you can boot into, is that CWM or stock recovery? Does the phone show "Unlocked" in the top left corner on the red Motorola logo?
Click to expand...
Click to collapse
Yes it displays unlocked on the top left corner and the recovery came with the auto unlocker script.
It's called Atrix 4g recovery v4.0.0.2 GOAPK.COM
I got the auto unlocker from here
http://j.mp/Ate8E5
http://www.youtube.com/watch?v=S6a0BWquqAc
quetzalcoatl2435 said:
There's your problem. Use romracer's recovery (cwm). Others have compatibility problems with flashing zip files.
Click to expand...
Click to collapse
While the battery was still alive I tried two different versions of cwm and I also tried team wins recovery And flashed cm10 with all of them and has same issue
quetzalcoatl2435 said:
Stick with cwm and try another ROM, preferably one based on the old GB kernel. Your phone might be incompatible with this (unfinished) kernel. It's a work in progress, so it's kinda expected. There are a few other people reporting that their phone is unable to boot with this kernel.
Click to expand...
Click to collapse
Can u suggest me a rom?
quetzalcoatl2435 said:
Stick with cwm and try another ROM, preferably one based on the old GB kernel. Your phone might be incompatible with this (unfinished) kernel. It's a work in progress, so it's kinda expected. There are a few other people reporting that their phone is unable to boot with this kernel.
Click to expand...
Click to collapse
I can't get cwm on there now,, fastboot always says not enough battery.....
quetzalcoatl2435 said:
Try flashing another ROM first. Neutrino CM7 is the smallest, so you can start there.
Click to expand...
Click to collapse
Ok don't have a memory card reader so gonna get a hold of one and will try later today thanks for the help!
---------- Post added at 02:14 PM ---------- Previous post was at 01:50 PM ----------
Also want to add that sometimes I get an error trying to mount /system from recovery, if that means anything
Who deleted all my posts?
I have a nasty issue with a hard brick which I was explaining in well detail, I had over 20 posts and was conversations with another user, where did all my posts go?!?!?!?!?! either that rom or that unlocker bricked me, someone is trying to cover it up?
http://forum.xda-developers.com/showthread.php?p=41771830#post41771830
dk00 said:
I have a nasty issue with a hard brick which I was explaining in well detail, I had over 20 posts and was conversations with another user, where did all my posts go?!?!?!?!?! either that rom or that unlocker bricked me, someone is trying to cover it up?
http://forum.xda-developers.com/showthread.php?p=41771830#post41771830
Click to expand...
Click to collapse
this will also be deleted as you posted in the wrong section !!
aaki_rocker said:
this will also be deleted as you posted in the wrong section !!
Click to expand...
Click to collapse
I posted the issue in that thread 6 hours ago
http://forum.xda-developers.com/showthread.php?p=41771830#post41771830
The thread is in this forum which is why i posted it here and someone deleted all of my posts , why?
This release bricked me who deleted all of my posts!?!?!?
Your posts were HEAVILY off-topic for that thread, and for the development section in general. I suggested that your posts be moved to a separate thread in the appropriate section, but i guess the mods decided to delete them instead. You should have just opened a separate thread in the Q&A section yourself, would have saved some trouble.
This thread will likely be deleted very soon too as it doesn't belong here.
ravilov said:
Your posts were HEAVILY off-topic for that thread, and for the development section in general. I suggested that your posts be moved to a separate thread in the appropriate section, but i guess the mods decided to delete them instead. You should have just opened a separate thread in the Q&A section yourself, would have saved some trouble.
This thread will likely be deleted very soon too as it doesn't belong here.
Click to expand...
Click to collapse
MayBe you haven't read a word I have said thus far, but that rom caused a hard brick on my phone, I am there fore explaining my issues in the thread so the debs know about it, don't you think you are being a bit anal there?
dk00 said:
I have a nasty issue with a hard brick which I was explaining in well detail, I had over 20 posts and was conversations with another user, where did all my posts go?!?!?!?!?! either that rom or that unlocker bricked me, someone is trying to cover it up?
http://forum.xda-developers.com/showthread.php?p=41771830#post41771830
Click to expand...
Click to collapse
@dk00
Your issue is that you posted for help in a development Thread.
The other issue is that you did not search.
With just a fast look at the general section I found THIS THREAD TO HELP YOU.
I have copied you post to this thread , for your reference.
Please continue your discussion in the help thread.
Thread moved & closed