Hi all,
I recently recovered from a pretty disastrous softbrick and now I'm trying to flash back some custom ROM's but can't seem to make any progress.
I had to use NVFlash to restore my bootloader three times today, because no matter what I flash (ICS or JB), it breaks it.
I'm on the stock .29 firmware atm, and I'm unable to flash anything else. I've tried CM 10, Baked #6, CM 9.1, CleanROM, and basically any others I can think of. I even tried flashing the latest JB firmware from the ASUS website but was greeted with a "FAILED: remote <>" error.
I've followed the directions on the CM wiki about performing a factory wipe before flashing, I've wiped caches and dalvik cache, still nothing.
That being said, I am able to USE my tablet but I can't change anything atm. I am rooted and unloaded with CWM recovery so I'm happier than being bricked, but I'd like to change from stock obviously.
Can anyone advise me to move forward?
I appreciate any responses, thanks.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
You could try TWRP?
Sent from my R800i using xda app-developers app
UndisputedGuy said:
You could try TWRP?
Sent from my R800i using xda app-developers app
Click to expand...
Click to collapse
I mean I could but at this point I don't think its an issue with the recovery I'm using. It seems to be something since my bootloader messed up.
This guy seems to be having the exact same problem I'm having, so it's odd that we both posted threads so close to each other.
Sounds like a bootloader problem to me. Sorry I don't know how to fix it.
Well, I can't seem to find a solution for your problem. I've never seen something like it before. I'm guessing you probably messed something up when wiping your device. Hope you get it fixed, though.
Related
Sorry if this has already been posted.
My phone is rooted on stock rom.
It started freezing up and wouldnt send text messages. GO sms locked me out. I had to take the battery out and restart several times. Now i cant connect to any wifi. In wifi settings it just says error. Any ideas what could be wrong?
your best bet is probably to flash back to stock OS...i dunno if there is a one click for inspire
or you could flash a rom :]...this was probably a weird glitch that would go away with a simple full flash
Why not start with doing a factory reset?
Sent from my Desire HD using XDA Premium App
I think he already did that, but if that doesn't work, try restoring your entire phone to stock...idk if there is a one click Odin for inspire like there is for Galaxy S models
Thats what I was thinking about doing. Will try that this weekend when I have time. Thanks!
henry.menzies said:
Thats what I was thinking about doing. Will try that this weekend when I have time. Thanks!
Click to expand...
Click to collapse
There's a guide stickied to this section that believe has the link to the RUU, which is what you might try, though I think going the RUU route will unroot you.
Inspired Ace 1.0.1¦ XDA Premium
Full wipe reflash should do it.
Sent from my HTC Desire HD using XDA App
yep I would try wipe data/factory reset, wipe cache, wipe delvik cache and a clean install of the rom
Flashed CoreDroid didnt fix the problem
would flashing a new radio fix the problem?
Did you have any luck with this? Im having the same issue and debating whether or not I should flash back to stock to see if this resolves the issue. I have flashed countless ROMs since root with no luck.
My phone is doing the same thing. Not sure when it started doing it since I don't use wifi often. I wanted to check for updates and the HTC one requires WIFI be on, thats how I found out.
My phone is completely stock, with only Apps installed. Factory reset made it say something about connecting for 10 seconds or so before saying error, and now once again it just says error every time i try to enable it.
Hey guys, I'm currently on the ICS leak and SCV7 rom, and my phone just keeps crashing and restarting, I've cleared the cache and dalvik cache multiple times, I don't think it was doing this on 2.3.6. What can I try? I just took this thing out of the box
Couple things you can try:
Factory reset.
Try NOT overclocking.
And try removing the supercharger script.
Sent from my SAMSUNG-SGH-I727 using xda premium
Fall of Enosis said:
Couple things you can try:
Factory reset.
Try NOT overclocking.
And try removing the supercharger script.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Thanks for the reply, it was doing it on the leak as well because I had a lot of trouble getting it rooted. It seems that every time it crashes it goes through the boot loop, crashes at a certain part, then boots properly to the lockscreen. The phone feels awesome and fast but extremely unstable. Another problem I'm having, root doesn't seem to be working, "Super user has denied Super user request" nothing can get root, so I can't boot into CWM to try and wipe stuff properly. Maybe I got a dodgy version of the leak or something I'm not sure, I guess I'm lucky I didn't install the OTA and I can go back. Any idea on the root situation?
EDIT: Just did a factory reset in stock recovery, can you tell me how I can go about not overclocking removing the supercharger script? And once it boots, if it boots, I'm going to try and root using the ICS .bat root script and hopefully I can get into a custom recovery.
When installing SCv7 is it normal for it to get stuck on the Preparing SCv7 message and then reboot? I'm not sure if it's installing scripts and restarting the phone or what... Because it did this the first time I installed it, and it's doing it again now after a factory reset. If I can get into CWM I'll try and flash the rom again. Can I flash the other ICS rom after a wipe, or do I need to FXZ back to 2.3.5, OTA to 2.3.6, flash the leak, then install the other rom?
I installed the other rom based on the leak, same problem, tried without my sim card, without my sd card, just keeps crashing, boot looping, and being generally unstable. Atm I'm using Jims FXZ script to go back to GB, I'll update to 2.3.6, keep everything stock and see how the phone goes, I'm really hoping I don't have the same problems on GB, because if I do then it seems like a hardware issue, and I really can't be bothered sending it back. I'll keep updating.
Rdavisct has posted in the SCV7 thread about how to remove those, and yes mate, I think you're on the right track with FXZing back to 2.3.5 and the re-updating to ICS.
Let me know how it goes. I'll keep an eye on this thread. :fingers-crossed:
I need to get the battery charged then I can fxz back to 2.3.5. Hopefully it all works out. Any ideas what would have caused the crashing?
Sent from my HTC Vision using xda premium
No clue man. Phones and flashing are funny that way.
Sent from my SAMSUNG-SGH-I727 using xda premium
Fall of Enosis said:
No clue man. Phones and flashing are funny that way.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
I hope it all works out because I literally only got to use the phone for about 5 minutes . Really liked ICS, super smooth super fast, screen is awesome. Crossing my fingers. My old HTC at least lasted a month or so before bricking .
I've subscribed to this thread so let me know if you run into any hiccups.
Sent from my SAMSUNG-SGH-I727 using xda premium
Ok, I have an AT&T HTC One X. I have already rooted the phone and I have been running Venom Rom successfully for quite some time now. I decided I wanted to give some other roms a try today and I am running into some weird issues that I can't seem to figure out. To clarify my set up, I am not trying to run any custom kernels or anything that would potentially cause the issues I am experiencing. The roms I have tried and had these issues on are King Kang, Paranoid Android, and CM 10 official. With each the issues are always the same. First of all, I can't even type anything because Android Keyboard keeps force closing. Secondly, none of my hardware keys work at all except the back key, volume rocker, and power (home and recent apps do not function at all except to vibrate). Basically it leaves the phone completely unusable. I have gone back to Venom Rom for now because I have NEVER had any issues out of it. If anyone has any ideas why I am being plagued with these issues I would appreciate some feedback because I can't seem to find anyone else experiencing these kinds of issues honestly. Also I might add that I used a method to downgrade my HBOOT to, I believe, 1.09 instead of 1.14 because of the need to flash kernels separately with 1.14. My phone has worked flawlessly installing any ICS roms. This seems to only happen with JB roms. Thanks for your help in advance guys!
Factory reset in TWRP, and wipe Dalvik and cache before flashing any new ROM?
And to confirm, you are flashing the respective boot.img extracted from each ROM file, every time you've flashed a new ROM?
redpoint73 said:
Factory reset in TWRP, and wipe Dalvik and cache before flashing any new ROM?
And to confirm, you are flashing the respective boot.img extracted from each ROM file, every time you've flashed a new ROM?
Click to expand...
Click to collapse
Yeah, I of course did a factory reset and wiped cache and dalvik.
As far as the boot.img, I was under the impression that was only necessary for those with HBOOT 1.14 which is why I reverted my HBOOT. That was the only reason I have read anywhere to have the extract the boot.img. I am not new to Android or rooting.
guitarjuggalo said:
Yeah, I of course did a factory reset and wiped cache and dalvik.
Click to expand...
Click to collapse
If you don't tell us, we don't know. Its a common mistake, and better to ask, rather than the possibility of your issue just being something simple like not wiping.
guitarjuggalo said:
As far as the boot.img, I was under the impression that was only necessary for those with HBOOT 1.14 which is why I reverted my HBOOT. That was the only reason I have read anywhere to have the extract the boot.img. I am not new to Android or rooting.
Click to expand...
Click to collapse
Ah, I see I read that part too quickly. Confirm on the hboot screen that you are in fact on hboot 1.09, since you seem unsure.
And you are on TWRP, not CWM right?
Yea he wouldn't even boot up if he was on 1.14...
OP, are you doing a titanium backup?
Sent from my One X using Tapatalk 2
redpoint73 said:
If you don't tell us, we don't know. Its a common mistake, and better to ask, rather than the possibility of your issue just being something simple like not wiping.
Ah, I see I read that part too quickly. Confirm on the hboot screen that you are in fact on hboot 1.09, since you seem unsure.
And you are on TWRP, not CWM right?
Click to expand...
Click to collapse
Yes, I am on 1.09 for sure and using TWRP.
InflatedTitan said:
Yea he wouldn't even boot up if he was on 1.14...
OP, are you doing a titanium backup?
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
No, I haven't done a titanium backup. When things didn't work for whatever reason in any of those roms I just went back to the nandroid backup I had for Venom Rom that I did before jumping to any of those roms.
That's odd... usually a 100% fresh install comes out with good results lol.
Sent from my One X using Tapatalk 2
InflatedTitan said:
That's odd... usually a 100% fresh install comes out with good results lol.
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Yeah, it is very weird. I have never encountered these kind of issues. I have been using android since the original G1 on T-Mobile and haven't encountered issues with roms this horrible. Installing any of those roms makes my phone pretty much unusable. All 3 of them (haven't tried others) exhibit the same issues. Android keyboard force closes over and over again and won't ever pull up, and the home and recent apps buttons don't work at all. Also just about any Google app or service I tried to use was crashing out.
What are you using to download?
Sent from my One X using Tapatalk 2
InflatedTitan said:
What are you using to download?
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Downloading through wi-fi on my computer and sending it to the phone via USB. Also dried downloading directly to the phone over wi-fi. Results are all the same.
So, it appears that nobody has an answer?
Did you check the md5 of the zip before flashing?
I had a problem where the Rom would install fine but issues loading. Md5 of the zip on my pc was good but was bad on my sdcard. Got messed up while transferring I guess.
Also try updating to latest twrp
Sent from my HTC One XL using xda app-developers app
Make sure you aren't flashing 4.2 gapps on a 4.1 ROM. That could cause a lot of Google app FCs.
Sent from my One X using xda app-developers app
lauterm said:
Make sure you aren't flashing 4.2 gapps on a 4.1 ROM. That could cause a lot of Google app FCs.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I officially feel retarded. Thank you so much! That was indeed the issue. FML lol :good: :victory:
Its amazing that gapps controls so much that it even screwed my hardware keys with the wrong version. I really appreciate all the suggestions guys.
Hi. I recently installed Liquid Smooth (Unofficial) 4.3 onto my Skyrocket. Since install, if I reboot the phone it will get the ever dreaded Black Screen Of Death. The only way I've found to fix this is to clear the data partition in my recovery (TWRP updated to most recent version) and then reflash the ROM and the gapps. Any ideas on how to keep the BSOD from happening again? I've tried everything I can think of. I tried just wiping the dalvek, cache and system and then flashing the ROM again. As I said, the only way I can find to "fix" it is to wipe the data partition and then flash the ROM and gapps again. I would have asked in that specific thread, but since I am a new member I can't until I reach the 10 post requirement.
CoolWolf22 said:
Hi. I recently installed Liquid Smooth (Unofficial) 4.3 onto my Skyrocket. Since install, if I reboot the phone it will get the ever dreaded Black Screen Of Death. The only way I've found to fix this is to clear the data partition in my recovery (TWRP updated to most recent version) and then reflash the ROM and the gapps. Any ideas on how to keep the BSOD from happening again? I've tried everything I can think of. I tried just wiping the dalvek, cache and system and then flashing the ROM again. As I said, the only way I can find to "fix" it is to wipe the data partition and then flash the ROM and gapps again. I would have asked in that specific thread, but since I am a new member I can't until I reach the 10 post requirement.
Click to expand...
Click to collapse
Try using the latest CWM recovery. Some people are reporting having better luck using this for the BSOD issue.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
jondroid2 said:
Try using the latest CWM recovery. Some people are reporting having better luck using this for the BSOD issue.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
I will try this and will get back to you. I'd still like to know what's causing the issue in the first place. I've been flashing on Samsung devices since the original Epic 4G launched. Never have had any issues like this before.
CoolWolf22 said:
I will try this and will get back to you. I'd still like to know what's causing the issue in the first place. I've been flashing on Samsung devices since the original Epic 4G launched. Never have had any issues like this before.
Click to expand...
Click to collapse
I've had the same issue and switching to cwm solved it. It's a real pita though as a prefer twrp and my nandroids are twrp. I switch back and forth between them.
jd1639 said:
I've had the same issue and switching to cwm solved it. It's a real pita though as a prefer twrp and my nandroids are twrp. I switch back and forth between them.
Click to expand...
Click to collapse
CWM fixed my BSOD. I've had 2 successful reboots so far. I too preferred TWRP over CWM. But oh well. I am in contact with the devs for TWRP to see if they are aware of the issue and can issue a fix for it.
CoolWolf22 said:
CWM fixed my BSOD. I've had 2 successful reboots so far. I too preferred TWRP over CWM. But oh well. I am in contact with the devs for TWRP to see if they are aware of the issue and can issue a fix for it.
Click to expand...
Click to collapse
There's an build of TWRP 2.7 that I've been using and haven't had any issues with. The only thing "wrong" with it is it only reads internal storage. Here's the Link
theesotericone said:
There's an build of TWRP 2.7 that I've been using and haven't had any issues with. The only thing "wrong" with it is it only reads internal storage. Here's the Link
Click to expand...
Click to collapse
Thanks. I'll download that and keep it in reserve for future reference.
Hi all,
I have looked all thought the forum and the closest thing I found to an answer was try twrp. What I have is an tf300t running 4.1.1 with stock rom, and cmw 6.0.2.3. Every time I try and create a back up I get "error while backing up boot image". I have tried backing up to external sd, internal, and even tried different SD cards. Nothing seems to be working. Has anyone else had this problem? Or any idea what it might be?
Thanks
Sent from my Nexus 7 using XDA Premium 4 mobile app
zac.wright said:
Hi all,
I have looked all thought the forum and the closest thing I found to an answer was try twrp. What I have is an tf300t running 4.1.1 with stock rom, and cmw 6.0.2.3. Every time I try and create a back up I get "error while backing up boot image". I have tried backing up to external sd, internal, and even tried different SD cards. Nothing seems to be working. Has anyone else had this problem? Or any idea what it might be?
Click to expand...
Click to collapse
Well, "Try TWRP" is indeed the right answer.
I think CWM uses the stock CM kernel and that does not expose the boot partition as a device. So CWM can neither read nor write the boot partition and an error is what you get trying to back it up.
Sent from my TF300T using Tapatalk
Thanks, I did go ahead and install twrp and it worked just fine. Should have done it from the beginning, I like it better anyway.
Sent from my Nexus 7 using XDA Premium 4 mobile app