I have solved this problem I think last night by updating to XXEMB1 on Kies last night - I have of course lost root for the moment but will get back to that later when I have more time
I have an international galaxy gt19300
It had begun to restart itself a few times a day and then would run for days with no issues
I eventually decided to root it when I found the new toolkit on here which seemed to work a treat
I now had superuser installaed titanium back up and ROM Toolboxand paid for pro versions of this and toolkit
to be honest apart from doing one back up using the toolkit the only other thing I did was to disable the auto scanning on start up to speed up booting the phone. A day or two after this the problems started again but this time with it no rebooting but just freezing. Eventually I took out the sd card as I remembered I had an sd card problem with my old S2 - though this is a new samsung sd card. At first I thought that was it but then a bit later it froze while i was browsing the app store and has done so periodically, though today it ran all day without freezing onvce. Then suddenly it froze again for no reason - I was just swithcing screens and it froze part way through the process
As far as I can see I have three options
1) Flash a new ROM (for the moment I am still using the stock rom having only just rooted it using Toolkit.exe from here) but not sure which one I should use so need reccommendations
2) Use the toolkit to download a stock odin flashable rom (but dont I have this already?) and then 3 reset the flash counter using triangle away (seems risky to me) install the stock rom , undo root (if necessary) and then return the phone to Samsung
3) go to Kies and install the latest update in the hope that the problem will go away - though if S User pro doesnt manage to keep root I wiill presumably have to re-root all over again.
What attracted me to S3 Toolkit was that it packaged up all sorts of options into one easy package - on the other hand this may have made me a little over confident with rooting. If I hadnt rooted it the earlier problem, though not as bad, would still have been there but I could easily have sent it back to Amazon UK or Samsung UK for repair and replacement.
My biggest worry at the moment is that whichever process I go for - or even a third option suggested here - there must be a risk that the phone might lock up during flashing or upgrade - probably not likely as it didnt when I restored the back up I had done (didnt help either) and the touch wiz ui wont be running
Anyway would really appreciate some help guys - even if it is only what you would do in the same circumstances. I guess I should have tried to have the problem fixed but earlier I put that down to maybe having too many apps and crapware and thougth rooting would help me solve it. I have unintstalled every app that I dont regularly use but it is still happening
gbswales said:
...
Click to expand...
Click to collapse
First of all you have to be aware of the fact that rooting & flashing ROMs is always a risk, toolkit or not.
The safest way is to stay un-rooted stock if you do not know why you need root in the first place. If you know you need root, and actually also before, read the guides & information in the stickies under the General section as they explain you in detail how to root, un-root, use triangle away etc.
As for your situation, I would try to 1) flash another kernel than the stock one, if this does not work, 2) flash the most up-to-date stock ROM (you can get it here on XDA or sammobile.com) via Odin or Mobile Odin, not the toolkit (Odin is as simple as the toolkit if you follow the how-to), if this also does not work 3) try a custom rom, and if it also does not work 4) return back to stock and give it to Samsung service centre.
I wish you good luck!
Thanks for your advice
chrismast said:
First of all you have to be aware of the fact that rooting & flashing ROMs is always a risk, toolkit or not.
The safest way is to stay un-rooted stock if you do not know why you need root in the first place. If you know you need root, and actually also before, read the guides & information in the stickies under the General section as they explain you in detail how to root, un-root, use triangle away etc.
As for your situation, I would try to 1) flash another kernel than the stock one, if this does not work, 2) flash the most up-to-date stock ROM (you can get it here on XDA or sammobile.com) via Odin or Mobile Odin, not the toolkit (Odin is as simple as the toolkit if you follow the how-to), if this also does not work 3) try a custom rom, and if it also does not work 4) return back to stock and give it to Samsung service centre.
I wish you good luck!
Click to expand...
Click to collapse
Firstly the good news is that it turned out to be a problem with the last XXELLA upgrade - I found a new one on KIES ran the update and it is fine
Of course I lost root access but expected that anyway.
I do enjoy tinkering with Systems and although I know my way around Windows I have not tried with Android until now - this is my second Galaxy so was naturally wary of bricking it if I rooted. Christmas time I bought myself a galaxy tab 2 10.1 with the express aim of rooting it and was prepared to take the risk - after a few false starts I got it rooted fine - was still wary of the phone but once the kit came out the benefit that has for me is the way you have to check things step by step systematically as you do things - my problem with doing stuff from instructions on line is that I find it is all to easy to skip a step (which I did with the tab first time around) Also with it being a system I haven't explored before I like having a step by step approach which is the same way that I learned DOS way back in time.
I do want to try some different ROMs on it to see what they offer and I would really have liked to have got some apps running from my external SD card and I also like having a complete image back up (as I have for Windows 8) so that in the event of a serious issue it is easy to wipe all and restore from new (I keep several images which I make on a weekly basis so that I don't have to re-install everything.
I confess to playing with computers and devices as a hobby - evidence of this was the 350 apps I had installed before I started purging them in case that was the cause of the problem. I pretty nearly try every new app I find just to see what it does and so there being a whole range of apps that I couldn't install without root access upset me. I am not going to rush to root again and will at least wait until the current version has been on the phone a while - just to make sure the XXEMB1 version is stable now - it has a lot of new admin features to keep me amused for a while!
Two things that disappointed me about root were that it looked as if I couldn't overclock the device to improve speed - the main CPU bar was already on max (though I didn't have time to explore more than that) and that it still seemed pretty hard , if possible at all on the hardware, to run apps from the external SD card -- as I do now with windows (using a smaller SSD ) I will have to be a bit more prudent about uninstalling the apps I find I don't really use.
I guess deep down the main reason why I want root is I don't like any manufacturer telling me what I can and cannot do with the device I paid for - one thing I did try was installing Linux but that didn't quite get finished before I lost root access.
Your advice however is very sound for people who don't like or enjoy tinkering or taking risks and I don't think I would recommend any normal phone user to root their device.
Thanks again
Just to add quickly....to overclock you need to flash a kernel that supports it.....And know what you are doing before doing it
I have a ZTE Avail 2 which I recently managed to root with Cydia Impactor. Afterwards I managed to screw it up by removing too many stock apps with Titanium. I did it carefully, one by one, and for a few days everything seemed to work fine. But then apps started force-closing, '<name of app here> has stopped working', etc. Factory reset doesnt help, it just restores me to the same screwed up state I'm in now. I already know why, it's because I removed some of the stock apps, which I now realize it needs. I'm currently stuck on the AT&T logo when powering on, it never gets any further. But even while it was messed up it was still halfway-operable, and now this. This device's subforum on Android Forums is all but non-existent, and XDA doesnt seem to have anything for it.
What I need is a 100% stock ROM (pre-rooted if possible) that I can flash, along with instructions on how to flash it. I have some experience flashing ASUS devices and Samsung devices, mainly the Transformer pad, and the Note 2, but have also rooted miscellaneous other devices in the past without alot of issues. But I have no experience with ZTE. I've already checked the manaufacturer's website for some kind of recovery software I can use to restore it, there doesnt seem to be anything.
Thanks for any help!
Stephen Wayne Hamilton said:
I have a ZTE Avail 2 which I recently managed to root with Cydia Impactor. Afterwards I managed to screw it up by removing too many stock apps with Titanium. I did it carefully, one by one, and for a few days everything seemed to work fine. But then apps started force-closing, '<name of app here> has stopped working', etc. Factory reset doesnt help, it just restores me to the same screwed up state I'm in now. I already know why, it's because I removed some of the stock apps, which I now realize it needs. I'm currently stuck on the AT&T logo when powering on, it never gets any further. But even while it was messed up it was still halfway-operable, and now this. This device's subforum on Android Forums is all but non-existent, and XDA doesnt seem to have anything for it.
What I need is a 100% stock ROM (pre-rooted if possible) that I can flash, along with instructions on how to flash it. I have some experience flashing ASUS devices and Samsung devices, mainly the Transformer pad, and the Note 2, but have also rooted miscellaneous other devices in the past without alot of issues. But I have no experience with ZTE. I've already checked the manaufacturer's website for some kind of recovery software I can use to restore it, there doesnt seem to be anything.
Thanks for any help!
Click to expand...
Click to collapse
Just out of curiosity you ever figure out a solution? I have the AIO branded version of it.
drago10029 said:
Just out of curiosity you ever figure out a solution? I have the AIO branded version of it.
Click to expand...
Click to collapse
If needed, I could back up my /system folder and send it to you.
Simba.7 said:
If needed, I could back up my /system folder and send it to you.
Click to expand...
Click to collapse
it's alright man. someone on android forums has already made a custom ROM. so the ball is rolling on out weak old device :laugh:
build.prop?
Simba.7 said:
If needed, I could back up my /system folder and send it to you.
Click to expand...
Click to collapse
did you ever get around to doing this? there is supposedly a stock image on androidforums but when I opened the Zip, all it had was the stock apps, no build.prop, which I think I blew away with xblast (xposed plugin). now I hang on the boot screen image. there is a stock Rom for the z993 our there, which I suppose I could use, because they are supposed to be the same phone, just different carriers... but then I need to get the at&t apn's and it is just a PITA. so if you could post /system backup or just a stock build.prop, that would be great!
(I'd post links to these rooms but I guess I'm too new of a member... I can provide them if needed.)
I'm way late on this, but just thought I'd post to say that I no longer have the device, and I was never able to fix it.In any case, I hope the rest of you guys get it fixed. It seemed to be a halfway decent phone, although a bit sluggish at times. But beyond that, with all the bloat removed, I'd say it ran pretty well for the duration of time that I had it (less than a month). I currently have a GNote 3 (T-Mobile) and a GNote Pro 12.2" now and it's just awesome, I'm really loving them.
Sorry, accidental double-post (can't figure out how to delete this post, the "Edit/Delete" button doesnt appear to have any option to entirely delete a post).
Just like "AnonVendetta83" messed up using Titanium.
Now desperately looking for Stock ROM or any working custom ROM to bring phone back to life.:crying:
alirezayami said:
Just like "AnonVendetta83" messed up using Titanium.
Now desperately looking for Stock ROM or any working custom ROM to bring phone back to life.:crying:
Click to expand...
Click to collapse
There is a working custom Rom for the z993 (identical hardware, different customized software for AIO, another cell provider). All you will need to do is change/update the data provider stuff so you can still use 3g and mms's. Plenty of info on this online on what needs to be changed.
You can get this Rom over at androidforums.com
http://androidforums.com/prelude-all-things-root/792279-zte-prelude-z993-stock-unrooted-rom-aio.html
There is also a cwm recovery there that works on this phone, and a partial /system backup by someone else for the z992... it is just apps and what not.
If they aren't available anymore, let me know and ill see if I still have them saved somewhere for you.
Sent from my KFTHWI using Tapatalk
AlexZap said:
There is a working custom Rom for the z993 (identical hardware, different customized software for AIO, another cell provider). All you will need to do is change/update the data provider stuff so you can still use 3g and mms's. Plenty of info on this online on what needs to be changed.
You can get this Rom over at androidforums.com
http://androidforums.com/prelude-all-things-root/792279-zte-prelude-z993-stock-unrooted-rom-aio.html
There is also a cwm recovery there that works on this phone, and a partial /system backup by someone else for the z992... it is just apps and what not.
If they aren't available anymore, let me know and ill see if I still have them saved somewhere for you.
Sent from my KFTHWI using Tapatalk
Click to expand...
Click to collapse
Thank you so very much Alex
I was wondering if I can just simply place the rom zip on the root of your sdcard and continue without doing "Install CWM - ZTE Prelude (Z993) Root&Recovery" step???
Honestly I have absolutely no idea how to do CWM steps as they come so complicated to me.
alirezayami said:
Thank you so very much Alex
I was wondering if I can just simply place the rom zip on the root of your sdcard and continue without doing "Install CWM - ZTE Prelude (Z993) Root&Recovery" step???
Honestly I have absolutely no idea how to do CWM steps as they come so complicated to me.
Click to expand...
Click to collapse
You need to install the custom recovery... It is the only way to install the zip file. If you just have the zip and go into the stock recovery I don't think you can select which zip to install
Sent from my N9002 using XDA Premium 4 mobile app
AlexZap said:
There is a working custom Rom for the z993 (identical hardware, different customized software for AIO, another cell provider). All you will need to do is change/update the data provider stuff so you can still use 3g and mms's. Plenty of info on this online on what needs to be changed.
You can get this Rom over at androidforums.com
http://androidforums.com/prelude-all-things-root/792279-zte-prelude-z993-stock-unrooted-rom-aio.html
There is also a cwm recovery there that works on this phone, and a partial /system backup by someone else for the z992... it is just apps and what not.
If they aren't available anymore, let me know and ill see if I still have them saved somewhere for you.
Sent from my KFTHWI using Tapatalk
Click to expand...
Click to collapse
AlexZap said:
You need to install the custom recovery... It is the only way to install the zip file. If you just have the zip and go into the stock recovery I don't think you can select which zip to install
Sent from my N9002 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thnx Alex
I would highly appreciate if anyone tell me what ADB Driver I should use for ZTE Z992. I almost understood all the procedure in the links but now the problem is despite I tried different ADB Drivers, but still ADB reboot-bootloader boots phone again in Normal bootloader.
Also Fastboot devices command does not see the phone, while ADB Devices command see it.
Seems bootloader is locked. Right? What should I do?
This is the method I used when I rooted my avail2 :
http://androidforums.com/zte-avail-2-zte-prelude/821217-how-root-zte-avail-2-z992-guide.html
The author (and I) just used the included drivers from zte that come with the phone. From what I remember, fastboot worked fine. Just hold the volume down button then turn the phone on. It will seem to lock on the start screen, but this is the bootloader. Then connect your cable and try your fastboot commands.
If you are already rooted, you can just download the package here
http://androidforums.com/prelude-all-things-root/797487-cwm-recovery-installer-zte-prelude.html
And skip the middle section, using the impactor to root (13 and 14).
Depending on what's wrong with your phone, you could also try just using the stock recovery and doing a system reset there. It will wipe any bad custom settings, but if the rom is still viable it might get you up and running again. It got me out of a bootloop without re-romming the whole thing. And with titanium backup or system app mover you can reinstall anything you need in the system partition.
*edit - Damn kindle auto correct
Sent from my KFTHWI using Tapatalk
A bit to much fiddling resulted in disaster
Hello XDA forum users,
I'm about ready to toss this phone in the trash. I have an AT&T Avail 2 with model number z992, which is apparently manufactured by a company called ZTE. First I think it would be helpful to explain what I've done to the phone and perhaps others out there can tell me if I've destroyed the phone or if it can be fixed.
A friend of mine sold me the phone for 10 bucks, its in great condition which is why its such a shame that it seems perma-bricked. I have no need for the phone aspect of the device, I simply wanted to "convert" it to a handheld media/application player, like an ipod or tablet for example. The phone comes with several bundled software applications that I find completely useless and wanted them removed, EX. AT&T Navigator and other AT&T software, plus a bunch of google applications.
The first thing I did when I decided to try and customize it was to use Kango's root tool which worked and rooted the phone. I was all excited that it worked and continued by installing the Super User application which allowed me to gain full control over the device. (I should have stopped there.) After the successful phone root I then installed a 3rd party app called NoBloat and used its uninstall options to remove a lot of stuff. I couldn't tell you exactly what all was removed but looking back, it must have been more important than I realized at the time. I know I took out all the AT&T software, then all the Google stuff to, which destroyed the play store. I didn't take out anything that seemed like a system file but apparently the Google stuff is the system files. The phone still worked in this state but it was erratic and things like Contacts would crash even if it was not running. So I considered that a failed attempt and commenced to do a factory reset using the recovery menu (Vol Up + Menu Key + Power button) but the factory reset didn't work, well not like it was supposed to. I had used the restore option before and it made the phone work like it was brand new. Now when the phone is powered on it will boot to the initial setup and ask me to choose a language, then it will get as far as the wireless connection screen (sometime not even that far) and the phone reports that "Unfortunately, Setup Wizard has stopped." and then I tap OK and the setup wizard restarts at the language screen. This is the state it is in now and I do not know how to fix it, I'm beginning to think there currently is no method to fix this.
Things I've tried so far include installing minimal ADB-Fastboot to try and sideload various ROM images, the ones I found here and other places. The phone is not recognized by Windows 7 though and the ADB does not work like it did on a motorola phone I did this to before. I've also purchased an inexpensive 8GB microSD chip with an adapter so I could put the ROM info on that and tried the "Update from external storage option" and that seems like it would work but none of the ROM's I've used will install. I guess because there is some kind of security feature built into the phones hardware which checks the data files for specific tags/sizes and therefore won't accept any of the ROMS I've tried.
There is no means to access the old file system anymore like most guides show, I do not have any CWM's installed nor any backup data whatsoever. It's been reset and now it seems the data it used to restore itself is, while not completely missing, damaged and will not reload anymore. All the guides I've read or watched usually show the user in the operating system or using software on a PC to type out commands. None of that works on this phone though, the phone as I just described it is basically bricked. Is there anything that can fix this, or is the phone a paper weight now? A functional ROM image from AT&T seems unlikely as they have absolutely no relevant information about this on the commercial website and the help and support seems like it's setup for old people who don't understand technology at all. If anyone out there has experience with issues like this then by all means let me know. If more information is necessary then I will be glad to provide it if available.
Alright I did manage to figure out how to make the computer see the phone as an ADB device and the minimal ADB interface shows the device now when I type ADB devices at the command prompt. Though this ADB thing seems irrelevant considering I can do the same thing by using the SD card adapter. So I don't know if this was useful or not. The ADB prompt shows a device number of P752A15.
Before I was unable to make the device show up at all in the ADB list. The problem now is how to make the phone accept a ROM, at this point I don't even care if the ROM is the default factory ROM or some random ROM made by a devoted user. The issue I encounter each time is that the built in recovery option to restore from an SD card will not accept the ROM's I've tried so far, and my research on this seems to indicate that I need a custom recovery option. This is apparently called the ClockWorkMod but as to how I install that without a functional operating system on the device is a mystery still. I've tried using a file called recovery.zip and but it does not show up when I view the contents of the SD card when the card is in the phone.
I feel like an idiot because I've done this to other phones for my family and friends, you know jailbreaking an iPhone, and rooted a Galaxy S3 once but this phone seems like its not going to be as easy as those others. I guess AT&T made sure that if you alter it, it breaks the phone. I'll check back later and see if anyone has dropped a line or two here in response to my inquiry.
Thank you and have good day.
Britton Burton said:
Alright I did manage to figure out how to make the computer see the phone as an ADB device and the minimal ADB interface shows the device now when I type ADB devices at the command prompt. Though this ADB thing seems irrelevant considering I can do the same thing by using the SD card adapter. So I don't know if this was useful or not. The ADB prompt shows a device number of P752A15.
Before I was unable to make the device show up at all in the ADB list. The problem now is how to make the phone accept a ROM, at this point I don't even care if the ROM is the default factory ROM or some random ROM made by a devoted user. The issue I encounter each time is that the built in recovery option to restore from an SD card will not accept the ROM's I've tried so far, and my research on this seems to indicate that I need a custom recovery option. This is apparently called the ClockWorkMod but as to how I install that without a functional operating system on the device is a mystery still. I've tried using a file called recovery.zip and but it does not show up when I view the contents of the SD card when the card is in the phone.
I feel like an idiot because I've done this to other phones for my family and friends, you know jailbreaking an iPhone, and rooted a Galaxy S3 once but this phone seems like its not going to be as easy as those others. I guess AT&T made sure that if you alter it, it breaks the phone. I'll check back later and see if anyone has dropped a line or two here in response to my inquiry.
Thank you and have good day.
Click to expand...
Click to collapse
Ok, been a while since I've used this phone, but hopefully this will help. I assume you have the kaw202_recoveryflasher.zip file. Once you extract it, look for the .img file. Try running these adb commands
adb.exe push cwm-z993.img /cache
adb.exe shell "su -c 'dd if=/cache/cwm-z993.img of=/dev/block/mmcblk0p17'
This should flash cwm if your phone is rooted and adb shell is working.
Sent from my KFTHWI using XDA Premium 4 mobile app
AlexZap said:
Ok, been a while since I've used this phone, but hopefully this will help. I assume you have the kaw202_recoveryflasher.zip file. Once you extract it, look for the .img file. Try running these adb commandsp
Click to expand...
Click to collapse
I have not come across that particular file yet, I did try to google it and the only results it had were two and one of those was this post. Would you mind telling me where I might find a copy of the kaw202_recoverflasher.zip?
I managed to find the zip you were talking about and have downloaded it, for anyone else looking for it. I am unable to post links but I would have linked to the files you mentioned. For others looking for the same zip file search for "CWM Recovery Installer ZTE PRELUDE". That's the title of the thread I found the file on that Alex mentioned above. The instructions on the page don't seem like they apply to the situation I'm stuck in but I'll give it a whirl anyway and see if the files work.
If this forum is like the others I've read through so far then there is no real answer to the issue. The phone seems kind of new and not many of the power users on these forums use rinky dink phones like this one. You guys all have the 600 dollar models I guess. What bugs me about this this phone and the state I managed to put it in, is that the damn thing was programmed the first time when it was made. So it seems to me like there should be a way to reprogram the phone the same way the factory did it. Think about it, when they make the phones they don't have any information on the phone at all. It's completely empty, so there must be a way to load the software for the phone even if the phone has no data at all in the main storage. If the files in the recovery flasher.zip file work then I'll post back the results but if it's like the other files I've messed around with (which didn't do anything) then I'm throwing it in the trash can.
Anyway thanks for your response and for pointing me in a different direction Alex
---------- Post added at 09:15 PM ---------- Previous post was at 08:39 PM ----------
HELL YEAH!!! It worked thank you Alex,
I would have never figured this out without your help! The phone now has a version of CWM on it and the recovery menu is different. I just tried to install a ROM and it said successful. After the phone rebooted went back to the setup screen from ZTE but it still did the same thing. However this is progress and I should be able to "wander in the dark" and figure out a way to use the CWM to install a completely new rom. Any recommendations on a ROM to use for the z992?
Good news, I was able to fix it using the information Alex guided me to find. Since there doesn't appear to be a stock AT&T version of the ROM I ended up using the Azazel ROM. Which at first failed even though it was installed, this I determined was due to the old ROM image still being partially active on the system partition. So I formatted the system partition to and tried again. This time it worked and the phone seems fully functional again, and best of all the annoying bloatware is not present and the apps are not crashing. I consider this issue resolved. Thank you again Alex I will be sure to leave a thanks on your post.
Britton Burton said:
Good news, I was able to fix it using the information Alex guided me to find. Since there doesn't appear to be a stock AT&T version of the ROM I ended up using the Azazel ROM. Which at first failed even though it was installed, this I determined was due to the old ROM image still being partially active on the system partition. So I formatted the system partition to and tried again. This time it worked and the phone seems fully functional again, and best of all the annoying bloatware is not present and the apps are not crashing. I consider this issue resolved. Thank you again Alex I will be sure to leave a thanks on your post.
Click to expand...
Click to collapse
ze
Glad I could help, but none of the work was done by me, the guys over at android central did all the heavy lifting, I just pointed you in the right direction. I have a stock system e m image around here somewhere if you need it, tho installation will be a bit more complicated. If azazels rom ever gives you issues, ill dig it up and try and help you install it.
Sent from my KFTHWI using XDA Premium 4 mobile app
Hi!
This is my first time ever posting here and although I've found some topics relating to my issue, none have helped me out.
My problem:
I downloaded an app called Flashify.
From the app, I downloaded android 4.4 KitKat because I wanted to update my ROM.
When I booted my phone into recovery (stock <3e>), I clicked on install from SD card, installed the .zip file but I got an error...
It read:
"E:failed to verify whole-signature"
"E:signature verification failed"
"E:update fail and delete temp files"
"formatting /cache..."
Instalation aborted.
Now, if I try to set up my phone again, I'll get as far as the welcome screen and it will always say:
"Unfortunately, Setup Wizard has stopped."
Please help.
I've tryed everything and I can't get rid of that error!
Thank you
Oh by the way, I forgot to give some details
The phone is a Huawei Ascend g330 U8825-1
Android 4.0.4 ICS
Rooted
Running stock everything (or at least it was...)
The file I tryed to install is called: "gapps-kk-20140105-signed-4.4.zip"
Did you even look at a guide on how to update your phone? Actually, I am quite sure you didn't or else you completely misunderstood everything you read. Neither is a good thing when trying to do something complicated like updating your phone unofficially.
1) You can't install a custom rom with stock recovery.
2) You didn't even download a rom - those are the Google Apps that are to be installed along with a custom rom like CyanogenMod.
3) You have to unlock the bootloader to install the custom recovery that will allow you to install updates not signed directly by Huawei.
I suggest you read through this thread:
http://forum.xda-developers.com/showthread.php?t=2198908
There are links in the later pages to a version of 4.4.2 from the Modaco forums, as well as links to the original firmware, which you will probably need to re-install if a factory reset doesn't help.
es0tericcha0s said:
Did you even look at a guide on how to update your phone? Actually, I am quite sure you didn't or else you completely misunderstood everything you read. Neither is a good thing when trying to do something complicated like updating your phone unofficially.
1) You can't install a custom rom with stock recovery.
2) You didn't even download a rom - those are the Google Apps that are to be installed along with a custom rom like CyanogenMod.
3) You have to unlock the bootloader to install the custom recovery that will allow you to install updates not signed directly by Huawei.
I suggest you read through this thread:
http://forum.xda-developers.com/showthread.php?t=2198908
There are links in the later pages to a version of 4.4.2 from the Modaco forums, as well as links to the original firmware, which you will probably need to re-install if a factory reset doesn't help.
Click to expand...
Click to collapse
I'm new to all of this and I thought that the app that I downloaded could do it all in one operation.
I wanted to take a chance and see would happen, thinking that any consequences that may occur, could be fixed with a factory reset.
Thanks for the link and the advice.
I'll have a read, now
Is it a serious problem or is there any way to fix it?
I tryed unlocking the Bootloader in DC-Unlocker but to no avail.
Well, I guess I'm one of those now. I installed SU, SafeStrap and had root working. Except for a few minor glitches here and there, the HDX was working great. I wasn't happy with the glitches, so I thought I could revert to stock. Tried OTA, but it wouldn't completely download, so I thought I could grab the bin off Amazon or the forums. Tried that and now I've got the Black Screen of Death. BTW, I don't' have a backup slot anymore and it seems recovery has become unstable (can't create new ROM slots).
After fully powering on, the power button makes the correct sound when you try to turn it off. The volume buttons also make their indicator sounds when you hit the top and turn down/up. I still can get into Recovery and have ADB in both Recovery and when on the BSoD. What I haven't been able to do is get root back so I can do the ADB push to restore anything to working. Here's what I've tried:
initially, tried restoring to stock Amazon through recovery... this is what started my mess
got the Amazon 'device can't start' so I wiped to factory... that didn't work
tried reinstalling apollo_g_apps_ROM... that didn't work
Then i tried http://forum.xda-developers.com/showthread.php?t=2792225 - no root, so I can't do it
and http://forum.xda-developers.com/showthread.php?t=2588608 - get stopped with jcase steps
and (jcase) http://forum.xda-developers.com/showthread.php?t=2542456 - get an error that my device isn't supported
I'd like to learn how to fix this rather than just call Amazon. Been rooting/ROMing my phones for a few years (Hero was the first one) and I've had good success. (I know HDX is different... I did read the warnings, I just made a mistake and now I want to learn how to fix it.) A little explanation of what I need to do would be appreciated though.
ok
enjid said:
Well, I guess I'm one of those now. I installed SU, SafeStrap and had root working. Except for a few minor glitches here and there, the HDX was working great. I wasn't happy with the glitches, so I thought I could revert to stock. Tried OTA, but it wouldn't completely download, so I thought I could grab the bin off Amazon or the forums. Tried that and now I've got the Black Screen of Death. BTW, I don't' have a backup slot anymore and it seems recovery has become unstable (can't create new ROM slots).
After fully powering on, the power button makes the correct sound when you try to turn it off. The volume buttons also make their indicator sounds when you hit the top and turn down/up. I still can get into Recovery and have ADB in both Recovery and when on the BSoD. What I haven't been able to do is get root back so I can do the ADB push to restore anything to working. Here's what I've tried:
initially, tried restoring to stock Amazon through recovery... this is what started my mess
got the Amazon 'device can't start' so I wiped to factory... that didn't work
tried reinstalling apollo_g_apps_ROM... that didn't work
Then i tried http://forum.xda-developers.com/showthread.php?t=2792225 - no root, so I can't do it
and http://forum.xda-developers.com/showthread.php?t=2588608 - get stopped with jcase steps
and (jcase) http://forum.xda-developers.com/showthread.php?t=2542456 - get an error that my device isn't supported
I'd like to learn how to fix this rather than just call Amazon. Been rooting/ROMing my phones for a few years (Hero was the first one) and I've had good success. (I know HDX is different... I did read the warnings, I just made a mistake and now I want to learn how to fix it.) A little explanation of what I need to do would be appreciated though.
Click to expand...
Click to collapse
Okay we tried this once before with another guy that had a similar situation and it worked for him.. You need to push root via ADB even if your system is screwed. Go back to this forum http://forum.xda-developers.com/showthread.php?t=2782159 especially the first half you will find me in their posting about a Chinese root method and how to use it. It came here just before towelroot .It will push root even though your system will not boot, via ADB . Have your Wi-Fi turned off on your computer while you are using this application to do this and promptly uninstall I don't know if we ever figured out that it was well trusted but it does work. You will also find somewhere in that thread about another link to XDA that runs an application to replace the Chinese superuser with our SU... But worry about that later. btw this shouldnt have happened if you were messing with a slot and not stock slot. Just do not factory reset.
jimyv said:
Okay we tried this once before with another guy that had a similar situation and it worked for him.. You need to push root via ADB even if your system is screwed. Go back to this forum http://forum.xda-developers.com/showthread.php?t=2782159 especially the first half you will find me in their posting about a Chinese root method and how to use it. It came here just before towelroot .It will push root even though your system will not boot, via ADB . Have your Wi-Fi turned off on your computer while you are using this application to do this and promptly uninstall I don't know if we ever figured out that it was well trusted but it does work. You will also find somewhere in that thread about another link to XDA that runs an application to replace the Chinese superuser with our SU... But worry about that later. btw this shouldnt have happened if you were messing with a slot and not stock slot. Just do not factory reset.
Click to expand...
Click to collapse
Good news is, Vroot may have worked. It reported it worked, but I'm still at a black screen. I attempted the next step, which was to modify build.prop. Again, no screen, so I used ADB. I was able to pull the file to my computer and make the changes, but I can't get SU confirmed so I can put the file back.
I found this post to try as a next step, hoping I could get the screen back: http://forum.xda-developers.com/showpost.php?p=53444204&postcount=75. When I issue SU, the kindle lights up (still nothing displayed) and ADB waits. Then it times out and reports not permitted.
I guess the biggest problem right now is, I can't confirm dialog boxes b/c I can't see them on the screen. Is there a way to force SU from ADB? My thinking after that is, I could then push an Amo bin and get my screen back. Maybe that's not possible either.
?
enjid said:
Good news is, Vroot may have worked. It reported it worked, but I'm still at a black screen. I attempted the next step, which was to modify build.prop. Again, no screen, so I used ADB. I was able to pull the file to my computer and make the changes, but I can't get SU confirmed so I can put the file back.
I found this post to try as a next step, hoping I could get the screen back: http://forum.xda-developers.com/showpost.php?p=53444204&postcount=75. When I issue SU, the kindle lights up (still nothing displayed) and ADB waits. Then it times out and reports not permitted.
I guess the biggest problem right now is, I can't confirm dialog boxes b/c I can't see them on the screen. Is there a way to force SU from ADB? My thinking after that is, I could then push an Amo bin and get my screen back. Maybe that's not possible either.
Click to expand...
Click to collapse
.
Safestrap was booting?
jimyv said:
.
Safestrap was booting?
Click to expand...
Click to collapse
Yup. Still is.
?
enjid said:
Yup. Still is.
Click to expand...
Click to collapse
What was your original system version? And which safestrap version?
jimyv said:
What was your original system version? And which safestrap version?
Click to expand...
Click to collapse
OS: 14.3.2.3 (I had recently updated and I noticed another one was trying to d/l before I ran the ToolKit.)
Safestrap: Not 100% sure. I used the HDX Toolkit v0.94, so Safestrap-Apollo-3.72 at the time(?) I still have the installer and can find out exactly if need be
did
enjid said:
OS: 14.3.2.3 (I had recently updated and I noticed another one was trying to d/l before I ran the ToolKit.)
Safestrap: Not 100% sure. I used the HDX Toolkit v0.94, so Safestrap-Apollo-3.72 at the time(?) I still have the installer and can find out exactly if need be
Click to expand...
Click to collapse
Did you make a backup of stock? If you did try to restore it to stock slot. Or just grab your bin file rename to .zip ,push to sdcard along with flashable supersu . Dirty flash to stock slot.
jimyv said:
Did you make a backup of stock? If you did try to restore it to stock slot. Or just grab your bin file rename to .zip ,push to sdcard along with flashable supersu . Dirty flash to stock slot.
Click to expand...
Click to collapse
Well... thank you. I messed up my backup of stock, so I couldn't just roll back. I thought I had tried flashing a bin, but I looked again and it was something I downloaded from a forum (so either a bad d/l or bad file in general).
Anyway, I did as you suggested with a brand new Amo download and it worked. Thank you for your help and patience.
Hey guys... So I'm REALLY new at this whole rooting thing, so please forgive me if I am not aware of any terms related to rooting and such.
So basically what happened was this:
I decided to root my Galaxy S4 (sgh-i337 --- AT&T) using the towelroot method. I had to use this method because my phone is currently running Android 4.4.4 KitKat (TouchWiz) and it worked fine. SuperSU was installed, Root Checker said my phone was rooted, it was good. I tried to install CWM using Odin, and I got the "RESET" or "PASS" from Odin, which I thought that it meant that it worked. However, when I tried to go into Recovery Mode, it went into Stock Recovery Mode. I started to look at other tutorials, and I came across another one that involved flashing your phone's respective CWM .img file from your phone itself (transfer the .img to your phone's SD, and then flash it from your phone using the app, Flashify). But when I tried to go into Recovery mode to see if it worked, it gave me the yellow triangle with an error message, "System software is unauthorized by AT&T" or something like that. I tried to look at other posts, and there was a general idea that I needed to flash the stock Kernel. Now, the way I rooted the phone in the first place, I already had two different ones downloaded. One was flashed, towelroot was used, and then the second kernel (which was the one that originally on my phone before rooting) was flashed. After that, it was rooted. So me, being the complete noob I am at rooting, decided to re-flash both, in order, to see if that cleared up the error message when trying to get into Recovery Mode. This did not solve the problem either.
Again, I would like to apologize for my lack of knowledge on rooting and such, so please forgive me for my incompetence. And yes, I know that there are other threads on topics like this, but I have tried several things and it has not worked. Any help on how to fix this problem (and how to install CWM properly on my phone - since it is updated to 4.4.4 TouchWiz - or if I should use TWRP instead, because I intend on downloading the Kangapop GPE ROM(and how to install that for my specific model/software version)) is greatly appreciated, thanks!