Hey guys. Got a problem here. My Coby 7022(which I have read that the hardware is known for problems) will not wake up on sleep after a period of time, so im sending it back to get an exchange. My problem is....I could uninstall superuser, but cannot find out(and ive looked everywhere) how to go back to original recovery.If someone would be kind enough to give me their stock recovery dump and explain how to do it, id greatly appreciate it.
Any help would be appreciated as I need this done ASAP
Thanks,
Zacho56
I am going to "try" to help you.
1) you want to remove Superuser...that is easy. we can do it later.
2) you say you want to go back to stock recovery? are you using CWM now? FDWN or fastoot?
I will be around most of the day today. reply back soon
http://forum.xda-developers.com/showpost.php?p=14737017&postcount=34
Download the zip at bottom of post.
move it to your /root directory of your sd card.
make sure you have no other files named"update.zip"(if you do rename it to something else.zip)
change name of downloaded file to "update.zip"
in settings/about phone or about device you should see an option to update. press that. it will install the update.zip to you device.
please report back and let me know if this worked.
more information:
the stock recovery is <3e> your CPU is a telechips tcc8803. I am not sure what you have been using for a search but insted use tcc8803 .
some useful links
http://androtab.info/cyanogenmod/telechips/
http://forum.xda-developers.com/showthread.php?t=1119778
http://kyros-tablet-zone.team-talk.net/forum
every thing I have provided here is what I think you are asking for. I am unable to test files due to not having the 7022. I am mostly know the 7015....so...use them at your own risk. I will keep digging aaround and post any thing else that i think might help.
Hi guys..
I messed up.. I have a maybe-bricked Prime, which I've been trying "everything" to get back to life..
Doing to drove me to AndroidRoot Mobi's website
I followed their "Tegra3 Guide: nvflash" guide, and I now see that my bootloader has been changed.. Is there a way to change the bootloader back?
Because I learned that on the AndroidRoot-bootloader you cant flash Blob-files.. and I think I need to be able to do so to get my Prime back alive
Bump - Sorry for just bumbing, but please do anyone know about this?
Actually I just got a little clearer on my problem
I staged the NVFlash file, and ran the generator.. but I couldnt find a way to access the internal SDCard, so I had no clue where to recover the Blob-files.. so I dont have em backed up.
Does that mean that I'm in biiiig trouble, or can they be regenerated?
I have fastboot working
I have AndroidRoot - bootloader
I cant flash a recovery image succesfully, therefore I cant get into ADB
I have NO working rom on it, which was my problem in the first place.
Any help is appreciated
OMG! I'm not going into details on what I did, I'd just like to request the Stock ROM that came with it so I could restore my phone. It has android 4.1.2 and I just want to install it using the "Apply Update From sdcard." And if you must know, I edited the Build.prop file (The internet told me to.) And it messed up and wouldn't start up and got stuck in "Bootloop" so I tried factory reset and it didn't and I really need my phone because if I don't fix it I'll have to try to send it in to Huawei or T-Mobile or who ever. Plllllllz help.
Solution may be here soon.
No one has the stock rom on hand yet. We are working on building a custom recovery for the phone, so please be patient.
Hopefully we can have a working recovery by this weekend, then you will have a way to still access your phone.
What files did you mess up on your phone? If i know the files, I can get someone to upload the files and then you can push the files to your phone using adb. If you haven't yet, I would recommend unlocking your bootloader via the instructions here:
http://forum.xda-developers.com/showthread.php?t=2546455
By unlocking the bootloader, you will be eligible to test the custom recovery as soon as it is available. Also, list the foiles you messed up, so that we can possibly upload them for you.
It will be a while until someone can form a stock rom update.zip for you.
Also, you can view the progress that we are making on the custom recovery.
amamartin999 said:
OMG! I'm not going into details on what I did, I'd just like to request the Stock ROM that came with it so I could restore my phone. It has android 4.1.2 and I just want to install it using the "Apply Update From sdcard." And if you must know, I edited the Build.prop file (The internet told me to.) And it messed up and wouldn't start up and got stuck in "Bootloop" so I tried factory reset and it didn't and I really need my phone because if I don't fix it I'll have to try to send it in to Huawei or T-Mobile or who ever. Plllllllz help.
Click to expand...
Click to collapse
You don't want to go into details but you still want someone to help you? Hahahahaha!!!
Good luck with that plan!
CtrlAltDelIrl said:
You don't want to go into details but you still want someone to help you? Hahahahaha!!!!
Click to expand...
Click to collapse
Show some compassion - I'm sure most of the people here have messed up, and hit their heads against the wall for it.
Deeeno said:
Show some compassion - I'm sure most of the people here have messed up, and hit their heads against the wall for it.
Click to expand...
Click to collapse
Yes and in those cases they're usually eager to share all the details required, unlike the OP.
When the proper details are supplied it's easy to help, nobody likes to mindread here.
CtrlAltDelIrl said:
When the proper details are supplied it's easy to help, nobody likes to mindread here.
Click to expand...
Click to collapse
Probably doesn't know exactly what they did to mess up.. so doesn't know how to explain it.
Merely asked for the stock application to try and fix it themselves is what I gathered.
But Whatever
Explanation.
Was using Android tweaker 2 and accidentally hit the "On Screen Navigation Keys" and then when I went to turn it off it wouldn't switch. It stayed on. Updated the T weaker app, hoping for a fix but the option disappeared and I was stuck with them. Searching the internet I found a option that allowed to disable the soft keys in the Build.prop. But when I save it and restarted the phone was stuck at the T-Mobile screen.
Also I never figured out how to do ABD it tried for a long time but it didn't work. Since I got it in October, I need to know who to send it to be repaired, since I have a warranty (But I don't really want to send it away so that's why I asked.) So, there's and explanation. I'd tell you what I edited if I could find the website.
ADB
Okay, I got ADB working. But if I unlock Bootloader, does that that void my warranty?
And basically I need a default Build.Prop. Thats the only file I edited.
Return the phone since you are under warranty, you won't be without a phone
If you are under warranty with tmobile, you should be able to get a replacement if you are on their JUMP insurance, even if it was accidental.
I would recommend first going to your tmobile store and asking them to send you a replacement(and to waive the restock fee). They will send you one by mail in a few days, then all you have to do is send the old phone back to them in the prepaid shipping package(instructions are included).
I would recommend doing this instead of unlocking your bootloader and waiting for a recovery and custom rom to come out. My belief is that unlocking your bootloader does NOT directly void your warranty, unless the company can prove that the unlocking directly bricked your phone(which it doesn't). A thread with the legality of unlocking your bootloader is found here: http://forum.xda-developers.com/showthread.php?t=2250113
Again, I recommend just bringing in your phone and saying your phone just refuses to boot anymore since an update or something of that like. You won't have to wait long. Also, the phone is $63 on ebay, if you are uneasy about going to tmobile to return it.
build.prop for Android 4.1.1
default Prism 2 build.prop file for Android 4.1.1 attached below. Don't know if this will work with 4.1.2, so make a backup of your build.prop before replacing it!
Prism 2 said:
default Prism 2 build.prop file for Android 4.1.1 attached below. Don't know if this will work with 4.1.2, so make a backup of your build.prop before replacing it!
Click to expand...
Click to collapse
Dont do this, you will brake it even more, every version has specific build prop.
Okay, but no.
Not on insurance....
They didn't offer it at Walmart, that I know of. The real reason I got it was that I was sick of my unlocked Pantech Link (An AT&T on T-Mobile...)
And plus, I'm just broke right now -_-
Are you sure you have Android 4.1.2? I have the latest stock T-mobile rom (just tried updating today) and I'm "up to date" with 4.1.1
How do you have 4.1.2?
That's strange. Can any other users confirm that their Prism Ii has 4.1.2?
Well...
Well.. I may be mistaken. But I can't check =/
Almost certain you have 4.1.1
Doubt they would push an OTA just to upgrade from 4.1.1 to 4.1.2, but if someone can verify they have 4.1.2 i am open for correction.
I think pushing the new build.prop to your phone is worth the shot, and it would not effect your bootloader since it is locked, and you are already softbricked.
To push the build.prop to your phone, you have to rename the old one in adb, and then use the adb push command to push the file into the appropriate folder ( /system )in this case.
If you need help organizing the files or using the actual commands, let me know. Also, you want to place the build.prop file in the same folder you installed adb.
Also, to run adb, you have to open cmd and change your directory(the command is cd) to the folder you installed adb to, in order to use the adb command.
The adb command only runs when you are in that folder in the command prompt, because adb is not a systemwide command
streetdev22 said:
Doubt they would push an OTA just to upgrade from 4.1.1 to 4.1.2, but if someone can verify they have 4.1.2 i am open for correction.
I think pushing the new build.prop to your phone is worth the shot, and it would not effect your bootloader since it is locked, and you are already softbricked.
To push the build.prop to your phone, you have to rename the old one in adb, and then use the adb push command to push the file into the appropriate folder ( /system )in this case.
If you need help organizing the files or using the actual commands, let me know. Also, you want to place the build.prop file in the same folder you installed adb.
Also, to run adb, you have to open cmd and change your directory(the command is cd) to the folder you installed asb to, in order to use the adb command.
The adb command only runs when you are in that folder in the command prompt, because adb is not a systemwide command
Click to expand...
Click to collapse
Pushed the Build.Prop, but still does the same thing. Lost the old one though, because I forgot to rename it.
Try Factory Reset once more
You are stuck in a bootloop? Try factory resetting once more.
If that does not work, you may be our first live install recovery image tester, and you'd just have to wait until a custom ROM was released.
Reseted... Still stuck.
Omg. They must make these phones just to make us upset when they break.
Wait until I get the unlock code from Huawei, also some other things to try
It should be any minute now, and I will see if there are other fixes. For now, unlock your bootloader according to the guide.
We will need access to recovery anyway, through recovery, we will try wiping cache/dalvik cache if available, and that may be the fix you need.
Also: I think you may need to change the permissions on the build.prop you pushed!
You would have to change the permissions to 644 according to this thread: http://forum.xda-developers.com/showthread.php?t=2152850&page=2
To do this, we would still need to use adb.
Commands in adb:
adb shell
remount rw
chmod 644 /system/build.prop
Also, are you sure that the file actually pushed successfully?
This tablet is a 7 inch tablet made by rockchip , is dual core, and runs android 4.4.2 kitkat. Since I bought it I wanted to find a way to root this tablet so that I could make it faster and so that I could change a few aspects from it. I could not find a way to root it AT ALL since I bought it. Last week, I found out that KINGO ROOT will effectively root this tablet. However, I do not have a backup of the device and got stuck in a boot loop.
The problem is that I changed the Bootanimation.zip in /system/media and apparently the permissions were wrong when I put it. I rebooted and it got stuck in a bootloop, later going straight into recovery mode.
So I have a question. Can anyone make a custom rom for it or a backup of the stock Rom? That or show me how to use ADB to fix this since I know what caused the problem but I am running the stock rom and not a custom one and there is NO CWM or TWRP installed.
All I need is a way to delete or edit the permissions from the bootanimation.zip from ADB or another way to fix this since that is the only problem.
Thanks
Did you get this fixed?? If you can tell me how you rooted the device ..I will get you a back up of the rom
Well I did fix it. I have no idea how . haha. I guess I just tried re rooting it. It updated then script, and then I got root. So I basically pushed the original boot logo and then deleted the other one with a mix of adb and file browser. It rebooted and then it was good. I would love for there to be a back up or custom rom (like cyanogenmod) of this device but I have not found any for it. Maybe cwm?
Well thanks for answering anyways. I can only hope for something like that since I have no idea how to create a custom recovery.
And i used kingo root for it
Hi all,
I have been through douzens of threads and forums looking for a solution to this.
I followed some instructions to modify the build.prop file on my Huawei G535-L11 to disable Huawei theme manager in order to get Xsposed working fully (changed ro.config.hwtheme: 0). I did a backup of my original build.prop before hand, and my phone was rooted and unlocked but running the stock rom.
Unfortunately, it rebooted but won't go past the first 'EE' splash screen (just turns off again).
I can inconsistently get in to both fastboot and Android recovery, so I have been trying to use adb to push the original build.prop to /system/ on the phone.
However, this fails as /system/ is apparently RO. I have now discovered that I can't get SU permissions despite my phone being rooted.
If I try:
adb shell
$ su
nothing happens and it goes back to a $ prompt.
If I try:
adb root
I get the message (paraphrased):
adb cannot run as root in production builds.
So I can't push or do any adb method of restoring the build.prop file?! I don't understand why it is acting as if it is not rooted. I had Link2sd, Gravity Box, No Frills Cpu Controller all set up and working before, so I'm fairly sure I did truly have root.
I have also tried flashing a TWRP recovery, which apparently is successful, but when I go in to recovery it is still the Android Recovery.
Does anyone have any ideas what I could do to get my phone working again please?! This is my last gasp before the phone gets filed under 'B' in the cylindrical cabinet in the corner of the room!
Any assistance greatly appreciated!
Some systems are very finicky with modded build.props, or you didn't set the file's permissions correctly. I'm afraid without being able to boot or a working custom recovery, then adb won't work, much less root enabled adb functions. adb works in some stock recoveries, but only for sideloading files directly signed by the manufacturer. In regards to TWRP, is the bootloader unlocked? If not, that would explain why it didn't work. Other than that, I don't believe you'll have any other options besides reloading the stock firmware.
Hi,
Thanks for the reply. Yes, the bootloader was / is unlocked.
Unfortunately, there isn't any stock firmware available anywhere. Unless someone out there has a backed up rom image from the EE Kestrel?
This is supposed to be a working TWRP for your device http://forum.xda-developers.com/showpost.php?p=58522448&postcount=117 - if you get it loaded, there might be a chance to push the working build.prop back to the phone. I would read that thread too and see if there isn't more useful info there or another member with your phone that could make a backup for you. Good luck.
Thanks.
Unfortunately, I'm pretty sure that is the TWRP I've tried. I'll double check when I'm on my PC.
I might try requesting a rom image on that thread, but the community for this phone seems to be pretty dead :/
I've just gone and ordered a new phone anyway, but it seems like a waste of a good phone just for the sake of one line of bad code!
Thanks for your help. I'll post again if I have any success.