Related
OK, i searched and found some threads on the matter but that was for the Prime. also found some other issues with the unlocker dealing with an un-recognized serial number or no data connection.
anyway, a little about my tablet. purchased it from a friend, brand new, sealed in box. serial numbers match (between box and device) i rooted right away since i was on the .17 firmware, did the OTA root keeper thing. the OTA was pushed to my device that same day, it updated just fine. a couple days later the .30 update was pushed to my device...took that as well just fine. so i was running stock .30 firmware but was rooted. I tried the unlock tool in that state, and got the message below. so i started reading and saw a reset could fix it...so i did that.....no dice.
did a "cold reboot" (volume down and power until the message pops up and just let it time out for the 10 seconds to clear caches and what-not.)
tried again....Nothing.
i have tried it while tethered to my Nexus, and connected to my home wi-fi with no luck.
what is my next step? should i downgrade to .17 and give it another go? is this possible without a computer (at work and would like to do it today)
is this just an ASUS server issue and just "bad timing" to unlock...or does this go deeper than that?
thanks for all your help....pulling out my hair trying to figure this out.
its a problem with your serial not been in the asus database. Call Asus and tell them that update is not working, don´t tell them that you want to unlock.
They will put your serial in their database. Then try unlock again.
Except, he got an OTA already.
I would recommend downgrading to .17 since some people have had success with that.
EndlessDissent said:
Except, he got an OTA already.
I would recommend downgrading to .17 since some people have had success with that.
Click to expand...
Click to collapse
that was my thoughts....i though the serial number issues also affected the OTA's being pushed.
can downgrading be one on the tablet alone?
i though i read on the TF prime site that you can download the built, extract the .zip file from the .zip you download from asus, plop it on the root of an sd card (internal storage or external SD? i have both available) then turn off, volume down + power and hit volume down, then volume up and it will install that....is this correct?
or do i need to do it though ADB?
turdbogls said:
that was my thoughts....i though the serial number issues also affected the OTA's being pushed.
can downgrading be one on the tablet alone?
i though i read on the TF prime site that you can download the built, extract the .zip file from the .zip you download from asus, plop it on the root of an sd card (internal storage or external SD? i have both available) then turn off, volume down + power and hit volume down, then volume up and it will install that....is this correct?
or do i need to do it though ADB?
Click to expand...
Click to collapse
Yeah, I think that's how it works. When I downgraded to .17 to root way back when, I used Wolf's method, which used ADB. I think either way will work fine.
OK, can anyone confirm or post a link or something to the exact method of an "on the device" downgrade method.
the only things i am finding online are Wolf method which involves ADB.
can i simply put the .zip or blob (which one?) on the root of internal memory.
turn off tablet
hold volume down +power
hit volume down
then volume up
and it will install the .17 system?
I am working late tonight with no access to my home computer for the next couple of days probably
ok, i actually got of work early and was able to downgrade via ADB. i am on stock .17 firmware right now doing a factory reset and then i will be giving it a go one more time.
edit: Annnnd....it didnt work >)
Damn. The worst part is that Asus refuses to help people in your situation. All I can suggest now (hopefully someone can suggest something better), is to try everyday, at least once. Some people get it to work like that.
I really wish I could help more. The most trouble I had with unlocking was signing into my Google account (I have 2-step authentication). I was on .30 rooted, and it worked perfectly. I know that's not what you want to hear. I just have no idea why it would work fine for some people and not work for others. The serial number issue was bad enough, but now, people with working serials can't use the unlocker? That's preposterous, and Asus needs to fix it.
Well....what can ya do. I am going to call Asus tomorrow and see if they can verify my SN is in the database.
I'd I can unlock...great!
If I cant , well I will still enjoy my rooted tf300 and wait patiently for my JB OTA.
I hope you get it sorted out. Knowing Asus, though, even if they don't help you, the official update should be ready shortly. Possibly before there's a stable CM10 available.
EndlessDissent said:
I hope you get it sorted out. Knowing Asus, though, even if they don't help you, the official update should be ready shortly. Possibly before there's a stable CM10 available.
Click to expand...
Click to collapse
I hope you are right....I dont expect it to be before a stable CM10 is released....but i do have high hopes to see it before the end of August.
FWIW, i am back on stock .30 rooted sofware. back at square 1
but i will be trying the unlock tool every day until JB arrives or it works...lol
also contacted ASUS (e-mail) about the issue, they told me to factory reset and see if that worked.....hope they can help me out even more when replying to my reply.
mikaole said:
its a problem with your serial not been in the asus database. Call Asus and tell them that update is not working, don´t tell them that you want to unlock.
They will put your serial in their database. Then try unlock again.
Click to expand...
Click to collapse
And don't say your serial is not in the database, cuz the only way to know that is
when trying to unlock!
Saintom said:
And don't say your serial is not in the database, cuz the only way to know that is
when trying to unlock!
Click to expand...
Click to collapse
lol
I'll give them some BS about a neighbor having the same issue and having them enter it into thier database fixed it.....that should work.
the announcement of an almost complete (BT and camera dont matter to me) AOKP JB build has me making this call in about an hour. I want this done SOOOO bad now
OK, so i called them with some BS about not getting updates and asked them to put my number in their "system"
the guy said that my SN was in there now.
still no dice on the unlocker app.
how long does it take to become "activated" in their system. should i be waiting a day before expecting results?
still nothing today...anyone else get this message and have it resolved?
i read a thread where a bunch of people are getting the same error (over on the TF Prime forums) it just wasn't working for some reason...then one day, boom, it started working again.
so maybe it is something on ASUS' end and they either shut it down or it just isn't working right now.
anyone successfully unlock their device in the last week?
turdbogls said:
anyone successfully unlock their device in the last week?
Click to expand...
Click to collapse
I had this exact issue and resolved it by doing a 'factory reset' on it, then reinstalling the tool. At the time, I was stuck on FW 17 and wasn't getting updates from Asus, so unlocking and flashing a different ROM was the way to go in order to keep ROOT.
Haven't looked back since (currently on AOKP's JB build and loving it).
bsaman said:
I had this exact issue and resolved it by doing a 'factory reset' on it, then reinstalling the tool. At the time, I was stuck on FW 17 and wasn't getting updates from Asus, so unlocking and flashing a different ROM was the way to go in order to keep ROOT.
Haven't looked back since (currently on AOKP's JB build and loving it).
Click to expand...
Click to collapse
I hate you for being able to do it so easy...lol
i have unrooted, i have factory reset a couple times, i have downgraded to .17 and factory reset then...nothing
I WAS getting OTA's though. so i guess i am just going to have to wait for official JB...i would love to be running AOKP JB on my 2 main devices.
Did you manage to get this working?
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
:crying:
Hello there!
I have a really serious problem with my TF300T. I had the newest bootloader installed with 4.4 enabled TWRP recovery. I had the 2014.01.07. CM 11 nightly installed and was running fine. I have seen, that there are some never releases so decided to update. I downloaded the newest nightly yesterday and pressed power button. Selected reboot and then selected Recovery.
And here comes the problem!
The tablet bricked himself! It did restart but got into a bootloop I cannot get through the Asus splashscreen. I tried POWER+VOLD DOWN, I cannot get into fastboot or recovery. The tablet keep rebooting, no boot to android either. I tried power off, no success. I tried the reset button. I removed battery, still the same.
As I have never done anything to the bootloader, I did not consider making NVFLASH backup, as it is a risky operation. Shame on me...
How could it happen????? Does cyanogenmod alter Bootloader partition to reboot into recovery??? What the hell??
Please help me somehow! I dont know what to do, I tried all I could! Maybe APX? or only Asus RMA??
yours,
dpeti said:
:crying:
Hello there!
I have a really serious problem with my TF300T. I had the newest bootloader installed with 4.4 enabled TWRP recovery. I had the 2014.01.07. CM 11 nightly installed and was running fine. I have seen, that there are some never releases so decided to update. I downloaded the newest nightly yesterday and pressed power button. Selected reboot and then selected Recovery.
And here comes the problem!
The tablet bricked himself! It did restart but got into a bootloop I cannot get through the Asus splashscreen. I tried POWER+VOLD DOWN, I cannot get into fastboot or recovery. The tablet keep rebooting, no boot to android either. I tried power off, no success. I tried the reset button. I removed battery, still the same.
As I have never done anything to the bootloader, I did not consider making NVFLASH backup, as it is a risky operation. Shame on me...
How could it happen????? Does cyanogenmod alter Bootloader partition to reboot into recovery??? What the hell??
Please help me somehow! I dont know what to do, I tried all I could! Maybe APX? or only Asus RMA??
yours,
Click to expand...
Click to collapse
No, sorry, you won't be able to use APX mode without have making the NvFlash backups beforehand.
is this possible? I'm now afraid to update to newer cm11 versions...
aplopeanu said:
is this possible? I'm now afraid to update to newer cm11 versions...
Click to expand...
Click to collapse
Yeah, Ive seen it happen to multiple people across the forums idk what the actual bug is though.
cmendonc2 said:
Yeah, Ive seen it happen to multiple people across the forums idk what the actual bug is though.
Click to expand...
Click to collapse
so basically ... don't update CM11 until this is fixed right?
aplopeanu said:
so basically ... don't update CM11 until this is fixed right?
Click to expand...
Click to collapse
Im not sure It only happened to a few people in addition to OP of this thread. Im not upgrading to be safe, but maybe the dev should look into it.
cmendonc2 said:
Im not sure It only happened to a few people in addition to OP of this thread. Im not upgrading to be safe, but maybe the dev should look into it.
Click to expand...
Click to collapse
Yea I'm doing the same thing...btw if you birck it...changing the motherboard will unbrick it?
aplopeanu said:
Yea I'm doing the same thing...btw if you birck it...changing the motherboard will unbrick it?
Click to expand...
Click to collapse
In theory, yes. But many people consider it easier to RMA it.
cmendonc2 said:
In theory, yes. But many people consider it easier to RMA it.
Click to expand...
Click to collapse
RMA?
aplopeanu said:
RMA?
Click to expand...
Click to collapse
Send it back to Asus and pay the repair costs.
I knew this day would come, I've traded PC trouble shooting for tablet troubleshooting. My son's tf300 gets to the screen where circles/dots go round and round and never gets any further. I am trying to learn everything I can and try everything I can before doing the wipe and starting over...as he has pictures and videos he'd like to save, and of course the all important saved game/app data...LOL. Anyway I'm new to tablets relatively speaking, but I've tried the volume down, and power button for doing a cold boot, same result. I've tried going to the recovery option just to see what that was about, and all I get is a flash of a screen saying something like updating android version or something like that and then the dead android with the usual red triangle and eventually the device will restart itself. I should that to him and told him he killed the android which gave me a puzzled look and then a smile...Anyway, you can't turn off the device nohow noway, except letting the battery drain completely.
I've been reading a little and learning about roots, backups, recoveries, etc... trying to come up with a plan of attack but feel like I'm spinning my wheels. Any advice here? and Can I access via PC to USB to device and just pull off his pics and videos to copy back over to the device after a wipe?
Problem started...I think when he ran the power dead completely and then had to restart...nor sure though... memories of a child are sketchy at best.
Feedback
chromegsx said:
I knew this day would come, I've traded PC trouble shooting for tablet troubleshooting. My son's tf300 gets to the screen where circles/dots go round and round and never gets any further. I am trying to learn everything I can and try everything I can before doing the wipe and starting over...as he has pictures and videos he'd like to save, and of course the all important saved game/app data...LOL. Anyway I'm new to tablets relatively speaking, but I've tried the volume down, and power button for doing a cold boot, same result. I've tried going to the recovery option just to see what that was about, and all I get is a flash of a screen saying something like updating android version or something like that and then the dead android with the usual red triangle and eventually the device will restart itself. I should that to him and told him he killed the android which gave me a puzzled look and then a smile...Anyway, you can't turn off the device nohow noway, except letting the battery drain completely.
I've been reading a little and learning about roots, backups, recoveries, etc... trying to come up with a plan of attack but feel like I'm spinning my wheels. Any advice here? and Can I access via PC to USB to device and just pull off his pics and videos to copy back over to the device after a wipe?
Problem started...I think when he ran the power dead completely and then had to restart...nor sure though... memories of a child are sketchy at best.
Click to expand...
Click to collapse
I have a solution, but your not going to like it, all data will be lost....:crying:
1. Download the latest version of Android for your tablet. Make sure you download the correct SKU version.
A. To find the SKU, go into settings, About tablet, and look for your Build Number, There are two letters (such as US,WW, TW, etc.) that is your SKU. When downloading the zip from ASUS', you must download the correct SKU zip.
2. Decompress downloaded .zip file (it will be another .zip)
3. Rename it to:
A. For the TF700 and TF300: EP201_768_SDUPDATE.zip
B. For the TF101: E101_SDUPDATE.zip
4. Make sure your MicroSD card is formatted Fat32. It must be Fat32 Format or it will not work.
5. Copy the file to (the root directory of) your MicroSD
6. Insert the MicroSD into the tablet
7. Shutdown (power off) the tablet
8. Power it on by pressing and holding VOLUME DOWN and POWER buttons simultaneously
9. When you see white text in the top left corner of the screen, release the buttons ^^ and press VOLUME UP button (on RCK, this is your recovery which should already be selected) until you see Android logo and process bar
10. Give the update process 5-10 minutes. It should not take longer than that. If it happens to run for more than 45 minutes to an hour, force shut down the tablet and see if it boots. If it does not, try rerunning steps 7-9.
Let me know if you need any help along the way.... Thx as always lj
lj50036 said:
I have a solution, but your not going to like it, all data will be lost....:crying:
...
Let me know if you need any help along the way.... Thx as always lj
Click to expand...
Click to collapse
So the RCK thing doesn't do anything unless you have SD card in to do something that's on the card?
And there's no way to access what's on the device without getting it booted all the way?
Sounds like your saving me and my son from updating from his original Android version after a wipe...Thanks
SKU
chromegsx said:
So the RCK thing doesn't do anything unless you have SD card in to do something that's on the card?
And there's no way to access what's on the device without getting it booted all the way?
Sounds like your saving me and my son from updating from his original Android version after a wipe...Thanks
Click to expand...
Click to collapse
Yes the tablet having a locked bootloader... You can only flash signed zip files...From the SDcard
When your on that screen with the RCK.. NEVER select the WIPE DATA.. Bad things will happen...
Also when your in the RCK screen.. That is called the bootloader screen....So you know if some one refers to it by its name.....
Also that is were you can find your SKU on the bootloader screen upper left in white letters... WW, US, TW ............... Make sure you get the right SKU from asus for your 300....
lj50036 said:
Yes the tablet having a locked bootloader... You can only flash signed zip files...From the SDcard
When your on that screen with the RCK.. NEVER select the WIPE DATA.. Bad things will happen...
Also when your in the RCK screen.. That is called the bootloader screen....So you know if some one refers to it by its name.....
Also that is were you can find your SKU on the bootloader screen upper left in white letters... WW, US, TW ............... Make sure you get the right SKU from asus for your 300....
Click to expand...
Click to collapse
Hey congrats on Recognized Contributor!
Happy
cmendonc2 said:
Hey congrats on Recognized Contributor!
Click to expand...
Click to collapse
I am happy about it.. Still so much to learn... Im not trying to let it go to my head...LOL:silly:
lj50036 said:
... NEVER select the WIPE DATA.. Bad things will happen...
Click to expand...
Click to collapse
As far as I know it's related only to custom recovery and if You have stock one it should work. Or I'm wrong?
Data Wipe
Graiden05 said:
As far as I know it's related only to custom recovery and if You have stock one it should work. Or I'm wrong?
Click to expand...
Click to collapse
Yes that is correct. I just like to move people away from even thinking its an option, as I have had people with stock everything and the Wipe Data
icon has even given them trouble, its just not worth touching....LOL...Thx as always lj
lj50036 said:
Yes that is correct. I just like to move people away from even thinking its an option, as I have had people with stock everything and the Wipe Data
icon has even given them trouble, its just not worth touching....LOL...Thx as always lj
Click to expand...
Click to collapse
Yep when I first got my tablet i was so scared about going into that menu because I learned that it was only 3-4 clicks away from a brick.
lj50036 said:
Yes the tablet having a locked bootloader... You can only flash signed zip files...From the SDcard
When your on that screen with the RCK.. NEVER select the WIPE DATA.. Bad things will happen...
Also when your in the RCK screen.. That is called the bootloader screen....So you know if some one refers to it by its name.....
Also that is were you can find your SKU on the bootloader screen upper left in white letters... WW, US, TW ............... Make sure you get the right SKU from asus for your 300....
Click to expand...
Click to collapse
Out of curiousity...Isn't doing these steps more or less just upgrading the firmware? Like getting an update from ASUS? If so, why will it lose all the data?
I haven't mustered up the courage yet to do this yet... actually it's more like getting the time to do it.
Feedback
chromegsx said:
Out of curiousity...Isn't doing these steps more or less just upgrading the firmware? Like getting an update from ASUS? If so, why will it lose all the data?
I haven't mustered up the courage yet to do this yet... actually it's more like getting the time to do it.
Click to expand...
Click to collapse
Yes, that is correct..but its not a ota.... So the process will wipe all data....Thx always lj
You could try using ADB to try and pull your files. I faced a similar problem and was able to pull some of my files:
http://forum.xda-developers.com/showthread.php?t=2253834
Sent from my R800i using xda-developers app.
It's nice to be important, but it's more important to be nice.
UndisputedGuy said:
You could try using ADB to try and pull your files. I faced a similar problem and was able to pull some of my files:
http://forum.xda-developers.com/showthread.php?t=2253834
Sent from my R800i using xda-developers app.
It's nice to be important, but it's more important to be nice.
Click to expand...
Click to collapse
Read your link. I have adb downloaded and cannot get it to list my device. I cannot see my device in device manager like you though.
chromegsx said:
Read your link. I have adb downloaded and cannot get it to list my device. I cannot see my device in device manager like you though.
Click to expand...
Click to collapse
Try installing the universal naked drivers.
cmendonc2 said:
Try installing the universal naked drivers.
Click to expand...
Click to collapse
Same result. Still nothing in Device manager.
chromegsx said:
Read your link. I have adb downloaded and cannot get it to list my device. I cannot see my device in device manager like you though.
Click to expand...
Click to collapse
Apologies, I'm very rusty with this stuff now. If flashing a .blob file doesn't wipe data (I can't remember whether it does or not), perhaps you could try doing that if you're able to get into recovery?
Call me, Beep me, If you wanna reach me.
UndisputedGuy said:
Apologies, I'm very rusty with this stuff now. If flashing a .blob file doesn't wipe data (I can't remember whether it does or not), perhaps you could try doing that if you're able to get into recovery?
Call me, Beep me, If you wanna reach me.
Click to expand...
Click to collapse
I just gave in and did the flash procedure. Looked like it went well, now I'm watching the circles for round again for the last 10 minutes.
chromegsx said:
I just gave in and did the flash procedure. Looked like it went well, now I'm watching the circles for round again for the last 10 minutes.
Click to expand...
Click to collapse
Just wanted to follow up on this...lj50036 is top noctch helper here. going above and beyond does not even come close to explaining what he has tried to do for me. Ultimately it was after we hit a brick wall, that I suggested flashing back to an earlier version that finally worked. I'm not convinced flashing to the latest version (like I first tried) would not work, as I didn't personally create/rename the SD card to do the flash. but re-flashing the original firmware got the tablet to boot finally. Of course all was lost other than what had been automatically backed up via google servers. Pictures/videos back to exactly one year from when the pad stopped booting were recovered. Everything before a year was gone. No game data or installs were saved. I thought maybe it had to do with a space issue, but after re-installing every app my son had before and about 1GB worth of pics/videos restored, there is still 16GB left, I doubt game/user data would have consumed that much...so I still have no idea what might have cause the pad to stop booting. Other than it was trying to do something important when he ran the battery dead. So at this point I'm having my son clean out unwanted apps, and we are going to unlock and root after a proper backup is done. Thank you to all that have had input on my dilemma. I've learned a ton.
Hello I'm a user of a Sky Vega Iron (IM-A870)
And I need desperate help.
It's not an ordinary boot loop I wish it was, here's the story.
I rooted my phone just to let you know.
So I installed the wrong version of cwd recovery on my phone and so when I go into recovery mode the screen will turn like this.
imgurDOTcom/iOFieHG (sorry I can't you links yet cause I'm new)
But it wasn't a big deal I just didn't use it.
Now is the deal I decided to update my phone to stock kitkat that the vega devs supported themselves with vega station(the stock updating app)
And when it started installing it suddenly went into cwm.
I wasn't that worried at the moment just tried pulling the battery out and rebooting but...it started a boot loop.
I can't navigate cwm because of the way it is and I'm stuck. Is there another way to factory reset? or to get out of the loop?
Maybe a way to get rid of cwm and get back to stock recovery mode? Please help I need help until tomorrow! (personal reasons)
I searched online hours for solutions yet I can't find one.
Please help. I'm begging anyone out there.
Thank You
Cottyn said:
Hello I'm a user of a Sky Vega Iron (IM-A870)
And I need desperate help.
It's not an ordinary boot loop I wish it was, here's the story.
I rooted my phone just to let you know.
So I installed the wrong version of cwd recovery on my phone and so when I go into recovery mode the screen will turn like this.
imgurDOTcom/iOFieHG (sorry I can't you links yet cause I'm new)
But it wasn't a big deal I just didn't use it.
Now is the deal I decided to update my phone to stock kitkat that the vega devs supported themselves with vega station(the stock updating app)
And when it started installing it suddenly went into cwm.
I wasn't that worried at the moment just tried pulling the battery out and rebooting but...it started a boot loop.
I can't navigate cwm because of the way it is and I'm stuck. Is there another way to factory reset? or to get out of the loop?
Maybe a way to get rid of cwm and get back to stock recovery mode? Please help I need help until tomorrow! (personal reasons)
I searched online hours for solutions yet I can't find one.
Please help. I'm begging anyone out there.
Thank You
Click to expand...
Click to collapse
this seems like a bit of a pia, but it looks like the only way i can find. click the link under the video for detailed text instructions.
Thanks but failed
Thank you so much but it didn't work.
Thinking of going to a service center and getting it factory reset.
Think it'll work?
Cottyn said:
Thank you so much but it didn't work.
Thinking of going to a service center and getting it factory reset.
Think it'll work?
Click to expand...
Click to collapse
not sure, cant hurt to try.
bweN diorD said:
not sure, cant hurt to try.
Click to expand...
Click to collapse
Is there a way to factory reset by myself?
I have to fix it today but the service centers are closed for sundays.(once again personal issues)
Thank you again
Cottyn said:
Is there a way to factory reset by myself?
I have to fix it today but the service centers are closed for sundays.(once again personal issues)
Thank you again
Click to expand...
Click to collapse
you would need to get to one of 2 places, i thought you couldn't get to either, settings (from booted up) or recovery.
but factory resetting would only remove any data, it will not restore any files or fix your busted cwm.
bweN diorD said:
you would need to get to one of 2 places, i thought you couldn't get to either, settings (from booted up) or recovery.
but factory resetting would only remove any data, it will not restore any files or fix your busted cwm.
Click to expand...
Click to collapse
Oh so then factory resetting won't get me out of my boot loop?
Cottyn said:
Oh so then factory resetting won't get me out of my boot loop?
Click to expand...
Click to collapse
i cant say that for sure, all im saying is, factory reset does nothing more than wipe data.
if there is an issue in there causing your problem, then yes it will fix it. if your problem is caused by a software issue, then no it will not.
bweN diorD said:
i cant say that for sure, all im saying is, factory reset does nothing more than wipe data.
if there is an issue in there causing your problem, then yes it will fix it. if your problem is caused by a software issue, then no it will not.
Click to expand...
Click to collapse
Okay thank you for everything really
I've given up I think there's nothing I can do.
Next time I get a phone I'm not screwing with it
Cottyn said:
Okay thank you for everything really
I've given up I think there's nothing I can do.
Next time I get a phone I'm not screwing with it
Click to expand...
Click to collapse
lol, ok, no problem.
I feel the pain
Cottyn said:
Hello I'm a user of a Sky Vega Iron (IM-A870)
And I need desperate help.
It's not an ordinary boot loop I wish it was, here's the story.
I rooted my phone just to let you know.
So I installed the wrong version of cwd recovery on my phone and so when I go into recovery mode the screen will turn like this.
imgurDOTcom/iOFieHG (sorry I can't you links yet cause I'm new)
But it wasn't a big deal I just didn't use it.
Now is the deal I decided to update my phone to stock kitkat that the vega devs supported themselves with vega station(the stock updating app)
And when it started installing it suddenly went into cwm.
I wasn't that worried at the moment just tried pulling the battery out and rebooting but...it started a boot loop.
I can't navigate cwm because of the way it is and I'm stuck. Is there another way to factory reset? or to get out of the loop?
Maybe a way to get rid of cwm and get back to stock recovery mode? Please help I need help until tomorrow! (personal reasons)
I searched online hours for solutions yet I can't find one.
Please help. I'm begging anyone out there.
Thank You
Click to expand...
Click to collapse
I am going through a similar situation here. I was using Choi Mobil Recovery and was trying to flash a custom ROM. It's now in BootLoop and there is nothing I can do!
fakesoul said:
I am going through a similar situation here. I was using Choi Mobil Recovery and was trying to flash a custom ROM. It's now in BootLoop and there is nothing I can do!
Click to expand...
Click to collapse
what variant of vega iron you were using and what rom youre trying to flash?