Hi, hope somebody can help me with my B70 TF101, rooted but everything else stock.
Earlier this week I received an Encryption Unsuccesfull message, tablet worked fine in the morning, would not work in the afternoon.
I tried a factory reset (volume down & power, but no luck, it starts but then displays the android with red exclamation mark.
After searching the forum I tried to use Easyflasher's unbricking/ flashing stock firmware tool with the latest Asus update for the US, chose SBK2 as it is a B70, Easyflasher showed succes, however when I tried to reboot the TF I receive the unrecoverable bootloader 0x000000004 error .
Anybody have any ideas what went wrong and how to correct this?
Thank you.
AmstelD said:
Hi, hope somebody can help me with my B70 TF101, rooted but everything else stock.
Earlier this week I received an Encryption Unsuccesfull message, tablet worked fine in the morning, would not work in the afternoon.
I tried a factory reset (volume down & power, but no luck, it starts but then displays the android with red exclamation mark.
After searching the forum I tried to use Easyflasher's unbricking/ flashing stock firmware tool with the latest Asus update for the US, chose SBK2 as it is a B70, Easyflasher showed succes, however when I tried to reboot the TF I receive the unrecoverable bootloader 0x000000004 error .
Anybody have any ideas what went wrong and how to correct this?
Thank you.
Click to expand...
Click to collapse
Can you boot in recovery?
Edit: Err.. did you flash the right ROM? Every one that has that problem is on the Prime, not the TF101. See this thread, brick 1b and 2.
No recovery, I can only get into APX.
Used US_epad-user-9.2.1.27 with Easyflasher. Downloaded from the Asus site.
Lethe6 said:
Can you boot in recovery?
Edit: Err.. did you flash the right ROM? Every one that has that problem is on the Prime, not the TF101. See this thread, brick 1b and 2.
Click to expand...
Click to collapse
AmstelD said:
No recovery, I can only get into APX.
Used US_epad-user-9.2.1.27 with Easyflasher. Downloaded from the Asus site.
Click to expand...
Click to collapse
Any other ideas or suggestions?
Is my TF101 now permanently bricked?
Can you flash it again with easy flasher?
Lethe6 said:
Can you flash it again with easy flasher?
Click to expand...
Click to collapse
I tried reflashing with Easyflasher, it shows success, but gives the same error at reboot.
Can you try an older revision of the firmware?
AmstelD said:
I tried reflashing with Easyflasher, it shows success, but gives the same error at reboot.
Click to expand...
Click to collapse
If flashing stock fails again then try following step
Instead of flashing stock rom, Try flashing recovery(TWRP) through easy flash, if that's a success then get into recovery n DELETE/FORMAT internal memory, cache, dalvik and everything under wipe option... down a custom ROM and flash it.. that might work
Sent from my Transformer using xda app-developers app
Lethe6 said:
Can you try an older revision of the firmware?
Click to expand...
Click to collapse
Looking for an older version of the stock to download, no longer on the Asus site. Where else can I find that? Need a US version of the stock.
udupa82 said:
If flashing stock fails again then try following step
Instead of flashing stock rom, Try flashing recovery(TWRP) through easy flash, if that's a success then get into recovery n DELETE/FORMAT internal memory, cache, dalvik and everything under wipe option... down a custom ROM and flash it.. that might work
Sent from my Transformer using xda app-developers app
Click to expand...
Click to collapse
I have tried to flash TWRP, receive success confirmation, but can not boot into recovery, still giving the unrecoverable boot error message.
Any other suggestions?
Looks like you're using an unsigned loader or something... but at this point I'm not sure how to solve this. Maybe try posting in the easy flasher thread, the author might have some ideas. If you want to start learning the more hardcore stuff, you can take a look here, though it's for a different model but can point you in the right direction.
This guy had the motherboard replaced to fix it.
People having the same problem, you should keep an eye out there as well.
Finally, last ditch effort... maybe roll back to 3.0? See the update in this post.
Even though some help/answers are for different models, they can help you think of new solutions or provide generic tools; it's worth looking into.
Thanks for the assistance. I gave up on the tf101 and bought a Note 2.
Lethe6 said:
Looks like you're using an unsigned loader or something... but at this point I'm not sure how to solve this. Maybe try posting in the easy flasher thread, the author might have some ideas. If you want to start learning the more hardcore stuff, you can take a look here, though it's for a different model but can point you in the right direction.
This guy had the motherboard replaced to fix it.
People having the same problem, you should keep an eye out there as well.
Finally, last ditch effort... maybe roll back to 3.0? See the update in this post.
Even though some help/answers are for different models, they can help you think of new solutions or provide generic tools; it's worth looking into.
Click to expand...
Click to collapse
Related
I tried rooting my phone, but when I flashed CWM my Nexus S stopped booting... it freezes on the Google screen in the intro. I can boot into Fastboot, and cwm, but I cant connect the Internal memory to the computer without it booting like it is supposed to. Does anybody know of anything I can do to fix my phone and bring it back to stock??
There are guides for returning to stock stickied in the Nexus S 4G Android Development forum.
Before you do that though, try flashing a different recovery, like the one linked to here or here.
Btw, which guide did you use? You're not the first person to have this problem, and it's really bugging me (though probably not as much as it's bugging you :-o).
Maximilian Mary: I tried to post the link, but since I'm a new member I have to wait 8 posts before I can post a URL.... :/
I will try a different recovery, but how would I flash a rom if I can connect my phone via usb mount?
deadzunehd said:
Maximilian Mary: I tried to post the link, but since I'm a new member I have to wait 8 posts before I can post a URL.... :/
Click to expand...
Click to collapse
What's the title of the thread?
.
I will try a different recovery, but how would I flash a rom if I can connect my phone via usb mount?
Click to expand...
Click to collapse
I'm a little out of my depth here, but I think it's
fastboot flash system system.img.
You don't need to put the rom image on the sdcard. Just put it in the same folder as fastboot.
It was titled "How to Root Nexus S!"
And I will try to flash recovery and try that rom command, thank you )
deadzunehd said:
It was titled "How to Root Nexus S!"
And I will try to flash recovery and try that rom command, thank you )
Click to expand...
Click to collapse
Hmmm. I can't find that exact title. Could you pm me the link?
deadzunehd said:
thank you )
Click to expand...
Click to collapse
There's a button for that.
I got the link. Thanks. I looks like you flashed a boot image that is incompatible with your phone. That guide was for the T-Mobile Nexus S. (Why they're screwing with the boot.img to begin with, I really don't understand.)
Download the attached file, and unzip it to the same folder as fastboot. The md5 sum is d4a9508f9321eb25df3383f00f571e8b. Then
Code:
fastboot flash boot boot.img
You'll probably also want to use one of the recoveries listed above to
Code:
fastboot flash recovery recovery.img
, but leave system alone for now. Flash that only as a last resort.
deadzunehd said:
I tried rooting my phone, but when I flashed CWM my Nexus S stopped booting... it freezes on the Google screen in the intro. I can boot into Fastboot, and cwm, but I cant connect the Internal memory to the computer without it booting like it is supposed to. Does anybody know of anything I can do to fix my phone and bring it back to stock??
Click to expand...
Click to collapse
I had this problem after flashing the wrong ROM onto my phone. I got the phone back to stock using ODIN.
My thread can be found here
http://forum.xda-developers.com/showthread.php?p=14172335#post14172335
hope it helps
Acnescar said:
I had this problem after flashing the wrong ROM onto my phone. I got the phone back to stock using ODIN.
My thread can be found here
http://forum.xda-developers.com/showthread.php?p=14172335#post14172335
hope it helps
Click to expand...
Click to collapse
OMG!! im having the same issue. could you please post the link for ODIN so i can return to stock and take it from there please? I rely on my phone so much and i need it asap thank you.
same problem with me.
but in my case, the phone not only freeze after the google logo before boot. I tried several times to pull the battery and start the phone again, it took several times until the phone can boot normally again.
After that, my nexus s can work as usual. but it only takes 3-4 hour until it freeze/hangs or reboot automatically and show image of green robot lay down with red alert triangle...
sometimes I noticed all application force closed like gmail, gtalk, etc. (its a basic apps instead of 3rd party app)
History :
- root GB 2.37 using superoneclick
- upgrade OTA to ICS 4.04
- problem happens
- root using guide : nexusshacks.com
- unroot using guide : nexusshacks.com
- back to factory setting on GB 2.34
- upgrade OTA to ICS 4.04
- Still got that problem.....
I'm using Nexus S 4G Sprint, pls help me guys...
nexus s won't boot
I had the same problem and read elsewhere that heating the phone with a hairdryer solves the problem.
I must say, indeed it did.
I removed the battery and the SIM card, then heated up the phone (so it really feels warm) put back the battery and sim and simsalebim the phone started again. and is still working since (now already a few day's)
It seems that a component in the phone is heat sensitive, the question in my mind is when will this show again and do I need to consider buying a new phone.
But sofar it works
PS I also tried hard reset factory reset the lot, but in the end only heating up helped.
Good luck, David
I fixed this problem! but I had to wipe all user data by rooting it using nexusrootICS. It finally boots up and the phone works now... that's all I need.
Hey,
My TF101 got bricked by a simple reboot - "encryption unsuccessful" splash screen.
I used the nvflash-package from the devel-section "[Tool] Nvflash unbricking released!" for getting back a fresh, clean install of 3.2.1, which seems to work well.
Sadly, no OTA-Update to ICS is found and no microSD-Update is recognized.
Wipe, another cold-boot tried.
Q:
nvflash repartition and format - thus there couldn't be hassle with my old "broken" Android, right?
Q2:Anyone has an idea why updates dont work? Within the thread mentioned above I found some posts about updates which where recognized.
Searched a lot but nothing specific to the nvflash image solution...
BR / Adarof
NvFlash the RougeXM touch recovery CWM and use that to flash a new ICS firmmware/ROM. That's probably the easiest route to take. You can flash total stock that overwrites the custom recovery if you'd like too. Should fix your ota problem too.
removed
Okay, I have flashed ww-9.2.1.11-CWM-full-rooted.zip.
Wipeing everything tried.
But still no updates...
I found http://forum.xda-developers.com/showthread.php?t=1655976, which are the same log-entries like I found
But no luck on googling further on
If you have anything but a stock recovery, you will not get an OTA. You need to here to get the stock recovery and flash it through CWR. Then when you boot to recovery, using the power+vol down wait to see the text at top right corner and then hit volume up, method, you'll see an android laying on his back with a ! above him. This is stock recovery. Should be able to push OTA through settings after this.
Wohu - Thanks, thats one of the very gernal infos I missed :-/
I tried your mentioned tutorial. The process itself seems to be fine.
But...still no updates (it takes ages for the 1st update-check and is very fast for the 2nd and ongoing checks)
I'm from Germany, thus I would expect to require a firmware and recoveryimage for DE but the tutorial just links a WW for firmware and just US for reecovery?
Well ... DE has gone to WW since .21, thus I tried ... but the process uses a repacked Android3, thus I should care about DE ?
Might this be the reason? Is there a repacked-CWM-enabled firmware-image with recovery for DE?
Thanks again so far!
BR / Adarof
adarof said:
Wohu - Thanks, thats one of the very gernal infos I missed :-/
I tried your mentioned tutorial. The process itself seems to be fine.
But...still no updates (it takes ages for the 1st update-check and is very fast for the 2nd and ongoing checks)
Click to expand...
Click to collapse
When the file goes to update, it will fail if there are any apps missing from /system/app that ASUS put in there. There is a checker that looks for these app. If you deleted any of these or any were deleted in the CWR version you flashed earlier, you'll have to replace them before the update will install.
adarof said:
I'm from Germany, thus I would expect to require a firmware and recoveryimage for DE but the tutorial just links a WW for firmware and just US for reecovery?
Click to expand...
Click to collapse
All you need from that link I posted above is the SURecovery image and nothing else. You can get the firmware.zips from Asus directly. The SURecovery is universal, meaning it will work no matter what region you are in. It is the ROM/Blobs that are region specific. Don't forget that if you download one from the Asus site, that you need to extract it first and then push the zip that was inside the original file you downloaded.
So it would look like this WW.zip->extract->firmware.zip<<<---This is your ROM
adarof said:
Well ... DE has gone to WW since .21, thus I tried ... but the process uses a repacked Android3, thus I should care about DE ?
Might this be the reason? Is there a repacked-CWM-enabled firmware-image with recovery for DE?
Click to expand...
Click to collapse
Not sure about these questions.
Woodrube said:
When the file goes to update, it will fail if there are any apps missing from /system/app that ASUS put in there. There is a checker that looks for these app. If you deleted any of these or any were deleted in the CWR version you flashed earlier, you'll have to replace them before the update will install.
Click to expand...
Click to collapse
Okay, I havent known this either...
Is there a list of asus-default installed apps? I havent found :/
Woodrube said:
All you need from that link I posted above is the SURecovery image and nothing else.
You can get the firmware.zips from Asus directly.
Click to expand...
Click to collapse
SURecoverty means the USRecovery.zip, right?
So, in summarize
1) Rogue XM Touch recovery via nvflash from http://forum.xda-developers.com/showthread.php?t=1446019
2) Use RogueXM to flash original asus-firmware (decompressed download archive)
3) Use RogueXM to flash USRecovery.zip from http://theunlockr.com/2011/11/28/how-to-unroot-and-remove-cwm-recovery-on-asus-transformer/
Am I right?
...on 2) I get
Code:
assert failed: write_raw_image("/tmp/blob","staging")
E: Error in /sdcard/WW_epad-user-9.2.1.24.zip
(Status 7)
Installation aborted.
...but I could install the repacked-8.2.3.13_WW+root-CWR-update(su_removed).zip.
I assume the RogueXM requires a blob-File within the zip, which is not provided by asus-original-downloads?
A bit confused ;-)
BR / Adarof
adarof said:
Okay, I havent known this either...
Is there a list of asus-default installed apps? I havent found :/
Click to expand...
Click to collapse
That is a tough one. i would suggest looking at the OP's for the custom ROMs and see if the have an Add-on pack that will put them in their custom ROMs. That way you'll be able to extract the apps from them and push to /system/app on your own (don't forget to set permissions also on the ones you push). If not, I will see if I can pull them from mine, zip them up and them send a link to you, but that won't be until I 1 get home and 2 get some time which unfortunately won't be tonight.
adarof said:
SURecoverty means the USRecovery.zip, right?
Click to expand...
Click to collapse
Yes sorry about that. I was typing too fast. :/
adarof said:
Am I right?
...on 2) I get
Code:
assert failed: write_raw_image("/tmp/blob","staging")
E: Error in /sdcard/WW_epad-user-9.2.1.24.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
This is the 3rd Status 7 I have seen today from someone. The other two were in my phone forums and it is bc of a mismatched CWR version. In my phone forum, they just needed to flash a different kernel. Not sure what is going on with it here, but see below...
adarof said:
...but I could install the repacked-8.2.3.13_WW+root-CWR-update(su_removed).zip.
Click to expand...
Click to collapse
If you can get this far, then NVflash this and get it to boot up completely. That way you shoudl have all the /system/apps anyways. You can root it (if you lose it somehow) with Razerclaw since it is HC.13 (if you accidentally update all the way to ICS .11 without rooting, you can use ViperMod or any of the other root tools out there) Remember that once you root it, you can use OTA Rootkeeper to preserve your Root status, accept the OTA and then restore Root (this is what I have done since HC). Then install this app and flash the USRecovery.zip and you should be good to go. Reboot to full boot up and then try to reboot into recovery using Key Combo. It should throw the Android on his back with ! above him.
I would then uninstall the Recovery Installer to make sure you don't accidentally hit it and you are back where you started. But you'll have the APK to reinstall whenever you want later on.
Sorry for the long post, just trying to cover everything bc I have log out for a bit and won't be on until later on. Maybe Thing O Doom will swing through, though.
Edit::: Check this out too.
Woodrube said:
That is a tough one. i would suggest looking at the OP's for the custom ROMs and see if the have an Add-on pack that will put them in their custom ROMs.
Click to expand...
Click to collapse
Well, Ok...since I "just" would like to have back a real stock system, with OTA - there should be another way ;-)
Woodrube said:
This is the 3rd Status 7 I have seen today from someone. The other two were in my phone forums and it is bc of a mismatched CWR version. In my phone forum, they just needed to flash a different kernel. Not sure what is going on with it here, but see below...
Click to expand...
Click to collapse
Okay! This explains why I cant find any 1000000 hits on google related to my prop, which seems to me rather "simple" in principle ;-)
Woodrube said:
If you can get this far, then NVflash this and get it to boot up completely. That way you shoudl have all the /system/apps anyways.
Click to expand...
Click to collapse
Agreed...apps should be there. But even the Asus storage app was missing? Thus no stock-apps included?
Its an old Andoroid 3.0.1 and it wouldn't find OTA updates - thats correct?
Woodrube said:
Then install this app and flash the USRecovery.zip and you should be good to go. Reboot to full boot up and then try to reboot into recovery using Key Combo. It should throw the Android on his back with ! above him.
Click to expand...
Click to collapse
Okay, while Power-VolDown -> VolUp (this gave me Rogue XM before but since I installed USRecovery it was overwritten, right?) -> a Droid on its back with a "!" comes up.
...and now?
The .24 update on SDCard is recognized but when I try to install the knocked-out droid with "!" comes on reboot again and next reboot yields to a popup "failed update, reverted to old system" or so.
Woodrube said:
Sorry for the long post, just trying to cover everything bc I have log out for a bit and won't be on until later on. Maybe Thing O Doom will swing through, though.
Click to expand...
Click to collapse
THANKS for your time so far and dont stress anything
I really appriciate it! Im feeling lost on android...even I work with Linux/Unices since a decade or so :-/
Woodrube said:
Edit::: Check this out too.
Click to expand...
Click to collapse
Thats a Win-solution :-/
Most propably I need a stock DE .21 or WW .24 , repacked for flashing with CWM ... right? But that doesnt exists?!?! Cant imagine...
BR - Adarof!
Im still on this problem and have no idea - searched a lot, but havent found any real howtos for DE-tf101 for unbricking.
So my main thoughts are about this Error7, which is really ...strange.
I could flash the repacked, which is available for .11. But I dont have a change to get anz further...
I SHOULD be able to flash a original asus stock Firmware with the Rogue XM Touch recovery, right?
Since Im not able to ... should I try an older version of Rogue XM?
BTW: Is the region info somewhat hard-wired thus it couldnt be changed?
BR - Adarof
There's a WW .24 available for tf101 and I'm making a 9.2.2.6 for the Tf101G,
so there is the latest FW available.
If you are flashing, then that means you have a custom recovery. That is why no OTA.
I'm mobile now but IIRC from before, you flash a working CWR version of the ROM. Thne boot up. Then flash the stock recovery. Then you should be able to OTA after that.
Just make sure whatever ROM you flash is full. If you can nvflash that would be better and then put stock recovery in after your first boot.
Thanks to both of you!
@Woodrube: Flashing means using RogueXM...
Summary:
1) Rogue could flash me either CWR/rooted images or the repacked one - both without OTA.
Just RogueXM is left as bootloader, which shouldnt prevent OTA?!
2) Rogue gives Error7 on flashing the asus-downloaded-onetime-depacked-firmwares, doesnt matter if the DE.21 or current WW.24. :-/
Trying to make the long story short:
For comming back to a "known" system I would like to really go back to a stock system.
I conclude that using nvflash would be the best for this, right?
But where do I get the img-Files for flashing using nvflash?
I just found one package which included a download.sh: It repartitioned, formated and installed a WW android3 (3.2.1) version and deleted the RogueXM. It mentioned its a stock firmware (thus should have all apps).
Sadly no updates afterwards...
I think it could be since its the WW version and I would need a WW .21/.24 (since 21/24 dont distinguish DE and WW anymore) or an older DE-version. But for nvflash I need the img files of these firmwares, which I dont find. ...
Maybe you could simply point me to such img files for nvflash, please?
BR / Adarof
Finally I managed to borrow a win pc and thus could give EasyTool of your posting #8 a try: http://forum.xda-developers.com/showthread.php?t=1688012
After some hassle with the driver I managed to flash asus stock download DE_epad-user-9.2.1.21, which is "DE_Special" for coming to WW of german tf101s. the tf was wiped and boots just fine - it states that it has
IML74L.WW_epad9.2.1.21-20120413 - as I think is fine.
Sadly no update again:
The OTA doesnt find any.
The microSD recognizes WW_epad-user-9.2.1.24.zip, but during rebooting I get the Droid with ! and after another reboot a popup with something like "update failed (12)" (in german Systemaktuallisierung fehlgeschlagen (12)). It mentiones that the new version in not compatible ...but ....the .24 is for the DE_special .21 the next ... ?!
I could flash the .24 using Easytool, but this would mean to loose always all data for an update ....
Installing rogue still gives error7 on flashing stock (once decompressed) .zip
I've been reading and Rouge gives errors with stock otas X.x
You can manually install the stock blobs with adb shell, but they will overwrite recovery and etc..
If you want total stock you need to NvFlash, and for whatever reason your tf does NOT like updates.
Rouge V1.3 will take otas, if you don't mind the downgrade.
Thanks for the hint - but I was to lazs to install the rogue 1.3.
I found a .zip, which I tried to install by Rogue 1.5 hoping for a downgrade overall, but during installation it stated "Returning to recovery" and still 1.5 was installed .
What I finally found is a ww-9.2.1.21-to-9.2.1.24-CWM-v1.0.zip image.
I installed this using rogue 1.5 and got a clean .24 installation.
So I'm using this installation hopeing either
1) OTA will work, if asus releases .24++ or
2) I find an ww-9.2.1.24-to-9.2.1.24++
Still I dont get why the EasyTool .21 installation yields to a non-OTA state ... but ...
So, THANKS all of you for your support and hints!
I'll come back here and report further on, if .24++ is out
BR / Adarof
bad luck
....meanwhile my tf101 has started to ignored the dock battery, while the keyboard still works. I tried cleaning ....no luck, the dock battery does not come up within the menues ...
Thus it was returned and I'm waiting for repairing or refunding ...
BR / Adarof
TF300t infinite reboot loop on asus screen after installing "THe ultra fast rom"
HI
I wanted to try out a new ROM for my TF300t. I ended up trying the ultra fast rom by surdu_petru. I did as he told, downloaded the 300 something mb file and copied it on to my device. I have bootloader unlocked, rooted and previously had CleanRom installed. I wiped cache and dalvik cache. Install took a while, but finally when it was done, i rebooted the device. It was stuck on the asus logo for a while, until it rebooted and so on and so on. There is NO use holding down the power button, it just keeps going. Iv tried power+volum+ and -. I am not very expirienced with this so i have no idea whats going on, its like an infinite boot loop.
I noticed something right after install that said unable to mount something..... I was in a hurry so i did not really care about it.
Any help would be apriciated.
EDIT!!
I feel like this thread is a bit messy, but here is where i am.
I am able to get into fastboot. I am also able to get into recover (TWRP). I have 1 backup of the official and stock 4.1.1. Should i install it, or should i try again the ultra fast ROM, as i am curious about why it failed. I also have my CleanROM.zip on my device. This is the first time something like this is happening to me, so im trying to learn from my mistakes ^^
EDIT, seems like i was not trying hard enough to get into fastboot, got in, just had to be quick enough. (PHEW) Now what?
Hi.
I'm stuck in the white asus logo. I don't know if it's the same problem you have, is it? I dont' know what to do
zephiruspt said:
Hi.
I'm stuck in the white asus logo. I don't know if it's the same problem you have, is it? I dont' know what to do
Click to expand...
Click to collapse
HI, if it keeps rebooting, hold down the power until it goes black, then release it. Quickly after hold down powerbutton+volum down. You should then be in fastboot. If you manage to get into fastboot, normally there should be no worries. As im kind of noob myself im not going to tell you what to do, as it might just make things worse. Try to wait for someone who knows this stuff to answer
Hey, thanks!
I already done that and I get to these 4 icons/options. The only thing I can do is going to Recovery mode (menu with options to install rom from zip, etç...) I can't do nothing more. Is this what you're saying? Can I just install a rom and it will work???
zephiruspt said:
Hey, thanks!
I already done that and I get to these 4 icons/options. The only thing I can do is going to Recovery mode (menu with options to install rom from zip, etç...) I can't do nothing more. Is this what you're saying? Can I just install a rom and it will work???
Click to expand...
Click to collapse
First off, what recovery are you using? (TWRP, CWM?) Secondly, have you made a backup of a working ROM that you have been using? If so, you should be able to get into recovery and flash it. (As i said, you SHOULD wait for some pros, im not very expirienced with this!!!!! and i might be wrong).
grimsonfart said:
First off, what recovery are you using? (TWRP, CWM?) Secondly, have you made a backup of a working ROM that you have been using? If so, you should be able to get into recovery and flash it. (As i said, you SHOULD wait for some pros, im not very expirienced with this!!!!! and i might be wrong).
Click to expand...
Click to collapse
I have CWM. I don't have any backup but I was going to try to install this one: http://forum.xda-developers.com/showthread.php?t=1893714
zephiruspt said:
I have CWM. I don't have any backup but I was going to try to install this one: http://forum.xda-developers.com/showthread.php?t=1893714
Click to expand...
Click to collapse
There is your problem! The ROM can only be installed using TWRP. I suggest you try out a ROM like the new Cyanogenmod 4.2, as it seems to only support CWM (i might be wrong).
Link for the ROM: http://forum.xda-developers.com/showthread.php?t=2055430
Be sure to read CAREFULLY trough the description so you are sure that you have everything needed etc.
Good luck
grimsonfart said:
There is your problem! The ROM can only be installed using TWRP. I suggest you try out a ROM like the new Cyanogenmod 4.2, as it seems to only support CWM (i might be wrong).
Link for the ROM: http://forum.xda-developers.com/showthread.php?t=2055430
Be sure to read CAREFULLY trough the description so you are sure that you have everything needed etc.
Good luck
Click to expand...
Click to collapse
Hmm. I just got the one I said installed. What do you mean by "The ROM can only be installed using TWRP"? At the moment, because I tought I bricked my tablet, I just want to put it as it came when I bought it but of course I'm open to try other ROM's.
zephiruspt said:
Hmm. I just got the one I said installed. What do you mean by "The ROM can only be installed using TWRP"? At the moment, because I tought I bricked my tablet, I just want to put it as it came when I bought it but of course I'm open to try other ROM's.
Click to expand...
Click to collapse
The ROM you tried to install can only be installed using TWRP, not CWM recovery as you are using. Thats why (i think) you got stuck after install. I recommend you install TWRP, because as far as i know its better than CWM. Just go the developement section and you should find it there.
So I accidentally wiped the internal Storage on my XT925 RAZR HD, before flashing because well I'm silly.
Now, I can boot into fastboot, and recovery, but I dont know how to get the phone into a state where I am able to use adb push to move the .zip with the new ROM onto my device so I can flash it with recovery,
have been searching for a while now but to no avail,
I dont expect a direct answer but maybe someone can point me in the right direction.
Any and all help Appreciated!
You can flash back stock fw and start from scratch-probadly not the preferred route but you will probadly have it done before you get the response your hoping for
jmcdonald58 said:
You can flash back stock fw and start from scratch-probadly not the preferred route but you will probadly have it done before you get the response your hoping for
Click to expand...
Click to collapse
Thats the thing I've tried flashing back to stock but it encounters an error and fails out , so that option unfortunately is out, I think I may just have to go buy a MicroSD card tomorrow and copy the new ROM that way
I used this toolkit to flash fw on my xt925 and it worked flawless in fastboot if you can get the rom on the pc etc, its worth a shot
http://forum.xda-developers.com/showthread.php?t=2154995
jmcdonald58 said:
I used this toolkit to flash fw on my xt925 and it worked flawless in fastboot if you can get the rom on the pc etc, its worth a shot
http://forum.xda-developers.com/showthread.php?t=2154995
Click to expand...
Click to collapse
Thank you so much, I had already downloaded my default carrier image, and this tool worked great ran it and it reset my phone to factory!
Thank you so so much.
CraigDav said:
Thank you so much, I had already downloaded my default carrier image, and this tool worked great ran it and it reset my phone to factory!
Thank you so so much.
Click to expand...
Click to collapse
Your welcome glad it worked out for you and I was able to help all credit to OP of toolkit for sharing :highfive:
hello everyone,
i'm developing a game with unity and sometimes when i compile and inject the game on the phone it crashes and forces me to factory reset the phone through fastboot. i've done it like 3 times already with no problems.
but today it happened again and the phone just wouldnt recover, i've tried the fix that this video (youtube.com/watch?v=laU6NQ0LxR0) shows but it still does not boot.
I am able to enter fastboot and my computer recognizes the mobile phone so that's a great start :victory:
not sure what guide to follow since i'm not sure whether the problem is on the rom or something else.
can someone give me a tip on what fix should I try? cant really afford to lose my phone right now
it has (had) a stock rom 4.4.2 with stock bootloader, tho i tried to install the fix in the video i've said earlier and i'm not sure whether it changed the rom or not.
thanks
pewtel said:
hello everyone,
i'm developing a game with unity and sometimes when i compile and inject the game on the phone it crashes and forces me to factory reset the phone through fastboot. i've done it like 3 times already with no problems.
but today it happened again and the phone just wouldnt recover, i've tried the fix that this video (youtube.com/watch?v=laU6NQ0LxR0) shows but it still does not boot.
I am able to enter fastboot and my computer recognizes the mobile phone so that's a great start :victory:
not sure what guide to follow since i'm not sure whether the problem is on the rom or something else.
can someone give me a tip on what fix should I try? cant really afford to lose my phone right now
it has (had) a stock rom 4.4.2 with stock bootloader, tho i tried to install the fix in the video i've said earlier and i'm not sure whether it changed the rom or not.
thanks
Click to expand...
Click to collapse
What about following this guide?
Landrea said:
What about following this guide?
Click to expand...
Click to collapse
got stuck here :/
dropbox.com/s/d3s378e9pvxs0ab/Screenshot%202014-03-30%2023.17.12.png
pewtel said:
got stuck here :/
dropbox.com/s/d3s378e9pvxs0ab/Screenshot%202014-03-30%2023.17.12.png
Click to expand...
Click to collapse
Have you configured the drivers on your pc? The phone is recognized? It looks like the pc can't dialogate with it
Sent from my Commodore 64 using Videotel
Landrea said:
Have you configured the drivers on your pc? The phone is recognized? It looks like the pc can't dialogate with it
Sent from my Commodore 64 using Videotel
Click to expand...
Click to collapse
the phone is recognized as motorola adb interface, i even re-installed the drivers. now trying a different rom but i'm pretty sure the ROM is not the issue
*edit: yep, still waiting for device even with different ROM
modaco.com/topic/366786-how-to-flash-to-the-standard-uk-rom/
:victory: :victory: :victory:
this worked for me,
posting the link just in case someone encounters the same problem. thanks
pewtel said:
modaco.com/topic/366786-how-to-flash-to-the-standard-uk-rom/
:victory: :victory: :victory:
this worked for me,
posting the link just in case someone encounters the same problem. thanks
Click to expand...
Click to collapse
Thank you for sharing
/Data gets corrupted
Even, I had the same issue. I tried flashing ROMs through recovery but it gave me error that/data/media/0/ can't be mounted. The only way to get out I found was to full format /data and /storage (philz recovery) and then to push ROM. zip to/sdcard through adb and then to flash it through recovery.
Hope it helps someone.:angel: