So i became a hacker (Obvoiusly) and ive had some issues but i always find a way to fix them and im glad i became a hacker ! <3 but alas i have problems once more :'/. See i was using cm7 BATF2 Or something along those lines, and ive had multiple problems but kept it due to lazyness of backing up and restoring my phone. but now it seems my phone keeps bootlooping unless i flash a new rom, so i flashed cm9 0.3.1. Sure i lost everything but i need a phone and quickly </3 :/.
But there seems to be a problem.....
Whenever i try to use cwm recovery (Button only 5.0.2.8 i believe) i cant factory restore because it cant reach a certain part of android (If im right its android secure.) and skips the format.
So i have literally no space on my phone.
Can someone help me with this and maybe some other issues??
Thanks in advance
-heyhey24 <3
This may work for you:
reboot to recovery
wipe dalvik
wipe cache
reboot to fastboot
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot reboot (to recovery)
flash ROM
Related
Hi,
I seem to be bricked more than usual. Don't ask me how, I was doing something, rebooted and now I can't get into early usb mode or android recovery. I have no clue what half the other boot options are.
I can use rsd lite to flash sbfs, no problem. Phone is stuck at initial m, no animation. I suspect it is something dumb like the internal memory having an error, something is causing the linux bit to loop. Not reboot, not crash, just hang there.
i can use fastboot, but since it uses names for partitions, I don't know how to flash exact partitions or know what they all are, I have system, webtop, boot, recovery, cdrom, other things like pds are not allowed.
I have a dev usb cable made up, can do everything without a battery, which is cool, have an extra battery and external battery charger. Obviously, I have all the partitions available as backups.
Somehow, I need to get the partitions restored, and internal memory formatted perhaps.
Any ideas? Short of trying to send it back?
Thanks.
for my little experience a full wiped pds let you run the os...and you know better than me which are the others partitions not overwritten by a flash with full sbf
I had a backup of my pds, but no way to flash it or erase it.
Thanks!
in milestone i was having your problem when changing builds (froyo,ginger, eclair) via update.zip without the correct boot.img
but if you already flashed the sbf...
have you tried flashing boot and recovery partition, and then entering it? maybe you regain adb access
I think I am getting blocked before I even get to recovery, early usb, android recovery, etc.
I have fastboot access and nvflash, so in other words I have fastboot.
I can flash boot, recovery, system, webtop, cdt, cdrom, preinstall, but not pds, and I can't erase boot etc.
Thanks.
...i searched for nvram in android:
maybe it's useful (from droid incredible dev area)
dknlght said:
I finally successfully recovered my BootLooped Incredible after i incorrectly updated the NV item of my phone. My situation was a little different than most bootloop error because no matter which stock rom or recovery image I flash nothing would stop it from rebooting because the NV items weren't overwritten during the flash. Then I came across a solution for the EVO by cutthroatamft on how he recovered his EVO from the same Mistake but unfortunately all his files were geared toward the EVO. After much searching I accidentally came across a single comment that posted a link for the ENG-HBOOT for the incredible. Now i manage to replace all the EVO specific files with the Dinc equivalent. Below is the link to the files and instructions compile by cutthroatamft but I updated it for the Dinc. Hopefully this helps someone else that has this problem. can't post a live link but I think you can figure it out
www megaupload . com /?d=RCZBCDDA
Click to expand...
Click to collapse
hope it helps somehow
Well, the file is about HTC phones, so it doesn't really apply, no hboot to swap to get a fastboot.
"fastboot erase nv"
"fastboot erase userdata"
"fastboot erase system"
"fastboot erase recovery"
"fastboot erase microp"
"fastboot erase boot"
"fastboot erase radio"
"fastboot flash nv nv.img"
I could try to do a flash nv nv.img perhaps, probably not a good idea since I have no idea what is in it, and likely locked against flashing. Interesting to see more fastboot partition names, although erase system or boot won't work.
Cheers!
NFHimself said:
Well, the file is about HTC phones, so it doesn't really apply, no hboot to swap to get a fastboot.
"fastboot erase nv"
"fastboot erase userdata"
"fastboot erase system"
"fastboot erase recovery"
"fastboot erase microp"
"fastboot erase boot"
"fastboot erase radio"
"fastboot flash nv nv.img"
I could try to do a flash nv nv.img perhaps, probably not a good idea since I have no idea what is in it, and likely locked against flashing. Interesting to see more fastboot partition names, although erase system or boot won't work.
Cheers!
Click to expand...
Click to collapse
i did not say that file was for you.
but if you can flash boot recovery system and your system won't boot it's something else in the bootstrap process (excluding hardware failures, you could not access fastboot then).
as i read you can flash (already flashed?) almost every partition except pds (useless for your needs) and nv.
i reported a case of other guys experiencing your same problem, with i guess the same cause.
i give you an idea, unfortunately i'm not a dev to give you solution
cheers
So I've been running my Atrix on several roms, radios, kernels etc since getting the device in late July. Was running cm7 last week, then changed to darkside 2.1 to get blur amongst others back. Now on Saturday I upgraded to darkside 2.2, following all the usual procedures of clearing cache/wipe data/dalvik and so on in CWM (RomRacers).
Since then I've had no luck in getting a connection on ANY rom or ANY radio. All the correct info is there in the apn settings, everything enabled in blur roms under battery and data settings, so I'm stuck for ideas.
I've just flashed back to my stock sbf (T-mobile uk, Froyo 2.2.2) and still have the same problem. Any thoughts on this? Hardware issue maybe?
All thoughts are appreciated, cheers guys.
fastboot erase system
fastboot erase user data *or just data if user data doesn't work for you*
fastboot erase webtop
fastboot erase boot *this is important*
fastboot erase cache
fastboot reboot
Do ALL of that, and then re-flash SBF.
jgc121 said:
fastboot erase system
fastboot erase user data *or just data if user data doesn't work for you*
fastboot erase webtop
fastboot erase boot *this is important*
fastboot erase cache
fastboot reboot
Do ALL of that, and then re-flash SBF.
Click to expand...
Click to collapse
I'll give it a try although I always do the the same procedure in CWM. This is a more thorough erase process though I take it?
*Edit* Tried doing so in fastboot - cache, user data and reboot work - boot, webtop and system commands do not.
*Edit Edit* I "Re-Unlocked" the bootloader in RSD using the IHOP-intl-fix.sbf and can now perform said commands in fastboot. Will report back.
Got everything erased usuing fastboot and reflashed the sbf, still a no go. Only thing I can think of is something hardware related? I thought it might be the sim but have signal and can make calls/texts.
Looks like a trip to the T-Mobile store is in order to try get the handset changed, luckily know a member of staff so hopefully no questions asked!
Hi, i have Atrix 4G on CM7 now. One day, I tried to pick a picture, but it didn't work. Just black screen, and in 2 minutes "Force close". Then, i download some other camera software, such as Camera 360, Go Photo, FX Camera... Still nothing. So i tried to reinstall CM7 at first, then i put back my stock kernel, i restored my backup from CWM Recovery, I put back stock AT&T Rom, i even reinstall Recovery. Nothing helped. Is it some possible way to find out that it is Hardware problem for sure, or any other solution?
THX a lot.
Try doing a complete wipe via fastboot before flashing a ROM if you are not already doing this:
reboot to recovery
wipe dalvik
wipe cache
reboot to fastboot
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot reboot (to recovery)
flash ROM
CaelanT said:
Try doing a complete wipe via fastboot before flashing a ROM if you are not already doing this:
reboot to recovery
wipe dalvik
wipe cache
reboot to fastboot
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot reboot (to recovery)
flash ROM
Click to expand...
Click to collapse
I did that...
EDIT: It is probably hardware problem, front camera works. I just want to be sure, that its really as i think... S*** But i still will be glad for any help..
EDIT2: Now, when i start the camera app, it says Camera error: Cannot conect to camera.
Anybody???
I am having issues with my ear speaker. For some reason when I flash a rom it works for 5 minutes then cuts out. I really do not want to use my loudspeaker to answer calls. It started after I flashed Neutrino 2.5p2, then I flashed CM7.2 CR and it keeps doing the same thing. Sometimes when I turn the speaker on and off it kicks on the ear speaker. Anyone have this issue before, I am prepared to replace the ear speaker, but will be disappointed if it was a software issue not a hardware issue.
I have already:
Factory Reset
Restored Roms
Cleared Cache and Div Cache
I think it might have to do with programming. The reason why is because the speaker does work for a few minutes after factory reset and rom restore. And when I turn speaker on and off it sometimes triggers the speaker to work.
Please Help me!!!!!!!
Try a full wipe and flashing again:
reboot to recovery
wipe dalvik
wipe cache
reboot to fastboot
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot reboot (to recovery)
flash ROM
If you are unsure about fastboot, there are several threads which will help you if you do a search in the Atrix forums.
CaelanT said:
Try a full wipe and flashing again:
reboot to recovery
wipe dalvik
wipe cache
reboot to fastboot
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot reboot (to recovery)
flash ROM
If you are unsure about fastboot, there are several threads which will help you if you do a search in the Atrix forums.
Click to expand...
Click to collapse
Fastboot has to be done through command prompt right? Do you have a link to erasing all the fastboot.
The problem is internal going to try to repair first. Then replacement
Sent from my MB860 using xda premium
Android The Greek said:
The problem is internal going to try to repair first. Then replacement
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Have you had any luck with this?
I had the same issue for the past few days and I assumed it was due to my ear speaker hardware. I ordered a new cable with those parts on it and replaced it this morning. $16 later, NO LUCK! GRRRR... So apparently it is a software problem at some level.
On the + side, my new front facing camera takes much clearer pictures now! haha.. (The camera was part of the same ribbon cable)
Okay, so I was trying to unlock my bootloader. Completed ALL the steps up to were I had to flash Radio.zip to get my signal back. Stupid me accidently hit to install the rom I had choosen to install after unlocking my bootloader. I didn't notice untilit was already installing. So it rebooted and I just get the non animated LG logo and it says security error under it. I am able to get to the s/w upgrade screen by holding volume up and plugging usb in. I searched Everywhere and can't solve the issue. I tried re-flashing my kdz file and it only goes to 15% then says my phone is not connected, tried reinstalling the drivers and got the same message. Then I proceeded to the online method. While doing this it found my phone and proceeded to the second part where it begins downloading. It went to 13 seconds time lapsed the stopped. No bar moving across and no more counting with the time lapse. I had read were it froze on others and they let it proceed and it did its thing. So I left it for about 4 hours and nothing changed. I then checked my traffic meter on my router and nothing had even began downloading. I reinstalled and tried again. It would go threw the checking for other software part fine then when it gets to the downloading part its at the 13 second time lapse freeze again. This time it didnt count up to it. It was just instantly where I had left off. I then went to my brothers and tried to his computer. Completely reinstalled it and it did the same thing! Didnt even count up to 13 seconds was just instantly there! I then read where someone had the same issues as me and installed fastboot and flashed xloader and uboot and then the offline method reconized them. Im thinking this is my key to fixing, however when i install the driver as instructed it says install failed because lack of electronic signature. So im lost and ran out of search methods to try. Has anyone else had this issue when installing fastboot? Also I was a little confused on which fastboot file to use so I tried a few and all had the same result. Does someone have a link to the one I need or any other advice? This stinks I just bought this phone but the stock rom was driving me crazy because im use to custom! Thanks so much and please help!!!
SOLVED! flashed ics xloader and uboot and it finally found my phone on the offline method. Now I just have the wonky TS to solve. Should be fun since I lost root and cwm. I was able to get show touches and usb debugging on so that makes lofe easier. You guys have no idea how relieved I feel! I thought I pretty much threw 200 bucks away!
Okay little update. I got fastboot loaded on my phone and flashed a recovery.img but still not having any luck. Both programs are doing the same exact thing as before. I feel like im getting there since I now have fastboot. What other options do I have that I can try?
fastboot erase userdata
fastboot erase system
fastboot erase cache
fastboot erase recovery
fastboot erase boot
Flash the ICS u and x and then use upgrade mode to flash the kdz with offline method.
Sent from my LG-P769 using XDA Premium 4 mobile app
LaDY Vengeance said:
fastboot erase userdata
fastboot erase system
fastboot erase cache
fastboot erase recovery
fastboot erase boot
Flash the ICS u and x and then use upgrade mode to flash the kdz with offline method.
Sent from my LG-P769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Okay I got it all up and running. However when I used your commands none of them would respond and do anything except flashing the ICS u and x. Once I did this I was able to get the offline method to work. I then rooted and installed Cwm to run the ts fix because I had the wonky touchscreen. I then flashed kumas rom . I forgot to use CWM to clear my cache and such before flashing to kumas ROM. Will this effect anything? Should I go to cwn and delete it all and reflash kumas ROM? Thanks!
fastboot erase userdata
fastboot erase system
fastboot erase cache
fastboot erase recovery
fastboot erase boot
I using that and i have S/W Upgrade ;(. My phone does not have logos lg and automatically turns on when you insert the batteries into the s / w upgrade
SlideShowPl said:
fastboot erase userdata
fastboot erase system
fastboot erase cache
fastboot erase recovery
fastboot erase boot
I using that and i have S/W Upgrade ;(. My phone does not have logos lg and automatically turns on when you insert the batteries into the s / w upgrade
Click to expand...
Click to collapse
So the only this you can access is sw upgrade mode? what lead up to this? did you install fastboot drivers twice?