Related
I just used ODIN to flash to stock ROM and modem in attempt to solve my problem with adding gmail account to my phone. It worked. I added my gmail account no problem and I was finally able to visit Android market. However, I have new problem now.
When I go to Market and download applications, I see bubble with "Your item will be downloaded" after I click on install button and then nothing happens. Application is not installed. No errors - nothing.
Does anyone have a solution? It would be much appreciated.
settings >> applications >> manage apps >> go to 'all' tab >> look for market >> clear data
after that re-login to market and see if that fixes it
Thank you xtone. I tried that to no avail. In addition to clearing cache on Market I also cleared it from Google Talk as I read they are somehow connected. Then I erased cache of all my apps and still it didn't get me anywhere.
Last thing I tried was to uninstall Market update. After that I have slightly different issue. Now it says 'Starting download....' and it never goes away. Also, it looks like Market re-updated itself to the new version! Is it possible?
I'm having the same exact problem. My issue started with Nero v2 and did not get fixed when I flashed Nero v3. Today, I tried PepperKake to see if that fixed the problem, but that didn't work either.
Even after a fresh install (after wiping and re-flashing, and before restoring my backups from Titanium), I try installing things from the market but nothing works.
If you look closely (at least on my phone), it will say "Downloading..." for a second or two, then FLASH "Download unsuccessful" and disappear almost instantly.
Somebody PLEASE help :'( This is very frustrating.
This happens to me on "occasion" where it says starting to download then nothing happens. The only way I get it to work, is if I cancel the current "download in progress" or whatever it says, then click "Install" once again, and then it starts immediatelly.
Also, I noticed that it was giving problems when I was using the older version of the market. Once updated it went away.
Duce HD2 said:
This happens to me on "occasion" where it says starting to download then nothing happens. The only way I get it to work, is if I cancel the current "download in progress" or whatever it says, then click "Install" once again, and then it starts immediatelly.
Click to expand...
Click to collapse
Just tried this, didn't work for me
Things that I found that could fix the problem...
Under settings>applications>manage applica.>running>clear data for "download manager", 'gmail".
Try re-formatting your SD card. Also, Unmount then Mount SD card.
Also, try using either data or WiFi and see if either works.
Do some research on this, there's alot of different threads concerning this issue, with possible solutions.
Duce HD2 said:
Under settings>applications>manage applica.>running>clear data for "download manager", 'gmail".
Click to expand...
Click to collapse
Tried, didn't work :/
Duce HD2 said:
Also, Unmount then Mount SD card.
Click to expand...
Click to collapse
Also tried, but to no avail.
Duce HD2 said:
Also, try using either data or WiFi and see if either works.
Click to expand...
Click to collapse
I've been on and off WiFi, but the problem persists.
Duce HD2 said:
Try re-formatting your SD card.
Click to expand...
Click to collapse
I don't mean to sound rude, but why would this affect anything? I feel like the problem must be with either the ROMs (JL5 ROMs maybe?) or the Market? As a test, I downloaded something through the browser with no problem. Also, is wiping much different from reformatting? What about disabling, then enabling voodoo (which I had to do in order to try out PepperKake)? I know they said "don't knock it till you've tried it," but backing up everything, reformatting, and then restoring everything seems like a tedious job and I wanna make sure I know why it's worth a try before doing it...
Also, to the OP: sorry if I'm hijacking your post. I just didn't want to start a new post and have people flame me with "THERE'S ALREADY A POST ABOUT THIS!" and whatnot.
Dude, all the stuff I brought up, I found through research in a couple minutes. Some of things I posted ended up fixing the issue for some people and some not. I do not believe the problem resides in the ROM or JL5 (which I'm running with no issue) but rather mods and what not that was installed previously...."ghost"
In the OP he states he went back to stock, so how could it be the ROM???
You don't want to be rude, nor do some research on the problem judging by your response. You want someone to give you an answer is all. Nobody has an exact answer, you just have to try different things and see what works.
"nuff said...do some research.
Duce HD2 said:
Dude, all the stuff I brought up, I found through research in a couple minutes. Some of things I posted ended up fixing the issue for some people and some not. I do not believe the problem resides in the ROM or JL5 (which I'm running with no issue) but rather mods and what not that was installed previously...."ghost"
In the OP he states he went back to stock, so how could it be the ROM???
You don't want to be rude, nor do some research on the problem judging by your response. You want someone to give you an answer is all. Nobody has an exact answer, you just have to try different things and see what works.
"nuff said...do some research.
Click to expand...
Click to collapse
No need to blow up like that...I was simply asking a question since this is the Q&A forum. I've had this problem for probably about two weeks and I have been searching through the forums, but I've never found a post where someone had the same exact problem (outside of the Nero post, but their questions went unanswered).
You bring up a good point about the OP using a stock ROM. However, I haven't installed any mods (I went straight to Nero from stock), so I'm not sure how there can be "ghosts."
Again, I'm not trying to be rude or appear lazy. There was no need for response like that. I'll take my research to solve my problem elsewhere.
I wasn't trying to be rude or anything.....but yes, there are various topics on issues with the market going from 2.2 back to 2.1 back to 2.2 and so on....hope you can find a solution to your problem, and maybe later share the outcome with us...good luck!
Found the cause but still no fix
Thanks everyone for feedback. After few hours of trying different things I found what's causing my Android market to not work.
Thus far, what I was doing when I got into trouble was:
1. ODIN to stock ROM and pda (repartition checked)
2. root using this method: http://forum.xda-developers.com/showthread.php?t=723479
3. as soon as my phone is rooted Android stops working
So I tried to install all the apps I really need first: ROM Manager and TBackup (my ultimate goal is to upgrade to nero3. Everything works great. However to use these apps I need root access.
So then I rooted again using same method as always and I get same result - malfunctioning Android Market.
When I root using above method everything works great but I see old icon of superuser application. Is there a newer update.zip to root my vibrant? Or perhaps different way to root my phone? Can I do it manually?
I have two Vibrant phones. One had no problems when I did above steps. One continues to give me grief!
Even when I odin to stock I know not all the folders get refreshed. What actually is untouched when I use ODIN method to revert my OS?
Duce HD2, what is the best way to eliminate 'ghosting' without bricking my phone? I also believe that it's caused by some mod that was done previously - I bought my phone used.
If reverting to 'stock' image is not good enough what else could I do to clean up my phone? I know for example that efs folder is unaffected by going back to 'stock' as my phone remains SIM unlocked when I do it.
Market problem
I'm having the same problem Nero v3 + voodoo. If you find a solution, please let me know,
Thanks!
ekloc said:
Thanks everyone for feedback. After few hours of trying different things I found what's causing my Android market to not work.
Thus far, what I was doing when I got into trouble was:
1. ODIN to stock ROM and pda (repartition checked)
2. root using this method: http://forum.xda-developers.com/showthread.php?t=723479
3. as soon as my phone is rooted Android stops working
So I tried to install all the apps I really need first: ROM Manager and TBackup (my ultimate goal is to upgrade to nero3. Everything works great. However to use these apps I need root access.
So then I rooted again using same method as always and I get same result - malfunctioning Android Market.
When I root using above method everything works great but I see old icon of superuser application. Is there a newer update.zip to root my vibrant? Or perhaps different way to root my phone? Can I do it manually?
I have two Vibrant phones. One had no problems when I did above steps. One continues to give me grief!
Even when I odin to stock I know not all the folders get refreshed. What actually is untouched when I use ODIN method to revert my OS?
Click to expand...
Click to collapse
I still use the Super User that you have and have no problems....
ODIN back to JFD
Root
reboot into CWM recovery
Wipe cache partition
Advanced
Wipe Davlik
go back
Factory Reset/Restore
and you should have gotten rid of everything
There is an update.zip root on the cynanogenmod ailing page for Vibrant.
http://wiki.cyanogenmod.com/index.php?title=Samsung_Vibrant:_Rooting
Don't know if its the new one.
Sent from THE Vibrant......
ekloc said:
Duce HD2, what is the best way to eliminate 'ghosting' without bricking my phone? I also believe that it's caused by some mod that was done previously - I bought my phone used.
If reverting to 'stock' image is not good enough what else could I do to clean up my phone? I know for example that efs folder is unaffected by going back to 'stock' as my phone remains SIM unlocked when I do it.
Click to expand...
Click to collapse
The best way ,"I" know, is to ODIN back to stock true (JFD), check repartition. Go through the usual process - root, rom manager, etc. Flash new custom ROM, "important" while it's still in recovery after installation is complete don't rebooot yet, this is where you'll perform these steps:
Wipe cache, wipe dalvik cache, fix permissions, perform factory reset. Then finally reboot phone.
I never ran into 1/10 of the problems that I see people having with their devices.
Also, after reboot make sure to leave your phone on idle for at least 15 minutes, so everything can properly get installed. Reboot, log in to gmail, give it 5 minutes, then reboot once again. Good to go.
Just like jmcghee1973 posted.
Give it a try and see if it works for you. Good luck.
Try using one click root as well. Never hurts to try...
Sent from my SGH-T959 using XDA App
Market working again
I followed the odin instructions, went back to stock, re-rooted, then re-installed nero3. This time I didn't restore system apps + data. My market is working. Hope this helps.
It worked for me too when I installed nero3 - market issues were gone.
I am actually not so sure any more that rooting caused the problem. What I observed was that my phone was downloading 'stuff' on its own soon after I reverted to stock image. I know that because I saw few 'download unsuccessful' messages. I also tested this theory - I reverted to stock. Immediately after I could use market but then 20-60 after my Market was not working, even when phone was un-rooted!
I don't know how these automatic downloads were triggered but my latest theory is that they have a lot to do with not working Market app.
Anyway, Nero 3 is not downloading anything automatically and I am really happy with it. Thank you guys for everything. You guys rock!!!
Greetings
As the tittle points outs, I flashed the latest Androwook Rom(2.1) and it always stucks at the Intro Crawl. I re-downloaded it, flashed it again, but had had no success.
The Prime has been unlocked since May, and it was running the Cyanogen Nightly Rom, before I tried the Wook one. I wiped Cache and Delvik, and tried an older build as well with no success. I use the latest TWRP, 2.1.3. I also tried all availlable kernels and options during the installation with no success.
Can anyone give me a hint as to what is the problem? I can always go back to CM Rom, but I would feel like I accepted defeat.
Also, why does the installation always wipe my internal sd card , when no such option is selected?
drsane1984 said:
Greetings
As the tittle points outs, I flashed the latest Androwook Rom(2.1) and it always stucks at the Intro Crawl. I re-downloaded it, flashed it again, but had had no success.
The Prime has been unlocked since May, and it was running the Cyanogen Nightly Rom, before I tried the Wook one. I wiped Cache and Delvik, and tried an older build as well with no success. I use the latest TWRP, 2.1.3. I also tried all availlable kernels and options during the installation with no success.
Can anyone give me a hint as to what is the problem? I can always go back to CM Rom, but I would feel like I accepted defeat.
Also, why does the installation always wipe my internal sd card , when no such option is selected?
Click to expand...
Click to collapse
jumping from one rom to another needs a full wipe i guess... when you said wiping your internal sd card, that's the reason why you're stuck into crawling? so i guess you use adb to push the ROM, then flash again?
in my case, when i had a bootlop, i push fullwipe.zip first, flash it, then push Androwook.zip, then flash it... it all came back alive..
First of all, thank you for your reply!
Now, to adress each step
jumping from one rom to another needs a full wipe i guess.
Click to expand...
Click to collapse
Yup, did one (factory reset+system wipe) before trying to flash AW Rom.
when you said wiping your internal sd card, that's the reason why you're stuck into crawling? so i guess you use adb to push the ROM, then flash again?
Click to expand...
Click to collapse
After the first three unsuccessfull attempt to flash the ROM did I wipe my internal SD, so it isn't the crawling looping intro's problem. And yes, I push ROMs via Adb, and trying flashing.
in my case, when i had a bootlop, i push fullwipe.zip first, flash it, then push Androwook.zip, then flash it... it all came back alive..
Click to expand...
Click to collapse
That was actually the last step I tried before asking for help. Even after I typed this post, I did it again. Flashed it, pushed AW, and flashed again. No success.
*Edit: I have forgotten a primary Troubleshooting technique. Downloading AW2.1 from a different source, will update.
sorry but im not much of a help i can see... hope somebody could. don't lose hope though...
Intentions matter
Thanks for your time anyway!
After two more failed flashes, I got it to boot!
Apparently the starting animation was causing some kind of problem, which I cannot ever imagine. After I checked the option to have the uggly original boot animation, the rom booted normally and I am now using it.
I am quite happy to get it to work, but if anyone has any solution to the boot problem, I would be really glad to hear him!
drsane1984 said:
Intentions matter
Thanks for your time anyway!
After two more failed flashes, I got it to boot!
Apparently the starting animation was causing some kind of problem, which I cannot ever imagine. After I checked the option to have the uggly original boot animation, the rom booted normally and I am now using it.
I am quite happy to get it to work, but if anyone has any solution to the boot problem, I would be really glad to hear him!
Click to expand...
Click to collapse
Hello Everybody! Guys, sorry for my english!!!!!
First of all, I have to present myself, my name is Marco, I'm italian, 25 years old and I'm in the Android world since about 12 Years.
I started whit a Galaxy S2, and after I bought an Asus Transformer Prime.
After just two week, I decided to put in a Custom ROM, on my devices, and I understood how the system work better instead of a Stock ROM!
And after, I understood, how the XDA Developers Forum is important for me, and expecially for all the people who like to learn about the Android World.
So, I just want to Thanks with all of you for the support that i receive EVERY DAY to solve my problems!
One of these was with flashing the Androwook, weeks ago I flashed the Team EOS 2.0, that was really amazing, but after a While, I found some slowdowns in some action on the system, so i decided to try a rom based on the stock rom, but with improvement and tweaks, so what's better then the Androwook?
The problem was, the same explained on this post, after all wipes, the prime was not boot, and stuck in bootanimation!
I solved, checking the box "Install custom ROM" as drsane1984 have done, and now the ROM is booted perfectly!!
Thanks another time! I'am convinced that if you are able to seach, you'll find for sure the solution to your problems! If not, just ask!
Bye!
This will help anyone who keeps having flashing issues.
More detailed instructions in my GUIDE!
http://forum.xda-developers.com/showthread.php?t=2295557
THIS IS ONE QUICK/SIMPLE ERROR FREE ROM FLASHING PROCEDURE
This should eliminate a few posts saying, stuck in download mode, stuck at logo. just vibrates and them MANY other issues that somehow, everyone seems to find.
Here is my quick rom flashing process I use ALWAYS (yes always)
THINGS YOU NEED ON extSDCARD
1. Extra kernels (2 or 3 you know works for your device)
2. Optional: 2 recoveries that can be flashed (I use CWM & TWRP)
3. Optional: apps.zip (a zip created from Titantium BU, containing Root Explorer, TU Backup, Quickpic, ES File Explorer and Terminal Emulator)
Flashing the rom: TOUCHWIZ/AOSP ROMS
1. Backup current rom (to the extsdcard)
2. Complete wipe, (I do complete, some people do not) Complete = No Issues [FACTORY RESET + CLEAR CACHE + CLEAR DALVIK CACHE + CLEAR DATA]
3. Flash the rom
4. Flash the kernel (your device kernel) (I know some roms have their own kernel) this is where your problems start.
AGAIN: FLASH YOUR KERNEL, you KNOW it works. 1 more time FLASH YOUR KERNEL. (you can experiment with other kernels after you boot)
AOSP ROMS - require you to flash gapps before you boot. [This is not required for TouchWiz roms]
5. Boot the rom.
FINISHED!!!! SUCCESS!!!
Total time to flash a rom:
7-10min
Errors - NONE
This goes for every rom in my guide.
TIPS:
This flash procedure is for Touchwiz Roms, if you are flashing AOSP roms, you must flash the gapps package associated with the rom you are flashing.
**** SGH-I337M Users: Often requires flashing a different kernel than the one included in most ATT ROMS. Any GT-i9505 kernel will work and Adam kernel and Faux kernel are both confirmed working for us Canadian users.
Note: Flash KERNEL directly after ROM then reboot device.
[Special thanks to blyndfyre for this helpful tip].
The extra recovery I flash if a rom does not like the recovery I am using.
Yes, you can flash recoveries back and forth.
Apps.zip I flash after the rom is up & running. This I use to get the rom setup (like root explorer and others needed)
I am in no way responsible for anything that may do damage to any device - Use these tips at your own risk - period!
If you found this useful in any way, please hit the THANKS button for my effort.
RESERVED
TheAxman said:
Any questions? Anyone.
Click to expand...
Click to collapse
I've been running into a lot of issues when trying to flash different ROMs. For instance, right now I'm on CleanROM 1.6 - I just tried to install PureGv2.
Steps I took:
Have Goo and ROM Manager installed after clean install of CleanROM 1.6
Flash CWM from ROM Manager
Install Recovery Script from Goo
Reboot into recover from Goo
TWRP loads
Wipe data, cache, dalvik, etc
Install PureGv2
I forget the error off the top of my head but it doesn't install
In a nutshell I'm asking what am I doing wrong? Do I need to flash another kernel?
Flash your verizon kernel. Correct. I know it is a vzn rom, but do it anyway.
TheAxman said:
Flash your verizon kernel. Correct. I know it is a vzn rom, but do it anyway.
Click to expand...
Click to collapse
Was looking through Tomsgt's Youtube channel and stumbled across a video of his that showed his "About Phone". Everything was identical to mine, so I'm still a little lost as to why I can flash certain ROMs but not others. Sac/Gru's ROM soft bricked my phone, Hyperdrive5.7 didn't install, CleanROM does. It's just funky...maybe I'll just Odin back to stock, flash the MDK and start fresh.
Could the downloads be a problem? I downloaded 2 of the ROMs from work today on a 50meg pipe and they didn't work.
Do you download the ROMs to your phone or to your computer and then move them to your SD card?
If you download to your phone, do you move them to the SD card or leave them in the download folder on the internal storage?
If you do the latter, do you use a micro SD adapter or plug the phone in and move them that way?
harrytery said:
Was looking through Tomsgt's Youtube channel and stumbled across a video of his that showed his "About Phone". Everything was identical to mine, so I'm still a little lost as to why I can flash certain ROMs but not others. Sac/Gru's ROM soft bricked my phone, Hyperdrive5.7 didn't install, CleanROM does. It's just funky...maybe I'll just Odin back to stock, flash the MDK and start fresh.
Could the downloads be a problem? I downloaded 2 of the ROMs from work today on a 50meg pipe and they didn't work.
Do you download the ROMs to your phone or to your computer and then move them to your SD card?
If you download to your phone, do you move them to the SD card or leave them in the download folder on the internal storage?
If you do the latter, do you use a micro SD adapter or plug the phone in and move them that way?
Click to expand...
Click to collapse
Download to the computer,then copy to the phones extsdcard, should be ok, make sure you do a md5 check on the files to make sure they are the correct size.
TheAxman said:
Download to the computer,then copy to the phones extsdcard, should be ok, make sure you do a md5 check on the files to make sure they are the correct size.
Click to expand...
Click to collapse
Alright sounds good. Flashing back to stock later today then re-rooting
thanks for the help
Remember always do a BACKUP before you do anything.
First off, big thanks for this thread.
Now I'm running Cleanrom 1.5. If I wanted to install a new rom can someone please explain exactly what I do to go about it? As jargon free as possible would be awesome.
Sent from my SCH-I545
I certainly scared the carp outta me the other night. I'm using the Carbon ROM and while I do like it, I miss a couple of the S4s features. I picked what looked like a good modified stock ROM and proceeded to flash it.
I'm using Goo and TWRP for the job. I checked of all 3 boxes for clearing cache, davik and factory reset.
Then I chose the file and started it.
The first result, it acted like if was doing everything but nothing changed. Phone still worked fine.
On the next try, I waited for TWERP to start and I reselected the ROM I wanted and flashed it.
When it booted up, I was very happy to see the original screens come up. Then it stopped on the one with the Verizon check mark. The blue LED slowly pulsing and nothing else for about 30 min. I removed battery to try and start over. Same thing again.
Time to goto my backup and restore my phone back to Carbon.
IT FAILED.
Now my phone is stuck in a weird looking boot up loop. After a few tries I was able to get into recovery
mode. TWRP started loading, froze and crashed! Even though I am a total noob at this, I still did not panic.
I'd restart my phone by removing the battery, going into recovery mode and then wildly press every button on my phone hoping to break the loop. It worked! I chose a different save and tried it all over again. FAIL.
ON the next I wiped every bit of old data off. Chose Factory restore crossed my fiingers....it work! My phone is fine now.
Thanks to that ordeal and this thread I think I know what I did wrong even though this never happened to me. before.
1) WIPE THE DATA
2)INSTALL A COMPATABLE KERNAL FIRST
V^^^^V
Vampyre111 said:
I certainly scared the carp outta me the other night. I'm using the Carbon ROM and while I do like it, I miss a couple of the S4s features. I picked what looked like a good modified stock ROM and proceeded to flash it.
I'm using Goo and TWRP for the job. I checked of all 3 boxes for clearing cache, davik and factory reset.
Then I chose the file and started it.
The first result, it acted like if was doing everything but nothing changed. Phone still worked fine.
On the next try, I waited for TWERP to start and I reselected the ROM I wanted and flashed it.
When it booted up, I was very happy to see the original screens come up. Then it stopped on the one with the Verizon check mark. The blue LED slowly pulsing and nothing else for about 30 min. I removed battery to try and start over. Same thing again.
Time to goto my backup and restore my phone back to Carbon.
IT FAILED.
Now my phone is stuck in a weird looking boot up loop. After a few tries I was able to get into recovery
mode. TWRP started loading, froze and crashed! Even though I am a total noob at this, I still did not panic.
I'd restart my phone by removing the battery, going into recovery mode and then wildly press every button on my phone hoping to break the loop. It worked! I chose a different save and tried it all over again. FAIL.
ON the next I wiped every bit of old data off. Chose Factory restore crossed my fiingers....it work! My phone is fine now.
Thanks to that ordeal and this thread I think I know what I did wrong even though this never happened to me. before.
1) WIPE THE DATA
2)INSTALL A COMPATABLE KERNAL FIRST
V^^^^V
Click to expand...
Click to collapse
I can not stress enough HOW IMPORTANT THE KERNEL IS!
Hmm so everyone is a now a Oriental Flash Master from the far East now huh?
What recovery is everyone using?
[updated: 07-12-2013]
Flashing Questions
So, if you just need to add something, like different Kernerl, do you have to wipe and start from scratch?
Should you.
If so, and you backup apps and data in Titanium, then what you do a full wipe, flash entire rom, and reinstall the apps and data associated therewith?
Last, I have asked this but cannot seem to get an answer.
Installed Hyperdrive 7 (also had 5.7 and 6). Rom is super smooth and fast, working like a charm. but I want Verizon Visual Voice Mail.
I tried to copy the apk file to the devices system/app directory but get permission denied message....tried to install, and get failed message....
xander45 said:
So, if you just need to add something, like different Kernerl, do you have to wipe and start from scratch?
Should you.
If so, and you backup apps and data in Titanium, then what you do a full wipe, flash entire rom, and reinstall the apps and data associated therewith?
Last, I have asked this but cannot seem to get an answer.
Installed Hyperdrive 7 (also had 5.7 and 6). Rom is super smooth and fast, working like a charm. but I want Verizon Visual Voice Mail.
I tried to copy the apk file to the devices system/app directory but get permission denied message....tried to install, and get failed message....
Click to expand...
Click to collapse
did you set the permissions for the app? That should work actually. Look at one of the apps in that directory, and set the permissions the same for the voice app. Reboot and see what happens.
Good luck.
May want to post this question also in my guide thread.
http://forum.xda-developers.com/showthread.php?t=2295557
Sorry if this is dumb, but how do I know what kernels for sure work with my device and how do I get them to my external sd card? I suppose the one that is currently on my device(how to get that to sd?), but what others?
Thanks.
Painterface said:
Sorry if this is dumb, but how do I know what kernels for sure work with my device and how do I get them to my external sd card? I suppose the one that is currently on my device(how to get that to sd?), but what others?
Thanks.
Click to expand...
Click to collapse
Please bring the question over to my thread up above. It shows also what kernels to use. We will help there.
Another noob question: so you still advise flashing a kernel even if the ROM creator says that the ROM comes with the appropriate kernel and that no extra flashing is required? I've got the Verizon Galaxy S4 variant and specifically am thinking of Dubbsy's Google Play Edition ROM.
Sent from my SCH-I545 using Tapatalk 2
theoneknownasbob said:
Another noob question: so you still advise flashing a kernel even if the ROM creator says that the ROM comes with the appropriate kernel and that no extra flashing is required? I've got the Verizon Galaxy S4 variant and specifically am thinking of Dubbsy's Google Play Edition ROM.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
You would flash the rom, and after, flash your verizon kernel, simple as that.
I hope i'm not overlooking a thread where this was a problem but i'm at a loss after looking for 3 days. I was running Tonked world edition v2 (android 4.0.3) without problems for almost a year when I saw that 4.3 PAC was released for the Rezound and I thought I would try it out. It was a lot of fun but I use my tablet for most everything and world edition seemed to give better battery life. Everything worked fine with PAC when it was running and I got world edition restored just fine but for some reason superuser is acting really weird. It would allow any app that had super user permissions before the upgrade to work fine but any new app that needed root permissions after the restore is not working. I've been using Root Checker after each trial to see if root access has been restored and nothing works. Not even a request for root permissions shows up. I booted up the phone using adb to make sure I had boot access and flashed both superuser app 3.1.3 and 3.2-RC3 and also tried just the binaries 3.1.1 (each individually of course). After trying to flash superuser through recovery even though the apps listed in superuser were stil there nothing was being granted super user access anymore. I noticed that su in system/bin didn't have correct permissions and root browser wasn't able to change anything after losing root permissions so I used adb shell to try and change permissions, which I was able to change, but it didn't do anything to help the problem. The weird thing is even after wiping the system, cache, and davilk multiple times and a fresh install of the rom the same problem persists. The only thing I can think of is somehow the built in superuser app (part of aokp) is still interfearing with superuser somehow but I have no idea and like I said i'm stil at a loss of what else to try.
I apologize in advance if this has been answered somewhere eles but if anyone can point me in the right direction I would be very greatful.
I appreciate any help in advance and even the slightest advice will be helpful, thanks again.
czach5932 said:
I hope i'm not overlooking a thread where this was a problem but i'm at a loss after looking for 3 days. I was running Tonked world edition v2 (android 4.0.3) without problems for almost a year when I saw that 4.3 PAC was released for the Rezound and I thought I would try it out. It was a lot of fun but I use my tablet for most everything and world edition seemed to give better battery life. Everything worked fine with PAC when it was running and I got world edition restored just fine but for some reason superuser is acting really weird. It would allow any app that had super user permissions before the upgrade to work fine but any new app that needed root permissions after the restore is not working. I've been using Root Checker after each trial to see if root access has been restored and nothing works. Not even a request for root permissions shows up. I booted up the phone using adb to make sure I had boot access and flashed both superuser app 3.1.3 and 3.2-RC3 and also tried just the binaries 3.1.1 (each individually of course). After trying to flash superuser through recovery even though the apps listed in superuser were stil there nothing was being granted super user access anymore. I noticed that su in system/bin didn't have correct permissions and root browser wasn't able to change anything after losing root permissions so I used adb shell to try and change permissions, which I was able to change, but it didn't do anything to help the problem. The weird thing is even after wiping the system, cache, and davilk multiple times and a fresh install of the rom the same problem persists. The only thing I can think of is somehow the built in superuser app (part of aokp) is still interfearing with superuser somehow but I have no idea and like I said i'm stil at a loss of what else to try.
I apologize in advance if this has been answered somewhere eles but if anyone can point me in the right direction I would be very greatful.
I appreciate any help in advance and even the slightest advice will be helpful, thanks again.
Click to expand...
Click to collapse
go to settings> about phone> and tap build number until deveoloper options are available....when enabled go back into settings and go to developer options and ensure root access has access to apps and adb
REV3NT3CH said:
go to settings> about phone> and tap build number until deveoloper options are available....when enabled go back into settings and go to developer options and ensure root access has access to apps and adb
Click to expand...
Click to collapse
Developers options were already visible from the beginning with the Rom but that option to restrict root to apps and/or adb isn't there (at least on 4.0). I know the setting your talking about and I'm going to see if there is another way to enable it.
czach5932 said:
Developers options were already visible from the beginning with the Rom but that option to restrict root to apps and/or adb isn't there (at least on 4.0). I know the setting your talking about and I'm going to see if there is another way to enable it.
Click to expand...
Click to collapse
what recovery did you try to install superuser from
I would assume your current rom has SU built in, may want to consider a clean install. At least back up your current one and install it clean (with no app data restored) to see if it fixes the problem.
REV3NT3CH said:
what recovery did you try to install superuser from
Click to expand...
Click to collapse
CWM based recovery by Flyhalf205 v6.0.1.9
Never had any problem until now. I tried Amon-ra a long time ago but it wouldn't wipe correctly sip I've stuck work this one
mjones73 said:
I would assume your current rom has SU built in, may want to consider a clean install. At least back up your current one and install it clean (with no app data restored) to see if it fixes the problem.
Click to expand...
Click to collapse
This Rom doesn't have su built in and I've tried about every combination of wipes, flashes, and restores
-Trial-
I noticed that in system/bin that there were two files, su and su.bak su was at 0 bytes and su.bak was at 23k and I tried switching them around and also giving su.bak (renamed to su) full 777 permissions but nothing worked. After the file modification root checker failed much quicker though. Changed everything back
I just noticed after changing everything back that su had its permissions changed again. It is listed as -rwsr-sr-x which is full read only user write and full execute with suid and sgid special. I'm trying to find out but I can't find how to give all permisions with suid and sgid. Any idea if any of this helps or is the culprit?
czach5932 said:
CWM based recovery by Flyhalf205 v6.0.1.9
Never had any problem until now. I tried Amon-ra a long time ago but it wouldn't wipe correctly sip I've stuck work this one
This Rom doesn't have su built in and I've tried about every combination of wipes, flashes, and restores
-Trial-
I noticed that in system/bin that there were two files, su and su.bak su was at 0 bytes and su.bak was at 23k and I tried switching them around and also giving su.bak (renamed to su) full 777 permissions but nothing worked. After the file modification root checker failed much quicker though. Changed everything back
I just noticed after changing everything back that su had its permissions changed again. It is listed as -rwsr-sr-x which is full read only user write and full execute with suid and sgid special. I'm trying to find out but I can't find how to give all permisions with suid and sgid. Any idea if any of this helps or is the culprit?
Click to expand...
Click to collapse
install AMON RA 3.16 as it has the super user fixed into it under advanced....once installed just reflash your custom recovery of your choice....also that version of cwm is way out of date you want version 6.0.3.6...they get updated for many reasons such as stuff like this
czach5932 said:
CWM based recovery by Flyhalf205 v6.0.1.9
Never had any problem until now. I tried Amon-ra a long time ago but it wouldn't wipe correctly sip I've stuck work this one
This Rom doesn't have su built in and I've tried about every combination of wipes, flashes, and restores.
Click to expand...
Click to collapse
Kind of surprising someone would release a modded Sense ROM with no su..
Sent from my ADR6425LVW using Tapatalk
I'll try that as soon as I can. I figured why change something if it's not broken. I appreciate the help and I'll report back as soon as I can
- UPDATE-
Tried to use Amon-RA 3.16 and use the SU fix option under advanced options. It removed my other super user app and replaced it but nothing changed, no popup to ask for super user permissions. After that I booted up cwm 6.0.3.6 touch a couple of times and like it so I decided to flash it and now data and wi-fi are not working. But before flashing, I booted it up a couple time and tried wiping everything (3x) and tried both a clean install and a restore and same problem. Neither the Amon-RA, 3.1, or the 3.2 nor the manually flashed binarys do anything. I also found how to change the premissions for su but now when I try to chmod anything it says read only system. Seems like i'm going backwards and making no progress.
I still appreciate any and all help.
Sent from my SCH-i815 using XDA Premium HD app
czach5932 said:
I'll try that as soon as I can. I figured why change something if it's not broken. I appreciate the help and I'll report back as soon as I can
Sent from my SCH-i815 using XDA Premium HD app
Click to expand...
Click to collapse
also if im not mistaken...tonked had a mass multitude of issues for me....if you need the phone for global use and trying to stay stock and stable as possible there is much better options...to further help...for all ICS roms and lower use Amon Ra 3.16 period...for anything higher like jellybean or kitkat use cwm or twrp...amon ra was meant for the earlier roms as cwm and twrp were not
REV3NT3CH said:
also if im not mistaken...tonked had a mass multitude of issues for me....if you need the phone for global use and trying to stay stock and stable as possible there is much better options...to further help...for all ICS roms and lower use Amon Ra 3.16 period...for anything higher like jellybean or kitkat use cwm or twrp...amon ra was meant for the earlier roms as cwm and twrp were not
Click to expand...
Click to collapse
When I rooted my phone initially Amon-ra it wouldn't wipe correctly and kept force closing everything which is why I went with cwm. Before I went to pac and android 4.3 everything worked perfectly. I just don't understand why (with full wipes) and a restore with upgraded recoveries something from 4.3 is still messing with the system.
The main thing I want is longest battery life and if you can suggest something I'll try it but Tonked gave me over three days on one charge with minimal use. I could get 6+ hrs talk time with hours of Mog with a single charge. I'll try anything. My screen is cracked so I'm thinking of using warranty and get a refurbished phone and restoring that way but I don't want to be out a hundred bucks.
czach5932 said:
When I rooted my phone initially Amon-ra it wouldn't wipe correctly and kept force closing everything which is why I went with cwm. Before I went to pac and android 4.3 everything worked perfectly. I just don't understand why (with full wipes) and a restore with upgraded recoveries something from 4.3 is still messing with the system.
The main thing I want is longest battery life and if you can suggest something I'll try it but Tonked gave me over three days on one charge with minimal use. I could get 6+ hrs talk time with hours of Mog with a single charge. I'll try anything. My screen is cracked so I'm thinking of using warranty and get a refurbished phone and restoring that way but I don't want to be out a hundred bucks.
Click to expand...
Click to collapse
because with any recovery...a full clean wipe meaning you wipe cache, dalvik cache, system, boot, data, factory wipe, and android secure. you still have the main internal files that never get touched by any recovery....if your s-off you can run my downgrade upgrade guide to get back to full stock as the ruu's fully wipe everything....ive actually managed with both talon 1.0 and tachyon to get 24+ hourse of normal use
REV3NT3CH said:
because with any recovery...a full clean wipe meaning you wipe cache, dalvik cache, system, boot, data, factory wipe, and android secure. you still have the main internal files that never get touched by any recovery....if your s-off you can run my downgrade upgrade guide to get back to full stock as the ruu's fully wipe everything....ive actually managed with both talon 1.0 and tachyon to get 24+ hourse of normal use
Click to expand...
Click to collapse
But how would flashing pac modify anything that a full restore wouldn't change back? I know I used a ruu before, maybe I need to go and do that back to bone stock and upgrade from there. I go out of town for a couple of days and I'll try that and let you know. If you can think of anything else I will be greatly appreciative. Thanks Austin.
czach5932 said:
But how would flashing pac modify anything that a full restore wouldn't change back? I know I used a ruu before, maybe I need to go and do that back to bone stock and upgrade from there. I go out of town for a couple of days and I'll try that and let you know. If you can think of anything else I will be greatly appreciative. Thanks Austin.
Click to expand...
Click to collapse
again...most recoveries only wipes so much to an extent....even most samsung devices no matter how much you wipe in recovery you will eventually have to odin back to stock to start fresh as certain things are left behind from flashes...im only assuming some of your issues on 4.3 was sd mounting issues as well as rebooting....in the posts for them are the fixes for those issues...some of which requires TWRP only to fix...twrp is more stable than any of the recoveries because it has the fullest amount of wiping methods that you can ask for and always gets the job done right...get 2.6.3.0 as 2.6.3.3 is for kit kat only
REV3NT3CH said:
also if im not mistaken...tonked had a mass multitude of issues for me....if you need the phone for global use and trying to stay stock and stable as possible there is much better options...to further help...for all ICS roms and lower use Amon Ra 3.16 period...for anything higher like jellybean or kitkat use cwm or twrp...amon ra was meant for the earlier roms as cwm and twrp were not
Click to expand...
Click to collapse
Not sure if I have time this weekend but I just read your s-off tutorial and it seems straight forward but what I'm wondering about is going back to stock. Do I have to go all the way back to stock or could I just use the most recent ruu on your downgrade tutorial to get close enough to stock to wipe the rest of 4.3 and then go back to my Tonked Rom?
Never mind read the tutorial wrong. Will hopefully try this later and I'm hoping to get everything back to normal.
I didn't have time for s-off or time to go back to bone stock (your tutorial) but I did flash the latest ruu and got it to boot to bone stock ics and then flashed the same Tonked Rom and it booted and runs just fine but the only thing that it's granted su access is su itself. No time to mess with anything else yet but looks like I'm running out of options. I'll try your tutorial if I can.
czach5932 said:
I didn't have time for s-off or time to go back to bone stock (your tutorial) but I did flash the latest ruu and got it to boot to bone stock ics and then flashed the same Tonked Rom and it booted and runs just fine but the only thing that it's granted su access is su itself. No time to mess with anything else yet but looks like I'm running out of options. I'll try your tutorial if I can.
Click to expand...
Click to collapse
ha ok i see what you did....when flashing that ph98img file you wiped everything....even superuser....re download amon ra 3.1.6 recovery and install su&superuser via developer options in that and youll have su again
REV3NT3CH said:
ha ok i see what you did....when flashing that ph98img file you wiped everything....even superuser....re download amon ra 3.1.6 recovery and install su&superuser via developer options in that and youll have su again
Click to expand...
Click to collapse
Well even though I tried this before flashing the ruu but after flashing supersu in recovery everything is working correctly. i'm not sure why though but I lost both my two recent cwm backups (even though I used spare sd card during ruu flash). When I went to restore from my main 64 gig sd card, even tough the folder with the date showed up, when I went to restore it said no backup avail (or something like that) and then the folder disapeared. Also haven't had time to figure why backup disappeared or if any backups are currently working but i'll cross that bridge when I get time.
But back to the main issue. Looks like superuser has been having problems with a recent update where people were having the same problem I was having. I attributed it to downgrading but looks like a faulty app update (even though when I tried to look into it no one had said the update had any problems) I guess the upside was I wanted to reset my rom to stock and kinda reset, not really the way I wanted to do it, but lemons to lemonade. I really appreciate all the help and sorry for the stupid problem.
OK. So. I've been encountering nothing but problems since I received my Huawei Ascend P2 phone.
To begin with -
I bought the phone for the sole purpose of it being 4G/LTE. When I got it, I couldn't figure out how to get it, so I contacted Three and was told that my phone had to be 4.3 - it was running 4.1.2.
When I tried to get 4.3 through whatever means, it stopped working.
I tried to do a complete factory reset and now I'm getting many more problems -
I keep getting errors that anything Google related has stopped working (especially Google keyboard).
My contacts won't auto-sync, despite me having my Google account synced up with it.
The icons at the bottom of the screen (back, home, settings/whatever else) won't light up and the home button isn't working.
It's a different loading screen than normal - before it was a Huawei Ascend splash screen, now it just says "Android".
It is not being detected by my laptop whatsoever.
When I try and download anything using a browser, it says "starting download" but nothing works.
So, anyone have a solution? It is driving me demented. And all because I wanted bloody 4G.
boneyarsebogman said:
OK. So. I've been encountering nothing but problems since I received my Huawei Ascend P2 phone.
To begin with -
I bought the phone for the sole purpose of it being 4G/LTE. When I got it, I couldn't figure out how to get it, so I contacted Three and was told that my phone had to be 4.3 - it was running 4.1.2.
When I tried to get 4.3 through whatever means, it stopped working.
I tried to do a complete factory reset and now I'm getting many more problems -
I keep getting errors that anything Google related has stopped working (especially Google keyboard).
My contacts won't auto-sync, despite me having my Google account synced up with it.
The icons at the bottom of the screen (back, home, settings/whatever else) won't light up and the home button isn't working.
It's a different loading screen than normal - before it was a Huawei Ascend splash screen, now it just says "Android".
It is not being detected by my laptop whatsoever.
When I try and download anything using a browser, it says "starting download" but nothing works.
So, anyone have a solution? It is driving me demented. And all because I wanted bloody 4G.
Click to expand...
Click to collapse
I think we need some more info on the attempt to upgrade via whatever means. What steps / guide were you following? Did you install a custom rom? If so, what rom and what recovery are you using? From a few minutes of searching around, it seems that there is no official 4.3 update for the phone, and just being ON 4.3 itself will not automagically enable LTE service as this has much to do with the radio/baseband used as much as the actual operating system and that will not get updated via a custom rom (99.999% of the time unless SPECIFICALLY stated). Seems like they are working on an LTE capable update/patch for 4.1.2 soon according to this: http://forum.xda-developers.com/showpost.php?p=50495570&postcount=162 (that post is part of a thread about your phone on a UK carrier so should be pertinent).
es0tericcha0s said:
I think we need some more info on the attempt to upgrade via whatever means. What steps / guide were you following? Did you install a custom rom? If so, what rom and what recovery are you using? From a few minutes of searching around, it seems that there is no official 4.3 update for the phone, and just being ON 4.3 itself will not automagically enable LTE service as this has much to do with the radio/baseband used as much as the actual operating system and that will not get updated via a custom rom (99.999% of the time unless SPECIFICALLY stated). Seems like they are working on an LTE capable update/patch for 4.1.2 soon according to this: http://forum.xda-developers.com/showpost.php?p=50495570&postcount=162 (that post is part of a thread about your phone on a UK carrier so should be pertinent).
Click to expand...
Click to collapse
Thank you for your reply.
I'll talk you through the steps I took as much as I can.
Firstly I rooted the phone using eRoot, which did work and allowed root access.
I then downloaded P2Tools, which was obtained from this thread and it allowed me to put CWM on it.
Once this was done, I attempted to put CM 10.2 on it, but kept getting a Status 7 error. Some quick Googling later, I discovered this video, which showed how to solve it.
When I followed the steps on there, I kept getting a Status 0 error.
That was when I started to encounter those problems, so I wiped everything I could, even system, but that part failed.
And that's about it.
boneyarsebogman said:
Thank you for your reply.
I'll talk you through the steps I took as much as I can.
Firstly I rooted the phone using eRoot, which did work and allowed root access.
I then downloaded P2Tools, which was obtained from this thread and it allowed me to put CWM on it.
Once this was done, I attempted to put CM 10.2 on it, but kept getting a Status 7 error. Some quick Googling later, I discovered this video, which showed how to solve it.
When I followed the steps on there, I kept getting a Status 0 error.
That was when I started to encounter those problems, so I wiped everything I could, even system, but that part failed.
And that's about it.
Click to expand...
Click to collapse
K. So you are still on the stock rom, rooted, with CWM recovery (which version?), and after you attempted to wipe /system, it failed to wipe (what was the error message there?), and now it boots and has all kinds of weird glitches? First thing to try would be to go back to CWM and wipe Cache and Dalvik Cache and then Fix Permissions. This MIGHT help. If it doesn't then you will just probably want to throw a stock rom back on there to get back to running right again.
es0tericcha0s said:
K. So you are still on the stock rom, rooted, with CWM recovery (which version?), and after you attempted to wipe /system, it failed to wipe (what was the error message there?), and now it boots and has all kinds of weird glitches? First thing to try would be to go back to CWM and wipe Cache and Dalvik Cache and then Fix Permissions. This MIGHT help. If it doesn't then you will just probably want to throw a stock rom back on there to get back to running right again.
Click to expand...
Click to collapse
I've wiped the Caches and Dalvik Cache and can't seem to find "Fix Permissions". I did some searching and it seems this feature was removed from CWM? I'm running v6.0.3.7 of CMW.
When I try to format the system, it says
E:format_volume failed to unmount "/system"
Error formatting /system!
Weird, they did take it out. Koush said it was a placebo. Which normally I would take as law, if it weren't for many times I have ran fix permissions and it caused apps that were force closing to not force close anymore. But whatever, if you wanna try, flash this: http://db.tt/9aWdF8Rp. It'll either help fix something, or do nothing. Won't make it any worse. If it can't mount to format though, it's either or a bug with CWM for your device, or after factory reset, reboot recovery and try again. But you really don't want to wipe /system unless you have a nandroid or another rom on your storage that is accessible.
Thanks so much for your help so far. Took me ages to figure out how to get that file on my phone, but I managed to do it. I then installed zip from recovery mode and chose the fix_permissions. Then reboot and it asked me to root the phone again. It's now upgrading and hopefully it will work now.
It is still saying "Unfortunately, Android keyboard has stopped" and other things. What do you reckon I can do now? You're right, it seems like I can't make it any worse.
boneyarsebogman said:
Thanks so much for your help so far. Took me ages to figure out how to get that file on my phone, but I managed to do it. I then installed zip from recovery mode and chose the fix_permissions. Then reboot and it asked me to root the phone again. It's now upgrading and hopefully it will work now.
It is still saying "Unfortunately, Android keyboard has stopped" and other things. What do you reckon I can do now? You're right, it seems like I can't make it any worse.
Click to expand...
Click to collapse
Ok. So looks like first thing to check is to see WHICH version of the P2 you have because it seems like there are at least 2 different sub versions of it. The P2-6070 and the P2-6011. Please go to Settings / About Phone/Device and let me know all the software info there.
Also, have you unlocked the bootloader (I'm guessing so since you have recovery, but just checking)?
I found some more info on how to get you back up and running, but want to confirm the system version so everything goes as smoothly as possible. There's a new update that just came out not too long ago that people are saying LTE works on, so hopefully we can get you to that point.
es0tericcha0s said:
Ok. So looks like first thing to check is to see WHICH version of the P2 you have because it seems like there are at least 2 different sub versions of it. The P2-6070 and the P2-6011. Please go to Settings / About Phone/Device and let me know all the software info there.
Also, have you unlocked the bootloader (I'm guessing so since you have recovery, but just checking)?
I found some more info on how to get you back up and running, but want to confirm the system version so everything goes as smoothly as possible. There's a new update that just came out not too long ago that people are saying LTE works on, so hopefully we can get you to that point.
Click to expand...
Click to collapse
Mine is the P2-6011.
Swear if we get this working, never changing anything ever.
Yes, the bootloader is unlocked.
Alright, so here is a link for the newest firmware for your phone :
http://huaweidevices.ru/ROM4221/P2/...R001C00B038CUSTC19D001_United_Kingdom_H3G.rar
Need to be on stock recovery. Unpack the rar file and put the whole folder /dload on the root of the SD card. This has the update.app that should take care of everything for you. Turn off the phone and turn it on by holding Vol + and - and Power together. This is supposed to boot it into the mode to take care of the update for you.
If you don't wanna go back to complete stock, I have another way that involves switching to TWRP recovery and restoring a rom via nandroid restore. If you'd prefer that, lemme know and I'll shoot you the links.
es0tericcha0s said:
Alright, so here is a link for the newest firmware for your phone :
http://huaweidevices.ru/ROM4221/P2/...R001C00B038CUSTC19D001_United_Kingdom_H3G.rar
Need to be on stock recovery. Unpack the rar file and put the whole folder /dload on the root of the SD card. This has the update.app that should take care of everything for you. Turn off the phone and turn it on by holding Vol + and - and Power together. This is supposed to boot it into the mode to take care of the update for you.
If you don't wanna go back to complete stock, I have another way that involves switching to TWRP recovery and restoring a rom via nandroid restore. If you'd prefer that, lemme know and I'll shoot you the links.
Click to expand...
Click to collapse
If I ever meet you I definitely owe you a drink. Did exactly as you said and everything (from what I can tell) is working.
It's one of the things I love about Android phones - unless you do some serious damage to it physically, for the most part it is fixable.
So, thanks button isn't enough - you saved me giving up and buying a new phone
*Hi Five* Glad all is well!
But yea, I do this for a living. Seriously. Helping people on here is how I stay sharp. lol
getting a gateway 504 error from link to firmware, would love to get this update working as i keep getting a notification on phone saying update available but it wont work
boneyarsebogman said:
Thank you for your reply.
I'll talk you through the steps I took as much as I can.
Firstly I rooted the phone using eRoot, which did work and allowed root access.
I then downloaded P2Tools, which was obtained from this thread and it allowed me to put CWM on it.
Once this was done, I attempted to put CM 10.2 on it, but kept getting a Status 7 error. Some quick Googling later, I discovered this video, which showed how to solve it.
When I followed the steps on there, I kept getting a Status 0 error.
That was when I started to encounter those problems, so I wiped everything I could, even system, but that part failed.
And that's about it.
Click to expand...
Click to collapse
Can you post the link of the CM 10.2 rom For huawei P2.
I search for a long long time. but still dosnt found a rom.
Thx
Sorry for digging this up but does someone have the stock ROM of the P2? Im stuck like the fella who started this thread and havent found the stock ROM anywhere.
Thanks for the attention.