I was trying to update my radio and also wipe the EFS partion and I installed superwipe+ and when it rebooted it's now stuck at the HTC white screen and that's it. WHAT DO I DO???
EDIT: upon calming down a little, I managed to boot it into recovery. From here should I just reboot or should I restore one of my backups?
Reinstall a backup or reflash your rom. Make sure your superwipe is correct. If you have a rom that uses ext3 only and use the ext4 superwipe you will freeze at that screen.
Thank you, the backup worked. That's the last time I do anything before I understand it 100 percent completely. I've managed to update my radio and also successfully wiped EFS without screwing anything else up.
kingston73 said:
Thank you, the backup worked. That's the last time I do anything before I understand it 100 percent completely. I've managed to update my radio and also successfully wiped EFS without screwing anything else up.
Click to expand...
Click to collapse
lol, you think the rest of us wait til we know something 100%? NO. or nothing would ever get done. it's how we learn. Don't swear off trying stuff you don't know 100%. (and get the insurance on your phone...)
Id say u superwiped and didnt flash a rom after. Superwiping wipes everything including your rom...by your description it sounds as if u didnt know that.
Sent from my HTC Vision using xda premium
Related
I started today trying to format my 2.1 rooted over to 2.2 and at some point in time have just trashed my phone. Then completely wiped/factory reset my phone. So I am sitting here and every 5 minutes or so the phone will just pop up the HTC quietly brilliant screen and it is insanely slow and barely loads anything. What can I do to just start over fresh?
It also tells me I have no service and I cant make a call to any # at all or even attempt to. So something is obviously up with the radio.
so you are rooted, right? You can get into recovery? Did you make a nandroid?
qmartman711 said:
so you are rooted, right? You can get into recovery? Did you make a nandroid?
Click to expand...
Click to collapse
My guess the answer would be "no."
Download one of the stable ROMs...Virtuous or Skyraider will work...reboot into recovery...wipe and reset everything, including the Dalvik cache and battery stats, then load the ROM.
When you get that ROM set up the way you like, boot into recovery and DO A FRIGGIN' NANDROID BACKUP.
The next time you want to **** with your phone, REBOOT INTO RECOVERY AND DO A FRIGGIN' NANDROID BACKUP FIRST!
So long as you can reboot into recovery, a Nandroid backup will take your phone back to the state it was when you did that backup.
Haha, I wanted to give him the benefit of the doubt
Sent from my Incredible using XDA App
He has a thread in the QA section which I told him to run the 2.2 ruu. He then did ran into this issue and I've asked him a few questions which he has yet to answer ...
I have a feeling when he was rooted on 2.1 he made some changes to the phone that a simple RUU would not fix as I bet it expected everything else to be normal.
Okay, today I was about to flash a new rom so I attempted to wipe, but I got an error that the phone could not mount the cache (and later couldn't mount data). It says "E:Can't mount CACHE:recovery/command" on the next line "E:Can't mount CACHE:recovery/log" and the next "E:Can't open CACHE:recovery/log". So I have tried reflashing recovery to fix it and it did not work. I cannot flash any rom without an error or restore my nandroid backups. I am in the process of trying to restore the nandroid backups throught fastboot. Can anyone give me any help on this?
SOLUTION: blancoisgod recommends formatting the cache partition to fix this problem
Did you pull the battery and retry?
Yep. Actually, the phone wont even turn on anymore. I will just have to return it to tmobile tomorrow
toby4059 said:
Yep. Actually, the phone wont even turn on anymore. I will just have to return it to tmobile tomorrow
Click to expand...
Click to collapse
This is exactly why manufacturers don't want people rooting and messing with their phones.
So because of your stupidity and lack of foresight you're now going to return your phone?! That's laughable.
Now T-Mobile and HTC have to pick up the bill for someone else's ignorance.
Note to self....remember your name and never help you!
No man dont turn it into tmobile. Now everyone is gonna ride you because you broke it and your going to return it because of what you have done,not the manufacturer.
Go ahead and turn it in, but please read around a bit before you do this again.
CBConsultation said:
This is exactly why manufacturers don't want people rooting and messing with their phones.
So because of your stupidity and lack of foresight you're now going to return your phone?! That's laughable.
Now T-Mobile and HTC have to pick up the bill for someone else's ignorance.
Note to self....remember your name and never help you!
Click to expand...
Click to collapse
Your right it is my fault; although, I am not sure what I did wrong. I am not a complete idiot and have been doing this stuff for a while. I did everything by the instructions and this happened. I actually saw this happen to someone in the G2 forum but no one found a solution. I see how returning the phone would be wrong but what are my options? I am only 15, no income, so what could I do. If I had income of course I would just pay for a new phone. I hope I am not coming off as a dumb juvenile crook, I apologize.
toby4059 said:
Your right it is my fault; although, I am not sure what I did wrong. I am not a complete idiot and have been doing this stuff for a while. I did everything by the instructions and this happened. I actually saw this happen to someone in the G2 forum but no one found a solution. I see how returning the phone would be wrong but what are my options? I am only 15, no income, so what could I do. If I had income of course I would just pay for a new phone. I hope I am not coming off as a dumb juvenile crook, I apologize.
Click to expand...
Click to collapse
Did you make a backup image? If so you could just flash your recovery image and be golden. If not, then your options are very limited.
I was not trying to hurt or insult your feelings but we constantly see people who 'think' they know what they're doing with these same issues all day every day.
My advice is limited as well at this point because I'm not sure exactly what you've done or precautions you had in place for this.
Can you even boot into the OS at all? Do a factory reset?
CBConsultation said:
Did you make a backup image? If so you could just flash your recovery image and be golden. If not, then your options are very limited.
I was not trying to hurt or insult your feelings but we constantly see people who 'think' they know what they're doing with these same issues all day every day.
My advice is limited as well at this point because I'm not sure exactly what you've done or precautions you had in place for this.
Can you even boot into the OS at all? Do a factory reset?
Click to expand...
Click to collapse
I cannot turn the phone on what so ever. I was flashing my backup through fastboot then tried to reboot and now it will no longer turn on. I fastboot erased recovery, system, userdata, and boot and restored them from the nandroid backup I had taken prior to the error. The day prior I had rooted successfully and flashed the desire z port. I decided I wanted to try the HD port so I wiped and flashed the rom. When I rebooted it got to the lockscreen and it showed some graphical corruption then began to boot loop. I turned it off and went to recovery and thats when the CACHE errors started. Was I supposed to wipe the dav cache because I am pretty sure I did. I just want to find out what I did wrong so it won't happen to me or anyone else.
toby4059 said:
I cannot turn the phone on what so ever. I was flashing my backup through fastboot then tried to reboot and now it will no longer turn on. I fastboot erased recovery, system, userdata, and boot and restored them from the nandroid backup I had taken prior to the error. The day prior I had rooted successfully and flashed the desire z port. I decided I wanted to try the HD port so I wiped and flashed the rom. When I rebooted it got to the lockscreen and it showed some graphical corruption then began to boot loop. I turned it off and went to recovery and thats when the CACHE errors started. Was I supposed to wipe the dav cache because I am pretty sure I did. I just want to find out what I did wrong so it won't happen to me or anyone else.
Click to expand...
Click to collapse
Between ROM's, you said you wiped. What did you wipe? Cache? Dalvik? Partition?
You said you're not too sure so I am going to assume you either didn't wipe something you should have or you did wipe something you shouldn't have.
Try this. Remove the battery for 10 minutes. When the battery is removed, hold the power button for about 2 minutes. This will drain any residual current left on the board. After the 10 minutes are up, try reinserting the battery, hold the volume- button and try to power on. We'll see if you can manage to boot into recovery at this point.
CBConsultation said:
Between ROM's, you said you wiped. What did you wipe? Cache? Dalvik? Partition?
You said you're not too sure so I am going to assume you either didn't wipe something you should have or you did wipe something you shouldn't have.
Try this. Remove the battery for 10 minutes. When the battery is removed, hold the power button for about 2 minutes. This will drain any residual current left on the board. After the 10 minutes are up, try reinserting the battery, hold the volume- button and try to power on. We'll see if you can manage to boot into recovery at this point.
Click to expand...
Click to collapse
Okay I will give that a try thanks.
I had the same error just right now man
What you want to do is format the cache partition when you get the thing booted.
blancoisgod said:
I had the same error just right now man
What you want to do is format the cache partition when you get the thing booted.
Click to expand...
Click to collapse
Did you do that and did it fix? I did that through adb and thats when it stopped booting, although I think the boot issue is unrelated to my current problem.
i did it via clockwork
Alright, I will try this if I can ever get my phone started again.
Just wondering if anyone who's flashing and rooting could please do a backup and upload it somewhere. Myself and a couple others have accidentally partitioned our internal SD incorrectly causing a catastrophic touch screen issue.
I'm hoping it'll have the properly partitioned SD storage because I'm having difficulty doing it manually. If someone could upload this it'd be hugely appreciated!!!
BUMP!!!
Can anyone please provide me with a Nandroid backup using Tenfar's recovery??? I can throw some money once I get my Paypal sorted out. I'm desperate, fellas!
Can someone please help? I'd like to try anything I can to get my phone working this weekend. It's been an entire week without my Atrix.
bongd said:
Can someone please help? I'd like to try anything I can to get my phone working this weekend. It's been an entire week without my Atrix.
Click to expand...
Click to collapse
Im relatively new to android...is this backup you are speaking about a TB backup. Or what method of backup are you looking for?
Sent from my MB860 using Tapatalk
You actually need to be rooted and have Tenfar's custom Recovery menu. In there it has an option to do a Backup.
If you're new it may be too engaging but I appreciate the offer nonetheless. If you could help, it'd be great. If it's too much trouble, I thank you anyway!
yeah what does the nandroid backup...back.. up? the apps?
What I'm HOPING and PRAYING for is that it'll also copy something in the internal SD which was partitioned due to my stupidity. dev/block/mmcblk0p18 is what that is in particular.
I tried manually formatting and partitioning it but I'm unable to do so. Fastboot freezes and Early USB Enumeration goes by so quickly I can't run the commands that I need through ADB. And I don't even know if that'll work because I made a script that executes the commands and I get weird errors. I'm far from an expert and monkeyed around too deeply where I shouldn't have.
About 4-5 others are reporting the same problem. The ****ty thing is that I'm in Canada and it'd be a huge pain to send it to Motorola. They're giving me a lot of grief and I've had to put up a big fight. Waiting to see if they'll send an RMA because I may need to send it in. When I get it back I might sell it and buy a Bell Atrix because I live in Canada and if something bad happens, it'll be easier to send to Bell or Motorola Canada.
from what i understand you have to have an unlocked bootloader to backup or restore using a nandroid backub
Maybe I'm using the wrong terminology then.. just need a backup from Tenfar's customer Recovery. I don't even know if it'll work but I'm out of ideas.
I'm at least thankful that the Xperia X10's bootloader was cracked. I forgot to send a replacement back to Rogers and I phoned them asking if I could use it for now. They thankfully said yes because they forgot to charge me for it lol... it's got some really great ROMs, but looking at this beautiful, mangled Atrix makes baby Jesus cry!
i can do that but im wondering why you dont try SBF file?? should work better than Backup
zen kun said:
i can do that but im wondering why you dont try SBF file?? should work better than Backup
Click to expand...
Click to collapse
i was just wondering the same thing... it also be more stable as nandroid restore are not so good on some phones and im guessing especially on a locked bootloader one.
also a nandroid backup would also restore some else's settings and information on your device....
Ronaldo_9 said:
i was just wondering the same thing... it also be more stable as nandroid restore are not so good on some phones and im guessing especially on a locked bootloader one.
also a nandroid backup would also restore some else's settings and information on your device....
Click to expand...
Click to collapse
I've already tried the SBF files but it doesn't do anything to the internal SD. I need an actual backup because the user settings are exactly what I'm looking for. Normally you'd want a fresh flash from stock but I hope you now understand why I'm asking this constantly.
Flashing to stock was naturally my first step. Unfortunately it had failed. About 5 others reporting the same problem.
bongd said:
I've already tried the SBF files but it doesn't do anything to the internal SD. I need an actual backup because the user settings are exactly what I'm looking for. Normally you'd want a fresh flash from stock but I hope you now understand why I'm asking this constantly.
Flashing to stock was naturally my first step. Unfortunately it had failed. About 5 others reporting the same problem.
Click to expand...
Click to collapse
What maybe you could do is? go into tenfars cwm recovery go to mounts and storage and format the internal sdcard and system and boot and data. This is safe as far as I know and me and tenfar have both done this.I literally formatted every single thing in the option menu. just to see if I could do it. Which was stupid but I was curious and used to do that before I installed new roms on my old backflip all the time! Also might wanna do a factory reset through cwm and clear dalvik cahe as well for good measure. Now after you format all that. reboot system which will send you in a boot loop/wont boot past first screen. Pull the battery and unplug usb cable from charger. Then reboot and enter rsdlite mode by holding volume up and the power button. Now just flash your 4.1.26 sbf file through rsdlite 5.0
As long as you flash back to retail 4.1.26 afterwords using rsdlite 5.0 that should put everything right! As I have done this and my phone is working normal.
I better put one of them warnings here though anyway lol
Disclaimer: You are doing this at your own risk! I am not responsible for any damage you do to your phone.
(^Yeah I think that covers it)
Gutterball said:
What maybe you could do is? go into tenfars cwm recovery go to mounts and storage and format the internal sdcard and system and boot and data. This is safe as far as I know and me and tenfar have both done this.I literally formatted every single thing in the option menu. just to see if I could do it. Which was stupid but I was curious and used to do that before I installed new roms on my old backflip all the time! Also might wanna do a factory reset through cwm and clear dalvik cahe as well for good measure. Now after you format all that. reboot system which will send you in a boot loop/wont boot past first screen. Pull the battery and unplug usb cable from charger. Then reboot and enter rsdlite mode by holding volume up and the power button. Now just flash your 4.1.26 sbf file through rsdlite 5.0
As long as you flash back to retail 4.1.26 afterwords using rsdlite 5.0 that should put everything right! As I have done this and my phone is working normal.
I better put one of them warnings here though anyway lol
Disclaimer: You are doing this at your own risk! I am not responsible for any damage you do to your phone.
(^Yeah I think that covers it)
Click to expand...
Click to collapse
JUST got your PM as I was clicking this thread. Thanks, broski.
I've got nothing to lose. It's easy enough to recover from soft-brick. I'll give it a shot right now. Wish me luck!
*** UPDATE ***
Still no dice. Bummer.
bongd said:
JUST got your PM as I was clicking this thread. Thanks, broski.
I've got nothing to lose. It's easy enough to recover from soft-brick. I'll give it a shot right now. Wish me luck!
*** UPDATE ***
Still no dice. Bummer.
Click to expand...
Click to collapse
mmm weird..
IMO if sbf dont help i really doubt a recovery will....
perhaps i highly recommend if someone do this, create a new account of gmail and flash a sbf file since the OP will have all sensitive data as email,contacts and so on as previous post say
zen kun said:
mmm weird..
IMO if sbf dont help i really doubt a recovery will....
perhaps i highly recommend if someone do this, create a new account of gmail and flash a sbf file since the OP will have all sensitive data as email,contacts and so on as previous post say
Click to expand...
Click to collapse
That won't work either. I have reasons for wanting a backup versus a new SBF flash as stated multiple times.
I have a nand if you still need one
Sent from my MB860 using XDA App
sgtmedeiros said:
I have a nand if you still need one
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Your motoblur account information is stored in plaintext and your google contact information is also in a nandroid backup. Be weary.
knigitz said:
Your motoblur account information is stored in plaintext and your google contact information is also in a nandroid backup. Be weary.
Click to expand...
Click to collapse
I was not aware of this and was so focused on correcting the challenge that this was a complete oversight. On second thought, I don't want to compromise anyone's security.
I had in mind a fresh backup, preferably for AT&T's 1.2.6 SBF but it's a bit of trouble and a lot of space. I retract my request due to the amount of work involved and that I don't want to compromise anyone's security in case they don't clear their user details, etc.
Thanks for pointing that out, knigitz. I think ADB access in the Recovery is our best bet. Crossing my fingers.
bongd said:
You actually need to be rooted and have Tenfar's custom Recovery menu. In there it has an option to do a Backup.
If you're new it may be too engaging but I appreciate the offer nonetheless. If you could help, it'd be great. If it's too much trouble, I thank you anyway!
Click to expand...
Click to collapse
Ill help you with your backup if you can help me root and flash the gladix rom on mine.
Sent from my MB860 using XDA App
I have 2 backups that I have tried to restore while using twrp 3.0. No h seem like they restore but when the phone gets to the screen where it would eventually say Android after the animation never goes away and the phone doesn't boot all the way up. Has anyone else had this problem or know a solution. When I did my back ups I backed up everything available including vendor and vendor.img. I just continue to get a bootloop and phone doesn't boot. Thank u to anyone who may help
This happened to me as well even before trwp 3.0. It worked for me once I restored only boot, system, and data.
janedoesmith said:
This happened to me as well even before trwp 3.0. It worked for me once I restored only boot, system, and data.
Click to expand...
Click to collapse
Thanks. I think I tried this how you've said but I'll try again later as I need to make sure my phone is working for now.
Since day 1 I've always backed up boot, system and data. Not sure why anyone would ever back up anything else. Takes up too much space and is unnecessary. I've never had one issue. On all past devices (all Nexus) I've always backed up boot, data and system. New twrp is great! Now we can flash vendor images!! ?
Sent from my Nexus 6P using Tapatalk
Mostly just out of curiosity I flashed a new ROM this weekend. I decided I like pure nexus better so I flashed my backup from twrp but wound up in bootloop. Even though I've never had issues restoring ROMs with MANY other devices, I still followed the directions for backing it up very carefully. I also did a full wipe before trying to restore it. In fact after the 3rd attempt I accidentally wiped internal storage. So that wasn't the issue.
Only thing I can figure is I was using elemental kernel when I made the backup so maybe that was the problem? I don't see why it would matter (or how that would work--removing the kernel, make backup, flash kernel again...) but I'm really stumped on how I went wrong.
KLit75 said:
Mostly just out of curiosity I flashed a new ROM this weekend. I decided I like pure nexus better so I flashed my backup from twrp but wound up in bootloop. Even though I've never had issues restoring ROMs with MANY other devices, I still followed the directions for backing it up very carefully. I also did a full wipe before trying to restore it. In fact after the 3rd attempt I accidentally wiped internal storage. So that wasn't the issue.
Only thing I can figure is I was using elemental kernel when I made the backup so maybe that was the problem? I don't see why it would matter (or how that would work--removing the kernel, make backup, flash kernel again...) but I'm really stumped on how I went wrong.
Click to expand...
Click to collapse
What partitions did you backup/restore?
Heisenberg said:
What partitions did you backup/restore?
Click to expand...
Click to collapse
Well Ive got the right guy to talk to Pretty sure it was what you suggested (system/data/boot/vendor boxes)
But I don't recall if I checked everyone to restore. However, I did store the backup on my computer. Even though I've since got everything back I can try again to restore it. But can you just confirm which I should check when I restore it?
I'll be certain to pay closer attention next time. Its just that this is one thing I had never struggled with. Thanks
KLit75 said:
Well Ive got the right guy to talk to Pretty sure it was what you suggested (system/data/boot/vendor boxes)
But I don't recall if I checked everyone to restore. However, I did store the backup on my computer. Even though I've since got everything back I can try again to restore it. But can you just confirm which I should check when I restore it?
I'll be certain to pay closer attention next time. Its just that this is one thing I had never struggled with. Thanks
Click to expand...
Click to collapse
I recommend restoring system, data, boot, and vendor. Just make sure you're not restoring system image or vendor image.
Heisenberg said:
I recommend restoring system, data, boot, and vendor. Just make sure you're not restoring system image or vendor image.
Click to expand...
Click to collapse
So simple. Thanks a lot!
KLit75 said:
So simple. Thanks a lot!
Click to expand...
Click to collapse
Let me know if you get it booting.
Heisenberg said:
Let me know if you get it booting.
Click to expand...
Click to collapse
Well yes. Thanks again. However, I've got something funky going on. Pin pointing is hard but yea the backup restored. Then I tweaked elemental kernel (nothing crazy, used stable profiles) maybe it was that and an xposed mod (thinking ifont because its one I only just started using lt recently). Anyway when I rebooted to install drivers for viper I got stuck in bootloop. This time I couldn't restore my backup. So I factory reset and reflashed pure nexus. Due to the time I couldn't try and restore the backup again but will try tonight. If I wasn't so hasty I could've deleted the modules list in twrp then maybe booted up but I'm not 100% it has anything to do with xposed. One other factor, it was using dark stock theme.
EVERYTHING I mentioned I've done/run on this ROM without issues but there's a combination of things that's causing the bootloop I think.