I am experienced with rooting and unlocking and all that jazz but rules dictate i have to ask questions here. I recently unlocked and rooted my Droid DNA. I am trying to install the Super Charged Hatka Rom to the phone. i follow the instructions done to the letter but for some reason during the install im getting a symlinks status 7 error. I have tried another rom and continue getting the same error. I dont know why i continue getting these errors because i am positive i did everything right during the unlocking and rooting process. I have been working at this for roughly around 6 to 7 hours and did not sleep at all last night. I realy need some help here and it will be much appreciated because i need sleep.
What recovery do you have installed?
Sent from my HTC6435LVW using xda app-developers app
First i was on TWRP then i tried on CWM and now im back on TWRP
It almost always has to do with recovery ... did you wipe your System partition before flashing ? That maybe something to try BUT NOTE IF YOU CANNOT FLASH ANY ROM THEN YOU WOULD HAVE A NON-WORKING PHONE unless you do a stock RUU or find a custom ROM which actually flashes through
Actually i re locked the phone after a couple of tries last night to get a rom in. I eventually said screw it and wanted to go back to stock. i downloaded the ruu and i keep getting error on that as well sooooooooo, it looks like i'm stuck in limbo here
P.s sorry i took so long to respond. i passed out.....
Been trying to go back to stock for some time now but the ruu keeps coming up with errors. its error 132 signature error and its telling em to get the right ruu. pretty sure i got the right one since everyone has been using this one to return their phones to stock. need assistance please
It may be from wrong region or carrier branded one
Sent from my HTC Butterfly using xda premium
Related
Hello, I am trying to flash NFHimself's Bell 2.2.2 CWM in order to install the recent 2.3.4 OTA which won't install but I keep getting the following error, can anyone help?
assert failed: package_extract_file(''app.bin'', ''/internal/app.bin'')
E:Error in /sdcard/Bell_2.2.2.stock.zip
(Status 7)
Installation Aborted
I've tried this many many times now, anybody know how to get this to work?
I'm desperately trying to get Gingerbread Update,
Thanks, and cheers from Ottawa area!
did you try posting in the actual thread (i haven't looked thus me asking)
make sure you are using Tenfars latest recovery to flash (i believe its the 6/30 update) anything else will lead to errors in my experience.
I cant post in the dev section i only have 2 posts lol... and i am currently trying to intall tenfar's 6/30 having a few complications using fastboot, currently searching on how to install... thanks
Sent from my MB860 using XDA App
have you met the requirements? (bootloader unlocked)
Im trying to do so but i cant seem yo be able to flash anything in fastboot... I can copy well but it wont install anything :/ can you eleborate on what I would need for this to work? Thanks by the way, I believe I've seen you quite often on many other posts
Sent from my MB860 using XDA App
ok so thats where the initial problem lies, you need to be unlocked to use that recovery and then get the gobstopper.
what rom do you currently have on your device?
Just want to understand your current status before directing you.
I have stock bell 2.2.2 but I tried the webtop mod a few weeks ago, obviouly something went wrong and I tried everything to undo. Nothing worked, so next step was waiting for OTA to see if it would overwrite... It downloaded,but keeps getting stuck at the "!" screen with the little android for 3 hours, so reboot.Now I just want to be able to get GB so I go out and find it a stock rom to flash, so I found NFHimself's.
Now that doesnt work so, here I am... :'/
Sent from my MB860 using XDA App
on the ! screen did you touch the right bottom corner of the screen? (opens it up to show you what the error is).
but none the less you need to be on tenfars recovery to flash this and to do that you need to have an unlocked bootloader.
Ok so I unlocked the bootloader, and now I'm trying to flash CWM by entering Android recovery but I'm getting the ! android screen again, they say I need to delete the recovery-install.sh in root explorer and unlock again. So I did, and I still can't get into the recovery to flash CWM... any ideas?
ok forgot to do one step, i just flashed CWM and rebooting, ill keep you posted
Wow, ok, so I got NFHimself's Stock Bell working, I downloaded the OTA, installed it to 70% and
E:Error in /cache/Blur_Version.0.37.23.MB860.BellMobility.en.CA.zip
so I erased cache, rebooted and somehow GB is installed... I happy i just hope everything is going to go ok...
good to hear make sure everything is running ok though if not you may need to try again.
same error
My bootloader is unlocked and I still cant seem to get past this same error. When I try to use fastboot it will just sit on "starting fastboot protocol".
Any help would be appreciated
Thanks
what are you trying to do in fastboot?
Thanks for posting this question...I was looking for the same thing, and you (and the rest of the posters here) cleared my head right up
After countless hours of research, I decided to unlock my bootloader and to root my Motorola Atrix 4G. With success, I was happy to have everything working and installed the Darkside Custom Rom. I let a friend borrow my phone, and they saw the AT&T system update and they decided to install it. They bring back the phone and the system update has finished and was installing. The phone powers off and starts to install the update. 10% into the install, it stops, and I got the little green droid man with the /!\ behind him. I take out my battery, place it back in after 30seconds. It powers on, boots up, powers off and tries to load the update again. I restart it, but this time quickly going into RomManager and starting it up in Recovery Mode. I go to restore the phone using the file I backed up from the TitaniumBackUp app, everything backs up except the system. I plug my phone into my laptop, and everything is in the folder. I performed a system/factory reset, downloaded the last Gingerbread update, but nothing helps. Anything I try to load it says "Installation aborted". No matter if it's the original update or a ROM I download. Looking up other forums, I notice others that have downloaded the Darkside ROM have had the same; if not similar issues. I apologize for the length of this message, but I wanted to put in as much detail as I could so you know exactly what the issue is. I look forward to hearing from someone, and thank you in advance!!!
You probably need to sbf it back to a stock ROM and start over. I had a similar problem when I first got my Atrix and the AT&T update first came out. I had already rooted it and didn't unlock the bootloader yet. It tried to update and bricked the phone. Got AT&T to give me another though as I had just got the thing.
nickdeal said:
You probably need to sbf it back to a stock ROM and start over. I had a similar problem when I first got my Atrix and the AT&T update first came out. I had already rooted it and didn't unlock the bootloader yet. It tried to update and bricked the phone. Got AT&T to give me another though as I had just got the thing.
Click to expand...
Click to collapse
Thanks a ton! How would I go about doing that?
You need to download motorola RSD app to you computer. Search XDA for stock firmwares and download one. You will then need to use the button combo to get in to RSD. Connect the phone to your computer and make sure it recognizes. I had an issue where one of my laptops would not recognize the phone for anything. I had to use a different laptop. Once it's done you should be back to stock. The bootloader should be unlocked still. Just root and flash your ROM of choice.
Sent from my MB860 using XDA App
I've tried multiple, and I mean multiple ROMS. All of them will just randomly crash, even if I'm not doing anything! I recently had my friend help me fix my phone because CWM recovery messed up my phone and made it so I couldn't charge my batteries at all. That problem is over with and I have a new recovery (Amon RA). Everytime I flashed a ROM I immediately flashed PH98IMG.zip because I am S-ON. Every ROM I've installed said it was compatible with S-ON. My phone just resets itself at random no matter what ROM I am on. Should I go back to stock or something? I really need help, my phone is useless at the moment.
My current ROM is CleanROM Professional Edition. This is also crashing.
Please reply someone, I need my phone to work ASAP :/
are you installing any apps or overclocking?
This happened to me as well when I was running on the leak prior to the last leak before the ota. Either way... Relock and RUU again with a fresh download. That fixed it for me. Also S-off really helps with this type of stuff because it makes it super easy to flash anything at any time including hboots. Just be careful about combos. S-off was actually the pain in the ass I thought it would be. Didn't go as smoothly as people described. BUT if u do your homework before attempting it u won't be stuck having to ask questions about what to do in the event something doesn't go perfectly. So to recap, easy for now, RUU with a fresh download the ota is prob Ur best bet. Or hard for now easy for later s-off.
Sent from my ADR6425LVW using xda app-developers app
I noticed late last night that my rezound downloaded a system update. I was half asleep and wasnt sure how to stop it, so I ignored it assuming it woulnt work anyway since I was rooted. I woke up this morning, send 2 texts and boom my phone restarted. It started trying to install the update. It looked like it said there was an error but I couldnt read it before the phone rebooted again. Now I am stuck on the white HTC screen. Ive been reading around all morning trying to fix this, all I can find is that apparently I was supposed to relock the boot loader after I rooted? Which I dont think I did. Can someone please help me get my phone working again?
Are you S-Off?
And were you running a custom ROM of any kind?
Sent from my ADR6425LVW using Tapatalk 2
LunaticSerenade said:
Are you S-Off?
And were you running a custom ROM of any kind?
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Im not sure what S-Off is? I rooted, but only really use it for my screen shot app and wifi hotspot. No custom ROMs
Most likely no.
When I go into H Boot, I noticed that it says PH98Diag is missing, no image. Is it possible that the verizon update just deleted those files and all i need to do is put them back onto my phone and it will be usable again? If thats a possiblilty, where can I grab these files from and what folder do they need to be put into?
ALso I just realized HBoot says S-On
RA- Vigor- v3.13 is what I have also.
EDIT:
I was thinking about it, and since Hboot was saying it was missing the image, I thought maybe installing a rom would fix that. I grabbed Scotts clean ROM and went threw the install on it. After doing this the phone now starts up, and everything seems normal EXCEPT: There is no connection, calling or data. How can I fix this? Im so close to having a usable phone again, just hopefully this last little bump in the road.... I double checked with Verizon and its nothing on their side that is keeping me from service....
If you can get into hboot you can run/flash the RUU and get yourself back in action. It will put you back to stock. You might have to relock your phone if it is still unlocked.
Long story short when I first bought my Note 2 a couple months back I decided I would try and root. I had never attempted something like this before and didn't make it very far before I decided to give up. Since then the phone has been fine until today. I got a message for an update and told the phone to proceed. The phone downloaded the data and reboot itself. This is where things get weird; instead of rebooting it takes me to "Team Win Recovery Project v2.3.2.3". I'm assuming I installed some type of boot loader that is preventing the device from installing the factory Verizon update.
Again I'm really a noob at this, and on top of it I really need a stable phone right now. Our family business of 45 years essentially burnt to the ground this past Friday so I'm running around like a mad man. I receive non stop calls and emails from contractors all day and really need to feel like the device is solid again. Help, please....
Sounds like u maybe unlocked? Not sure how far u made it.... first I would install goomanager from the market and open hit menu install recovery... this will update twrp to the latest.... next I would reboot into recovery from goomanager once there backup ur device on sdcard.... then I would try to flash the modded stock update from imnuts....to remain stock...should be fairly safe as from wut I read u only need root which I'm assuming u have if u have twrp...
http://forum.xda-developers.com/showthread.php?t=2269736
Also backup ur apps SMS mms contacts pics and whatever u want to keep....
TaPpEd from my TwEaKeD N2
Or just skip the update for now if u don't want to chance it.... if u make a backup u should be ok tho just in case....
03stage2 said:
Long story short when I first bought my Note 2 a couple months back I decided I would try and root. I had never attempted something like this before and didn't make it very far before I decided to give up. Since then the phone has been fine until today. I got a message for an update and told the phone to proceed. The phone downloaded the data and reboot itself. This is where things get weird; instead of rebooting it takes me to "Team Win Recovery Project v2.3.2.3". I'm assuming I installed some type of boot loader that is preventing the device from installing the factory Verizon update.
Again I'm really a noob at this, and on top of it I really need a stable phone right now. Our family business of 45 years essentially burnt to the ground this past Friday so I'm running around like a mad man. I receive non stop calls and emails from contractors all day and really need to feel like the device is solid again. Help, please....
Click to expand...
Click to collapse
It wont update because you have a custom recovery, you should avoid updating to the newest OTA because all our current exploits for bootloader unlocking are useless on it.
Pretty much what happens when you have a custom recovery and you download the update is it tries to install but the custom recovery stops it, it will boot to TWRP which is your custom recovery and then go no further until to tell the phone to reboot into the sytem.
Sent from my SCH-I605 using XDA Premium HD app