Has anybody heard about this? Has anybody seen this?
On other phones, the opposite has happened, how the hell does this happen? Is it about partitions? What can I do to find out if I've screwed them up?
I mean, like, come on.
Just updated my N7 and it's the exact opposite.
Since you've given no details, no one can answer.
This is a DOA thread. No info, what software was used, no error log from flash.
Related
Hi, I tried to manually install the 2.2.2 update through recovery as the OTA didn't seem to be arriving (dialer checkin didnt work either) but i get an error saying that the update.zip cannot be verified or something like that and it will not complete the installation.
I do not think my N1 is rooted however i did buy it second hand but it was sold as unused and there is no lock on the boot animation.
Also I don't know if this is relevant or not but my N1's kernel version says HTCatand or something where most peoples' says Android Build.
As you can probably tell im a bit of a noob (only experience with this kind of stuff is from my old rooted DEXT).
Anyway do you guys have any idea why the update won't verify?
Thanks.
Also I don't know if this is relevant but i saw someone on another similar post mention their hboot in the bootloader. If its relevant mine was 0.35.something.
Im kinda worried about this as its too late to return the N1 to the guy I bought it from so any help would be hugely appreciated.
Ok, I've done something stupid and I don't know what.
I've searched the forums for about 5 hours now, and can't find any help. If I've missed something, I apologize. I'm kind of frazzled.
I was trying to install an updated ROM from my internal SD via CWM recovery. There was an error, and now I'm stuck in recovery mode. I've tried clearing everything, but it won't boot to anything other than the CWM Recovery screen. I can't go into download mode to flash anything, or else I would just flashback to stock and start over. I even tried the whole taking your battery out and plugging the tab in to go to DL mode, but that does nothing.
We're dealing with a Galaxy Tab 2 7.0 P3113.
I'm about to cry.
Plz halp.
I might have it fixed now, but I don't want to get ahead of myself.
I finally managed to time my button mashing well enough that I'm in download mode. Will update soon.
If anyone cares.
I GOT IT
Ok, so I sill don't know what I did to end up in his mess, but through what I count as sheer luck I ended up in download mode, and was able to use ODIN to flash a stock rom.
I would delete this thread, but I want to leave it open in case anyone else runs into the same issues.
I had a similar issue when trying to update my rom, I found this to be particularly useful: http://forum.xda-developers.com/showthread.php?t=2302599
basdxz said:
I had a similar issue when trying to update my rom, I found this to be particularly useful: http://forum.xda-developers.com/showthread.php?t=2302599
Click to expand...
Click to collapse
I did read that, but I was flashing a GB ROM, so I figured it didn't apply. I do appreciate the tip, though.
Hi guys, I'm pretty new to rooting so tell me if i need to give more info etc cause I know i can be a bit vague.
So I rooted my phone no problem via the all in one kit thing and installed cyanogen, but this was right before the big android update so I wanted to switch back and update to that, but somewhere along the line i got rid of all the Roms (I think)
The stage it's at now: I can boot normally but the startup wizard fails, I assume this is because the stock operating system isnt hooked up to run, regardless I can't find a copy or figure out how to run it. (before my TWRP seemed to stop running on startup)
Bootloader: I don't know how it ended up relocked after I'd unlocked it but am guessing that is why i cant access the custom recovery at the moment (twrp)
If anyone is able could you walk me through, or point me to a guide to show:
How to unlock a relocked phone,
How to get a Stock version of Android (anything after 4.0 I guess because it will auto update?) running on there
Tell me if I'm being dumb in any part of this (apart from pissing about with things I don't understand, haha)
OK, So i'm unlocked and back onto TWRP, that was easy though, What I do need help with is working out how to install the factory Operating system again, last time I tried that is what caused the relocking etc so any help would be amazing.
Thanks, Simon
Redijedeye said:
OK, So i'm unlocked and back onto TWRP, that was easy though, What I do need help with is working out how to install the factory Operating system again, last time I tried that is what caused the relocking etc so any help would be amazing.
Thanks, Simon
Click to expand...
Click to collapse
Is this the same device as the one you are asking about in? [Q] How do I know what RUU to use, and more by Redijedeye
sd_shadow said:
Is this the same device as the one you are asking about in? [Q] How do I know what RUU to use, and more by Redijedeye
Click to expand...
Click to collapse
Sorry yes, meant to close this post now that this particular problem was kinda sorted but didnt get round to it last night. Unless you know a way to get the correct firmware for the wifi? Just seems strange it'd update wrong.
Redijedeye said:
Sorry yes, meant to close this post now that this particular problem was kinda sorted but didnt get round to it last night. Unless you know a way to get the correct firmware for the wifi? Just seems strange it'd update wrong.
Click to expand...
Click to collapse
No, I don't.
I consider this [Completed] and have thread closed.
I have been searching for a solution for over 2 weeks, and i have not found a single working solution. My problem is that i was trying to put WeLoveKatamari on my phone and i changed the build.prop to make my phone seem to be a 1024MB Samsung S4 SDRAM DIE=4Gb so i could get it. I also deleted the play store as well. Then i shut my phone off and since it was rooted (i don't know if it still is, probably is) it took a few boots to actually get the spinning logo, but halfway through it goes to a black screen. I can get to the recovery and fastboot. So i looked up stuffs and found out how to flash stuff and i tried flashing stock firmware but for some reason (currently guessing it is because of my locked bootloader) it says stuff like preflash validation failed and remote failure, so i can't flash stuff. I tried factory reset and it does nothing. Is there a way to forcefully flash something like a blankflash or stock firmware? Nothing seems to be working, and if you can help it would be greatly appreciated. Also if pics of anything are needed i am happy to give them to you. I hope i have a chance to fix this, and i would hug anyone of help.
**** yes i fixed it
Probably be a good idea to tell folks about how you did it. You never know when someone could use the knowledge.
Sent from my XT1064 using Tapatalk
tronmech said:
Probably be a good idea to tell folks about how you did it. You never know when someone could use the knowledge.
Sent from my XT1064 using Tapatalk
Click to expand...
Click to collapse
agree
Hi everyone,
I'm a little in trouble and I'd need some help 'cause I'm getting an headache.
I temporary have to use a Galaxy S Duos 2, and given its really old OS I tried to flash it with something more recent. Problem is, there is something weird in the device preventing me to flash it.
In short, I'm stuck on two problems:
1) All the resources I've tried are either for the GT-S7580, kylepro, single SIM or for the GT-S7582, kyleprods, dual sim. Guess what? Mine is a GT-S7582, kylepro, dual sim. What the hell?
2) All the roms I've tried fail during the installation 'cause of an error on the sha1 of the system folder. I've tried everything, wiped the folders in the suggested order, restored the file system...nada.
So, any idea what's going on, and how to get out of this situation? I'd absolutely need to make the device work, but I'm clueless. I've even thought to reinstall the stock rom, but I've got no idea which version is the correct one for my device version.
Uh, just to add as much info as I can: I'm using Odin3 v3.12.10 and TWRP 3.2.1-0-kylepro
Help, please?
Well, exactly like last time I posted and asked for some help, I got totally ignored. Luckily, after a while yesterday I've done some thinking and I've found the possibile cause of the problem, tried and...yes, it worked; posting here in case someone else would ever find itself stuck on something similar in the future.
In short, the root of the problem is that for whatever reason the phone was thinking to be a kylepro instead of a kyleprods. I tried to correct the build.prop file, but there is no chance to do it from inside TWRP so I ended up tweaking the updater-script file. The procedure is explained on line in different sites, I cannot give a link as the forum system does not allow me to do it.
you can post the link with a minor mentioned edit, would be helpful for others who might face the same in future