Related
Im getting this error and force close on one of my Heros when I try installing any of my apps on any of the 2.1 roms. Im coming from Fresh 1.1 and following the same procedure I used on my other Hero on which the market is fully functional. Ive wiped everything over and over and cleared data on anything that looked like it at to do with the market. I also tried fix apk mismatches from recovery. Short of RUU which Id like to avoid if at all possible Ive tried everything else I can think of. In searching I have come across this error code on other android phones, but nothing on the hero and nothing specific to trying to install apps. So has anyone else seen this? And would RUU do anything a full data wipe didnt already?
Reading instructions has its benefits grasshopper...
Download the latest recovery and throw it onto your SD Card, boot into the old version of recovery and flash the new recovery as a .zip update, reboot into recovery again and then wipe your phone again, then install android 2.1, don't reboot yet, make sure your rom either has it's own custom kernal or download one for 2.1 and flash it, open up adb and clear dalvik cache and boot cache, then reboot your phone and you should load without any problems.
Thanks. But I did that from the get go. Aside from flashing a kernal, but Im running Darchtrev2 on the fully functional Hero that I mentioned and thats got a custum kernal built into the rom. So thats what I started with on the second one using the exact same process without success. Does wiping from adb do more than wiping from recovery? Thats one other thing I didnt do after the initial install.... But do understand you correctly that you have seen this specific error before?
Just bumpin the tread in hopes of finding a solution. I dont even mind gettin flamed for asking a stupid question if I could get linked up with a fix! lol I see its getting views, just no ideas I guess... It sucks cuz everything else works fine except the market. I get the list of my downloads, when I tap on one to install I the download button instead of the install button, so Ill tap on it and I get get the progress bar saying its downloading. When it gets to 100% I get the error and force close... Anyone?
I would try wiping again then flashing fresh 1.1 see if that boots and everything works ok then I would redownload the recovery and flash that still running fresh then reboot make sure everyhting is cool, then redownload whatever 2.1 rom you want and wipe and flash.
doing this serves 2 purposes
1. make sure that somewhere along the line none of the files corupted
2. if you still have the same problem then it will let you know where the problem is coming from.
just process of elimination
if you still have problems after that then I would say RUU, yes it is different than just wiping from recovery as it restores a completely stock image and gets rid of everything else. all a data wipe really does is get rid of user data.
just my opinion.
honestley thinnking about it I RUU'd my phone just for giggles then I re-rooted and then flashed DCv1 right from stock and I found that a lot of the little bugs that people where seeing I wasnt so it may not be a bad idea to ruu anyways.
Thanks for the reply and for giving me something different to try. I hadnt thought about trying that. Frustration I guess! It makes sense though. Ill give it shot. Thanks!
Why not see why it fc'd?
Adb with logcat of ...vending....
Find the syntax here: http://developer.android.com/search.html
Just an idea. It may or maynot give you the insight to fix the cause ( like a parameter ...vending... is null fetching on ).
Yeah, Ive been thinking about RUU'n too just to see if making a fresh start would make any difference, but after all the time I spent getting the one Hero working like I want on 2.1 and the troubles Ive had with the second and what Ive read about people bricking trying to RUU or flash recovery Ive been kinda hesitant....
willy900wonka said:
Why not see why it fc'd?
Adb with logcat of ...vending....
Find the syntax here: http://developer.android.com/search.html
Just an idea. It may or maynot give you the insight to fix the cause ( like a parameter ...vending... is null fetching on ).
Click to expand...
Click to collapse
Thanks. I dont know that Im quite that knowledgable though. Im sure I could read a logcat... understanding what the hell I would be reading is something else again. Saving the url though in case I need to dig deeper. Thanks for the reply.
wtphoto said:
honestley thinnking about it I RUU'd my phone just for giggles then I re-rooted and then flashed DCv1 right from stock and I found that a lot of the little bugs that people where seeing I wasnt so it may not be a bad idea to ruu anyways.
Click to expand...
Click to collapse
Sometimes it's just fun to RUU and do everything again
Alright if you're still having problems then just follow these steps:
Boot into recovery and make a nandroid back up just in case something goes wrong.
Download the latest version of your current 2.1 rom and reflash it from Recovery.
Open up adb and mount the /data directory (adb shell, mount /data)
Enter the following two commands in adb: rm -r /data/boot-cache , rm -r /data/dalvik-cache
Go Back to ADB and type the following commands: cd /data/data/com.android.vending , rm -R cache
Fix UID Mismatches using the tool in Recovery and then reboot your phone
regaw_leinad said:
Sometimes it's just fun to RUU and do everything again
Click to expand...
Click to collapse
or NOT!
Thanks again for your help all. I ended up just RUU'in . I'm with fixxer... fun isn't how I'd describe it! Anyway, I got it all working just to find out its got the mms issue now... if its not one thing its another. Oh well, something for me to work on tomorrow! Thanks again for the replies and advice.
HERNANDEZ4LIFE said:
Thanks again for your help all. I ended up just RUU'in . I'm with fixxer... fun isn't how I'd describe it! Anyway, I got it all working just to find out its got the mms issue now... if its not one thing its another. Oh well, something for me to work on tomorrow! Thanks again for the replies and advice.
Click to expand...
Click to collapse
You should have updated to the latest ruu...
wcgbmd said:
You should have updated to the latest ruu...
Click to expand...
Click to collapse
The latest RUU? I used the 1.56..... I did get it working tho. Flashed the mms. fix zip. Just wasn't expecting to have to as I didn't with my other hero. Don't know what the difference is between the two devices. Both are google branded, but the second one fought me every step of the way.
HERNANDEZ4LIFE said:
Thanks again for your help all. I ended up just RUU'in . I'm with fixxer... fun isn't how I'd describe it! Anyway, I got it all working just to find out its got the mms issue now... if its not one thing its another. Oh well, something for me to work on tomorrow! Thanks again for the replies and advice.
Click to expand...
Click to collapse
First, sorry for the bump.
I just started getting this error and wanted to know if you figured out exactly what it was so I didn't have to go through that whole RUUing process. Thanks.
don't know if this is your problem, but i know on sushi rom you have to go to manage applications, market, click on it and then click on uninstall updates.. Then apps. will download and install correctly.
boredmug said:
don't know if this is your problem, but i know on sushi rom you have to go to manage applications, market, click on it and then click on uninstall updates.. Then apps. will download and install correctly.
Click to expand...
Click to collapse
You're the bomb. That worked like a charm.
boredmug said:
don't know if this is your problem, but i know on sushi rom you have to go to manage applications, market, click on it and then click on uninstall updates.. Then apps. will download and install correctly.
Click to expand...
Click to collapse
Cant believe nobody wrote this first
boredmug said:
don't know if this is your problem, but i know on sushi rom you have to go to manage applications, market, click on it and then click on uninstall updates.. Then apps. will download and install correctly.
Click to expand...
Click to collapse
I was having the same problem on DC a couple days ago and that fixed it for me. I was reading this thread wondering why no one had mentioned it yet.
has stopped unexpedectly.
i was messing around with switching the ROMS and when i rebooted, it said this.
i have no home screen, and it keeps popping up but i can still recieve phone calls and texts
anyone have any idea of what to do?
i can't seem to go into recovery mode either..
pacDiesel said:
has stopped unexpedectly.
i was messing around with switching the ROMS and when i rebooted, it said this.
i have no home screen, and it keeps popping up but i can still recieve phone calls and texts
anyone have any idea of what to do?
i can't seem to go into recovery mode either..
Click to expand...
Click to collapse
nothing to worry about.. if you switched radio, check that the time on the phone is correct, sometimes its being reset to year 1903 which messes up many apps. Also if you switched radio/spl did you run fastboot erase system -w afterwards?
This exception should not be related to the recoveryconsole
easiest is just to wipe everything and reflash, dont forget ext. if youve used it.
If recovery is for some reason unaccesable you can reflash via flash_image() when the phone has booted android.
Also do a logcat
Mod. edit: not dev related, moved to general
ivarson_swe said:
nothing to worry about.. if you switched radio, check that the time on the phone is correct, sometimes its being reset to year 1903 which messes up many apps. Also if you switched radio/spl did you run fastboot erase system -w afterwards?
This exception should not be related to the recoveryconsole
easiest is just to wipe everything and reflash, dont forget ext. if youve used it.
If recovery is for some reason unaccesable you can reflash via flash_image() when the phone has booted android.
Also do a logcat
Click to expand...
Click to collapse
Yeah bro, I have no idea what you just said.
lol
nothing to worry about.. if you switched radio, check that the time on the phone is correct, sometimes its being reset to year 1903 which messes up m
Click to expand...
Click to collapse
Yeah bro, I have no idea what you just said.
lol
Click to expand...
Click to collapse
Which rom were you using and which rom are you using now. Did you change your radio or spl before installing this rom.
Load up into recovery and run fix uid mismatches. Reboot and see if that helps.
Does your app launcher work? If so run terminal emulator. Type in su and then enter
Type in fix_permissions and then enter. Let the script run.
Type I'm exit then enter
Type in exit and then enter again. Terminal will close. Reboot phone. If you cannot get to terminal emulator then run it from adb ( if possible )
And the other poster was referring to when you change radios there are a few commands. He wanted to make sure you ran them all
-------------------------------------
Sent via the XDA Tapatalk App
I know you guys hate when people jump the gun...but I'm honestly running out of ideas here. Earlier today I tried to use LCD Density changer on my Nexus S...whether this was stupid on my part, you all can decide later. As for now my nexus boots a black screen. I'm only posting here cuz maybe in finding a solution we can uncover a bit about how the nexus is set up, because it seems to refuse any changes made to the system through fastboot or adb push.
I have tried just about every option to restore the system to stock format, and need help getting my nexus back to booting condition. I've tried fastboot flashing the system.img and just get a "write failed" error. I've pushed the whole system dump to /system through adb and when i reboot it is still missing the files i just pushed. I've flashed different boot.img's in combination with the first two steps, and still my phone remains unbootable.
Any ideas what could be going wrong?
fykick said:
I know you guys hate when people jump the gun...but I'm honestly running out of ideas here. Earlier today I tried to use LCD Density changer on my Nexus S...whether this was stupid on my part, you all can decide later. As for now my nexus boots a black screen. I'm only posting here cuz maybe in finding a solution we can uncover a bit about how the nexus is set up, because it seems to refuse any changes made to the system through fastboot or adb push.
I have tried just about every option to restore the system to stock format, and need help getting my nexus back to booting condition. I've tried fastboot flashing the system.img and just get a "write failed" error. I've pushed the whole system dump to /system through adb and when i reboot it is still missing the files i just pushed. I've flashed different boot.img's in combination with the first two steps, and still my phone remains unbootable.
Any ideas what could be going wrong?
Click to expand...
Click to collapse
Is it safe to say you didnt do nandroid restore prior?
Yes, that is correct...didn't think it'd cause this much of a problem(stupid me). I asked earlier if maybe some could upload a nandroid restore for me so I could at least attempt that. But I got no response, so I'm still in the dark.
fykick said:
Yes, that is correct...didn't think it'd cause this much of a problem(stupid me). I asked earlier if maybe some could upload a nandroid restore for me so I could at least attempt that. But I got no response, so I'm still in the dark.
Click to expand...
Click to collapse
When I get home in an hour, I'll factory wipe and make a backup of the stock rom for you.
Any recommendations on where to upload?
I got you man im backing up right ow....going to wipe then backup again and ill upload it so give me a bit
maybe ill be really nice and include some custom transitions for you
Only been 1 day since it came out, since it boots to black, take it back to the store, act stupid, get another one. Solved.
nandroid
pm'ing you the link
let me know if it works
mount usb storage copy and paste the into clockworkmod/backups
unmount usb storage and restore....gave you all the goodies too
nxt said:
Only been 1 day since it came out, since it boots to black, take it back to the store, act stupid, get another one. Solved.
Click to expand...
Click to collapse
Hahahahaha best thing I've heard all day
Apparently the NS is super-brickable, according to JBQ (@jbqueru) on android-building:
-Even though Nexus S is designed to be suitable for AOSP work, there
are some caveats. I very strongly recommend against trying to use
Nexus S for anything related to AOSP at the moment. Trying to unlock
or use your Nexus S for AOSP work could easily turn it into a Nexus B
(where B means "brick"); I have two of those, they're not very useful.
I'll send some guidelines about what is currently possible once I've
finished pushing the source code.
Click to expand...
Click to collapse
Is there anyway I can get the link for that nandroid? I seem to have messed my system files up as well.
wdfowty said:
Hahahahaha best thing I've heard all day
Apparently the NS is super-brickable, according to JBQ (@jbqueru) on android-building:
Click to expand...
Click to collapse
Now that is a frightening prospect;( How can google make a dev phone thats super brickable... hmmm
JD
AndHel said:
Is there anyway I can get the link for that nandroid? I seem to have messed my system files up as well.
Click to expand...
Click to collapse
Can I get the link for the stock nandroid also? I need to use a secure boot image.
Okay, thank you very much for the Nandroid. It worked and I'm back up and running.
OKay
So i sent the backup to at least 3 people anyone care to let me know hows its going and whether or not they like the customizations
drexman8244 said:
So i sent the backup to at least 3 people anyone care to let me know hows its going and whether or not they like the customizations
Click to expand...
Click to collapse
maybe you can upload it to mediafire or somewhere else, and create a thread? it might help others out
ill take your advice on that Thanks
adb push may not have been working because your system wasn't mounted properly in Clockwork recovery. I had this issue when trying to root. In Recovery, go to Mounts & Storage and hit "Mount System" THEN adb push the system dump.
You probably didn't need to nandroid. Could have just used adb to reset the density line in your build.prop I assume?
fykick said:
Okay, thank you very much for the Nandroid. It worked and I'm back up and running.
Click to expand...
Click to collapse
Please mention it on the Thread Title PROBLEM SOLVED.
An nandroid backup can be found here http://forum.xda-developers.com/showthread.php?t=877601
Hi guys, i'm the developer of LCD Density Changer. Sorry about the problems it caused.
Is it true that the Nexus S, doesn't support a density change. That would be a real bummer! Not for the app, but in general. I just don't hope Google blocks a density change in their new Android versions.
A question: does the "preview/temporarily" density change works in the LCD Density Changer app. If so, there is still hope.
Meanwhile, based on these reports I will put up a note to warn Nexus S users.
Whenever I try to make a backup with CMW, it gives me an error that says "An error occurred while attempting to run privileged commands"
How do I fix it?
You have S-Off?
estallings15 said:
You have S-Off?
Click to expand...
Click to collapse
Yep fully rooted and everything. It worked before but not sure why it's not working now.
HTC~TwikiE said:
Yep fully rooted and everything. It worked before but not sure why it's not working now.
Click to expand...
Click to collapse
Try reflashing your recovery. Sounds like it's borked.
estallings15 said:
Try reflashing your recovery. Sounds like it's borked.
Click to expand...
Click to collapse
I just tried that and it gives me "An error occurred while downloading your recovery."
How do I do it manually?
HTC~TwikiE said:
I just tried that and it gives me "An error occurred while downloading your recovery."
How do I do it manually?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1242901
estallings15 said:
http://forum.xda-developers.com/showthread.php?t=1242901
Click to expand...
Click to collapse
Just tried that, back to square one. Same error
HTC~TwikiE said:
Just tried that, back to square one. Same error
Click to expand...
Click to collapse
Hmm, I'm getting worried that this may be a hardware problem. Does anybody have any ideas?
estallings15 said:
Hmm, I'm getting worried that this may be a hardware problem. Does anybody have any ideas?
Click to expand...
Click to collapse
The error isn't necessarily hardware; that message could be occurring because of a software problem with the su application that is being used.
- Have you been flashing/nandroiding successfully with CWM in the past?
- Were your su binaries updated recently?
- Did the ROM get an OTA recently that might have updated the su binaries?
- Was this failed backup being done after/before flashing a ROM that wasn't full-wiped?
- EDIT: Why of course you have S-off and anyone who asked after you said so would be a silly fellow.
If all else were to fail, I'd suggest going back to a stock ROM and re-rerooting, and I imagine that your problems would 'go away'. I'm not sure what intermediate methods you could try, though, unless you wanted to try to run your backup commands over adb or re-push your su binaries or .apk.
tuxkamen said:
The error isn't necessarily hardware; that message could be occurring because of a software problem with the su application that is being used.
- Have you been flashing/nandroiding successfully with CWM in the past?
- Were your su binaries updated recently?
- Did the ROM get an OTA recently that might have updated the su binaries?
- Was this failed backup being done after/before flashing a ROM that wasn't full-wiped?
- Do you have S-off?
If all else were to fail, I'd suggest going back to a stock ROM and re-rerooting, and I imagine that your problems would 'go away'. I'm not sure what intermediate methods you could try, though, unless you wanted to try to run your backup commands over adb or re-push your su binaries or .apk.
Click to expand...
Click to collapse
I was under the impression that your recovery didn't need the SU binary to do it's job. The SU binary is used within Android, right?
Edit: Also, he already said that he has S-Off. If you're going to offer help, please pay attention.
I had the same error show up recently. I just went around it and did a backup while in boot recovery.
... now... what to do if that starts to fail... Hmm
Sent from my myTouch 4g using xda app
estallings15 said:
I was under the impression that your recovery didn't need the SU binary to do it's job. The SU binary is used within Android, right?
Click to expand...
Click to collapse
I'm referring to both the Superuser.apk and the general su/busybox binaries (that got installed as part of his rooting process) which I think get used when doing the calls to make backups to your SD card. He's most likely getting the message because either his rooting method has gone awry or whatever his phone thinks is the appropriate way to get elevated privileges is no longer able to do that. The possible causes for that pretty much boil down to either permissions needing fixing or needing to redo the installation of the su "stuff".
I'm not sure how that would _happen_. This goes back to knowing what happened recently to the phone from a software perspective (any new ROM flash lately, potentially to something that doesn't have root perms?). He was able to reinstall CWM, but he may need to re-push the su/busybox stuff in order to get back to full functionality (and maybe do it a few times, just like in the initial rooting process, to make sure it 'sticks').
Edit: Also, he already said that he has S-Off. If you're going to offer help, please pay attention.
Click to expand...
Click to collapse
I'm not sure why I wrote that. I did notice he said it, said 'meh' and wrote it down anyway. -_-
tuxkamen said:
I'm referring to both the Superuser.apk and the general su/busybox binaries (that got installed as part of his rooting process) which I think get used when doing the calls to make backups to your SD card. He's most likely getting the message because either his rooting method has gone awry or whatever his phone thinks is the appropriate way to get elevated privileges is no longer able to do that. The possible causes for that pretty much boil down to either permissions needing fixing or needing to redo the installation of the su "stuff".
I'm not sure how that would _happen_. This goes back to knowing what happened recently to the phone from a software perspective (any new ROM flash lately, potentially to something that doesn't have root perms?). He was able to reinstall CWM, but he may need to re-push the su/busybox stuff in order to get back to full functionality (and maybe do it a few times, just like in the initial rooting process, to make sure it 'sticks').
I'm not sure why I wrote that. I did notice he said it, said 'meh' and wrote it down anyway. -_-
Click to expand...
Click to collapse
No offense, but I'm fairly positive you can perform all the functions in recovery with a completely wiped system partition. If that is the case, then that theory is debunked. S-Off should give you all access/permissions you need. This is why I said that I'm worried about his hardware. If his bootloader was HTC dev unlocked, then I would say he needed S-Off.
estallings15 said:
No offense, but I'm fairly positive you can perform all the functions in recovery with a completely wiped system partition. If that is the case, then that theory is debunked. S-Off should give you all access/permissions you need. This is why I said that I'm worried about his hardware. If his bootloader was HTC dev unlocked, then I would say he needed S-Off.
Click to expand...
Click to collapse
The error message he's getting is from trying to start his backup out of ROM Manager, not recovery--that error usually pops up before going into the backup process. You can verify this yourself by temp unrooting in Superuser, launching ROM Manager, and trying to do something like make a backup or fix permissions. I have a feeling TwikiE could do backups by _booting_ into recovery.
That's why I'm suggesting the need to check the Superuser implementation. ROM Manager doesn't think it has either root permission or privileges. If TwikiE isn't seeing the 'you must be rooted' popup when starting ROM Manager, then the phone is rooted but the app doesn't think it's privileged to send the phone into the backup process. If this the first time TwikiE's tried a backup since his last ROM flash, the ROM might have a bad or incompatible set of root tools, or some other app may have been installed that has bad tools. Or maybe it's as simple as having accidentally hit Deny on a Superuser prompt.
Some things TwikiE could do to try and resolve the problem without rerooting could be:
- Try Fix Permissions out of ROM Manager and see if the same error message appears. If it succeeds, try backing up again. If not...
- Check the Superuser app settings to see if ROM Manager is on the list as allowed or denied. If it's on deny, clear it out. If it's allowed or not there, move on.
- Clear out the application data and cache for both the Superuser app and ROM Manager from the apps menu. Try to backup again and see if the superuser prompt appears.
- If that doesn't work, try uninstalling and reinstalling Superuser and ROM Manager from the Play Store, reinstalling both, then try to backup.
Beyond that comes more drastic steps.
tuxkamen said:
The error message he's getting is from trying to start his backup out of ROM Manager, not recovery--that error usually pops up before going into the backup process. You can verify this yourself by temp unrooting in Superuser, launching ROM Manager, and trying to do something like make a backup or fix permissions. I have a feeling TwikiE could do backups by _booting_ into recovery.
That's why I'm suggesting the need to check the Superuser implementation. ROM Manager doesn't think it has either root permission or privileges. If TwikiE isn't seeing the 'you must be rooted' popup when starting ROM Manager, then the phone is rooted but the app doesn't think it's privileged to send the phone into the backup process. If this the first time TwikiE's tried a backup since his last ROM flash, the ROM might have a bad or incompatible set of root tools, or some other app may have been installed that has bad tools. Or maybe it's as simple as having accidentally hit Deny on a Superuser prompt.
Some things TwikiE could do to try and resolve the problem without rerooting could be:
- Try Fix Permissions out of ROM Manager and see if the same error message appears. If it succeeds, try backing up again. If not...
- Check the Superuser app settings to see if ROM Manager is on the list as allowed or denied. If it's on deny, clear it out. If it's allowed or not there, move on.
- Clear out the application data and cache for both the Superuser app and ROM Manager from the apps menu. Try to backup again and see if the superuser prompt appears.
- If that doesn't work, try uninstalling and reinstalling Superuser and ROM Manager from the Play Store, reinstalling both, then try to backup.
Beyond that comes more drastic steps.
Click to expand...
Click to collapse
Who does anything in ROM Manager? Damn it, OP, reboot into recovery and do it right.
Heh. I didn't want to put it *exactly* that way...
Sent from my HTC myTouch 4g using xda app-developers app
I tried flashing X-Note 6.0 and things have gone sour from there. I keep getting bootloop, i'm able to do initial setup until it asks me for gmail, once i input my address, it pulls my name and when it asks me to confirm it, it restarts the phone. Then im able to finish setup, but as soon as i'm back and i reboot again, im stuck in infinite bootloop.
I tried reverting back to stock via odin, but i got bootloop again, fortunately for me, after about 1h, it booted back into OS and i was able to root and reinstall twrp.
I dont have a backup of my EFS, again i'm not even sure thats the real problem, can anybody please help?
EDIT: On stock the bootloop is not infinite, after about 10 minutes the phone eventually boot back in OS
polish_pat said:
I tried flashing X-Note 6.0 and things have gone sour from there. I keep getting bootloop, i'm able to do initial setup until it asks me for gmail, once i input my address, it pulls my name and when it asks me to confirm it, it restarts the phone. Then im able to finish setup, but as soon as i'm back and i reboot again, im stuck in infinite bootloop.
I tried reverting back to stock via odin, but i got bootloop again, fortunately for me, after about 1h, it booted back into OS and i was able to root and reinstall twrp.
I dont have a backup of my EFS, again i'm not even sure thats the real problem, can anybody please help?
EDIT: On stock the bootloop is not infinite, after about 10 minutes the phone eventually boot back in OS
Click to expand...
Click to collapse
Please help me someone. I tried the EFS fix here with no success. I tried to restore via odin, factory reset, every time i finish initial setup and restore my apps and reboot, it bootloops.
Shot in the dark, but disable auto installing of apps/restoring apps. Could be that it is triggering the bootloop due to an incompatible app with X-Note.
If no good. You gotta be brave and strip that badboy back with a full wipe/dalvik/cache, reflash your stock image (get shot of recovery also) then see if it can get past the bootloop (don't forget to remove your SD Card also if you have one) - Give it shot, see what you come up with.
Also if you're on an N9005 model, head over to Djembays thread and grab an image of him, seems to have gotten a lot of people out of issues (JayTheNut uses his images when he messes up) -
Lemme know how you get on, I'll have a nose around see what else it could be.
radicalisto said:
Shot in the dark, but disable auto installing of apps/restoring apps. Could be that it is triggering the bootloop due to an incompatible app with X-Note.
If no good. You gotta be brave and strip that badboy back with a full wipe/dalvik/cache, reflash your stock image (get shot of recovery also) then see if it can get past the bootloop (don't forget to remove your SD Card also if you have one) - Give it shot, see what you come up with.
Also if you're on an N9005 model, head over to Djembays thread and grab an image of him, seems to have gotten a lot of people out of issues (JayTheNut uses his images when he messes up) -
Lemme know how you get on, I'll have a nose around see what else it could be.
Click to expand...
Click to collapse
I dont think you read the thread. I'm not on xnote anymore, i'm on stock firmware, MJ4, i also have a W8 and the EFS script fix is for international version. I've odined back to stock and all the issues i'm having are also present on stock firmware
polish_pat said:
I'm not on xnote, i'm on stock firmware, MJ4, i also have a W8 and the EFS script fix is for international version
Click to expand...
Click to collapse
Ah ok, so that changes the playing field a little. - Give @CalcProgrammer1 a Message, he uses the W8 and the guy certainly knows a thing or two about it. All I can think of at this time.
EDIT: actually thinking about it, you haven't upgraded your bootloader by mistake have you?
I have a feeling background WiFi scanning is enabled in Settings -> WiFi -> Advanced - I don't think any of the newer ROM updates ever managed to have that not bootloop your phone on reboot. In case you're stumped and can't find the setting, you'll have to hit the menu key on the WiFI screen.
radicalisto said:
Ah ok, so that changes the playing field a little. - Give @CalcProgrammer1 a Message, he uses the W8 and the guy certainly knows a thing or two about it. All I can think of at this time.
EDIT: actually thinking about it, you haven't upgraded your bootloader by mistake have you?
Click to expand...
Click to collapse
I dont think so, unless flashing Xnote 6.0 or using odin to restore stock does that. Thats pretty much all I did, but i think i might have done something that might have fixed the problem, i'm not sure yet, but i'll confirm shortly
radicalisto said:
Ah ok, so that changes the playing field a little. - Give @CalcProgrammer1 a Message, he uses the W8 and the guy certainly knows a thing or two about it. All I can think of at this time.
EDIT: actually thinking about it, you haven't upgraded your bootloader by mistake have you?
Click to expand...
Click to collapse
I use the N900T (T-Mo) version, though I guess it's pretty similar to the W8. Unfortunately I don't know anything about the efs side of things on the N900T or equivalents. I've been avoiding the backup and restore functionality in TWRP since it was widely reported to cause bootloops in the first few weeks after release anyways. Have you tried the bootloop fix method over at the T-Mobile N900T forum? I forget what the process exactly was but people reported great success using it (including those who intentionally recreated the problem to test the fix). I did have a similar boot loop issue on my Note 1 which was fixed doing a complete Odin restore with a full factory image (bootloader, system, modem, kernel, recovery, etc. - the entire complete factory restore). I don't know if such a package exists for the N900W8 and that's something I wouldn't use the wrong variant's version of.
odin was one of the first thing i tried, as mentionned the problem was on 100% stock device. Now i've tried formating SD cards and i was able stop the bootloops but now instead i get a worse problem when my phone keep giving me force closes and everytime i dismiss one, another one pops back up and its just a FC Loop:crying:
I have an W8...I also had terrible boot loop problems and I can't quite remember the cause, but this is what fixed it.
Obviously I can't stress enough to read this and type this in very carefully, and that if your phone stops working, turns into a robot, explodes, or tries to kill your dog I'm not responsible .
1. Reboot to recovery
2. Hit "Advanced" Select "Terminal Command"
3. Hit "Select" (lower right corner)..Do not select any specific folder, just hit select..
4. keyboard will open, type in the following commands, make sure you put the spaces and / where they need to be, it needs to look exactly as outlined..
mke2fs /dev/block/mmcblk0p12
Hit Go - The command will run.
Clear the box, type the following command
mkdir /efs
Hit Go - The command will run.
Clear the box, type the following command
mount -t ext4 /dev/block/mmcblk0p12 /efs
Hit Go - The command will run.
Do a factory reset, reboot system
Can't remember where I got this from, only saved the text not the forum >.<
stucked
Hello guys .... I wanna say first ... that I tryed all options and all efs backups etc etc ... everything works just fine back up my efs . and restore but .. when I try to register my phone on network ends like this :
- only emergency calls
- when try to insert a new sim card my n9005 just reboot when search for network also ... is charging but allways remain at 8-10% no more up .
I tryed all kind of stuff ... made back ups .... and tryed install stock firmware etc ... rooting and did anything ... I will apreciate any kind of help ...I just wanna tell you I am close to deat ... becouse is my wife phone and still does not know I messed up with
polish_pat said:
EDIT: I'm offering a 50$ bounty to anybody that gives me a solution that fixes my phone, paid in full by paypal
I tried flashing X-Note 6.0 and things have gone sour from there. I keep getting bootloop, i'm able to do initial setup until it asks me for gmail, once i input my address, it pulls my name and when it asks me to confirm it, it restarts the phone. Then im able to finish setup, but as soon as i'm back and i reboot again, im stuck in infinite bootloop.
I tried reverting back to stock via odin, but i got bootloop again, fortunately for me, after about 1h, it booted back into OS and i was able to root and reinstall twrp.
I dont have a backup of my EFS, again i'm not even sure thats the real problem, can anybody please help?
EDIT: On stock the bootloop is not infinite, after about 10 minutes the phone eventually boot back in OS
Click to expand...
Click to collapse
Hey dude i think xnote 6 is mk2 based, so what basically is going wrong is that you're trying to downgrade your bootloader. please try flashing an mk2 stock rom ( or an mj7) via odin, that should fix it ..
just my 2 cents
Hi guys i tried everything my phone was in a constant state of bootloop and wouldnt connect to any carrier. Then i came across this thread http://forum.xda-developers.com/showthread.php?t=2567133 and now my phone is working, still wont connect to a carrier but the phone is now stable which is a good thing. Hope this helps some of you :fingers-crossed:
Thanks for all the input, as of now, i was able to stop the boot-looping on stock rom, but I do still have major issues like i cannot install twrp, by goomanger it tell me its done but when i reboot into recovery, i end up in stock recovery. And yes, i'm rooted. Also i cannot format my SD card from the OS, it keep telling me the card is being checked all the time. I also have a lot of other small issues that should not be there on a fresh install. i honestly dont know what screwed up so bad but i will try some of the solutions mentioned above and report back.
To me that sounds like your partitions are all screwed up have you tried flashing using a pit file?
Sent from my SM-N9005 using xda app-developers app
Steeno78 said:
To me that sounds like your partitions are all screwed up have you tried flashing using a pit file?
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
Never. I'm def not that newbish. I dont know whats happening but everytime i format the phone it gets a little better.
Sent from my SM-N900W8 using Tapatalk